APRS Packet Errors for VA3RT (last 168 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
20261029224759VA3RT>APWW11,VE3UEL*,WIDE2-1,qAR,KD2PWD-10:;VE I� *29224Ñ417.16N/07628.72WrPHG5580146.‚j!é�C151-060 NET Tu730WÖZ‰É¹co
20261030071116VA3RT>APWW11,TCPIP*,qAC,T2TEXAS:;VE3KBR *3ŠŠÒÑ417.16N/628.72WrPHG5580146.940MHz C151 -060 NET T&²•Íkbr.com
20261030072116VA3RT>APWW11,TCPIP*,qAC,T2TEXAS:;VE3KBR *300ŠÒÑ417.16N/07628.72WrPHG5580146.940MHz C151 -060 NET Tu ve3kbr.com
20261030205948VA3RT>APWW11,VE3UEL,VA3PEC,WIDE2*,qAR,VE3EJP:;VE3RªÊÒÑ417.16N/07628.72WrPHG5580146.940MHz C151 -060 NET Tu730 ve3kbr.com
20261031023746VA3RT>APWW11,VE3UEL*,WIDE2-1,qAR,VE3EJP:;VE3KBR *310237z4417N/028.7MM146.940MHz C1 -060 NET Tu730 v‰É¹com