APRS Packet Errors for 145.450pb (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
20260208200055PY2TB-15>BEACON,qAO,PY2PE-1:;145.450pb*111111z2329.56S/04540.06Wr145.450MHz T067 -060 PY2KCR
20260208203055PY2TB-15>BEACON,qAO,PY2PE-1:;145.450pb*111111z2329.56S/04540.06Wr145.450MHz T067 -060 PY2KCR
20260208210055PY2TB-15>BEACON,qAO,PY2PE-1:;145.450pb*111111z2329.56S/04540.06Wr145.450MHz T067 -060 PY2KCR
20260208213055PY2TB-15>BEACON,qAO,PY2PE-1:;145.450pb*111111z2329.56S/04540.06Wr145.450MHz T067 -060 PY2KCR
20260208220055PY2TB-15>BEACON,qAO,PY2PE-11:;145.450pb*111111z2329.56S/04540.06Wr145.450MHz T067 -060 PY2KCR
20260208223055PY2TB-15>BEACON,qAO,PY2PE-11:;145.450pb*111111z2329.56S/04540.06Wr145.450MHz T067 -060 PY2KCR
20260208230055PY2TB-15>BEACON,qAO,PY2PE-1:;145.450pb*111111z2329.56S/04540.06Wr145.450MHz T067 -060 PY2KCR
20260209000055PY2TB-15>BEACON,qAO,PY2PE-1:;145.450pb*111111z2329.56S/04540.06Wr145.450MHz T067 -060 PY2KCR
20260209003055PY2TB-15>BEACON,qAO,PY2PE-1:;145.450pb*111111z2329.56S/04540.06Wr145.450MHz T067 -060 PY2KCR
20260209010055PY2TB-15>BEACON,qAO,PY2PE-1:;145.450pb*111111z2329.56S/04540.06Wr145.450MHz T067 -060 PY2KCR
20260209013055PY2TB-15>BEACON,qAO,PY2PE-1:;145.450pb*111111z2329.56S/04540.06Wr145.450MHz T067 -060 PY2KCR