APRS Packet Errors for 439.025pb (last 6 hours)

This table contains packets in which findU has detected an error. This is an automated system, no manual checking of these packets has been done. Most common cause of this is mistakes in entering the latitude/longitude into hard-coded digis, or positions of 0/0. If packets of yours appear here, and you have looked at it carefully and cannot find the error, look again. I've been watching these error messages in my log, and believe my parser is reasonably correct. Go get the APRS spec to be sure. If you have done that, and are CERTAIN the packet is a legal APRS packet, then it is possible that there is an error in my my parser. Only email me if you are absolutely, positively certain...ask yourself, would I bet $100!

time (UTC)	Packet
20260209093257	PY2TB-15>BEACON,qAO,PY2PE-1:;439.025pb*111111z2329.56S/04540.46Wr439.025MHz T000 -500 PY2KCR DMR
20260209100300	PY2TB-15>BEACON,qAO,PY2PE-1:;439.025pb*111111z2329.56S/04540.46Wr439.025MHz T000 -500 PY2KCR DMR
20260209103257	PY2TB-15>BEACON,qAO,PY2PE-11:;439.025pb*111111z2329.56S/04540.46Wr439.025MHz T000 -500 PY2KCR DMR
20260209110257	PY2TB-15>BEACON,qAO,PY2PE-1:;439.025pb*111111z2329.56S/04540.46Wr439.025MHz T000 -500 PY2KCR DMR
20260209113257	PY2TB-15>BEACON,qAO,PY2PE-1:;439.025pb*111111z2329.56S/04540.46Wr439.025MHz T000 -500 PY2KCR DMR
20260209120257	PY2TB-15>BEACON,qAO,PY2PE-1:;439.025pb*111111z2329.56S/04540.46Wr439.025MHz T000 -500 PY2KCR DMR
20260209130258	PY2TB-15>BEACON,qAO,PY2PE-11:;439.025pb*111111z2329.56S/04540.46Wr439.025MHz T000 -500 PY2KCR DMR
20260209133258	PY2TB-15>BEACON,qAO,PY2PE-1:;439.025pb*111111z2329.56S/04540.46Wr439.025MHz T000 -500 PY2KCR DMR
20260209140257	PY2TB-15>BEACON,qAO,PY2PE-1:;439.025pb*111111z2329.56S/04540.46Wr439.025MHz T000 -500 PY2KCR DMR
20260209143257	PY2TB-15>BEACON,qAO,PY2PE-1:;439.025pb*111111z2329.56S/04540.46Wr439.025MHz T000 -500 PY2KCR DMR
20260209150257	PY2TB-15>BEACON,qAO,PY2PE-1:;439.025pb*111111z2329.56S/04540.46Wr439.025MHz T000 -500 PY2KCR DMR