APRS Packet Errors for YM3BUR (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
20251114200313YM3BUR>APMI06,LOCAL-4,qAR,YM2VTC:;145.775Tu*010101z4008.30N/02908.09E
20251114200424YM3BUR>APMI06,LOCAL-4,qAR,YM2VTC:;145.775Tu*010101z4008.30N/02908.09E
20251114200834YM3BUR>APMI06,LOCAL-4,qAR,YM2VTC:;145.775Tu*010101z4008.30N/02908.09E
20251114200939YM3BUR>APMI06,LOCAL-4,qAR,YM2VTC:;145.775Tu*010101z4008.30N/02908.09E
20251114201349YM3BUR>APMI06,LOCAL-4,qAR,YM2VTC:;145.775Tu*010101z4008.30N/02908.09E
20251114201554YM3BUR>APMI06,LOCAL-4,qAR,YM2VTC:;145.775Tu*010101z4008.30N/02908.09E
20251114202005YM3BUR>APMI06,LOCAL-4,qAR,YM2VTC:;145.775Tu*010101z4008.30N/02908.09E
20251114202155YM3BUR>APMI06,LOCAL-4,qAR,YM2VTC:;145.775Tu*010101z4008.30N/02908.09E
20251114202605YM3BUR>APMI06,LOCAL-4,qAR,YM2VTC:;145.775Tu*010101z4008.30N/02908.09E
20251114202830YM3BUR>APMI06,LOCAL-4,qAR,YM2VTC:;145.775Tu*010101z4008.30N/02908.09E
20251114203241YM3BUR>APMI06,LOCAL-4,qAR,YM2VTC:;145.775Tu*010101z4008.30N/02908.09E
20251114203537YM3BUR>APMI06,LOCAL-4,qAR,YM2VTC:;145.775Tu*010101z4008.30N/02908.09E
20251114205336YM3BUR>APMI06,LOCAL-4,qAR,TA1KNN-1:;145麪¢Õ©010101z4008.30N/02908.09Er145.775MHz T114 -060