APRS Packet Errors for KE0VWY-10 (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
20260323022046KE0VWY-10>APVRT9,TCPIP*,qAC,T2CSNGRAD:!0r @APRS 144.390Mhz AVRT9B_v1.21_9
20260323025041KE0VWY-10>APVRT9,TCPIP*,qAC,T2CSNGRAD:!0r @APRS 144.390Mhz AVRT9B_v1.21_9
20260323032037KE0VWY-10>APVRT9,TCPIP*,qAC,T2CSNGRAD:!0r @APRS 144.390Mhz AVRT9B_v1.21_9
20260323035033KE0VWY-10>APVRT9,TCPIP*,qAC,T2CSNGRAD:!0r @APRS 144.390Mhz AVRT9B_v1.21_9
20260323042029KE0VWY-10>APVRT9,TCPIP*,qAC,T2CSNGRAD:!0r @APRS 144.390Mhz AVRT9B_v1.21_9
20260323045024KE0VWY-10>APVRT9,TCPIP*,qAC,T2CSNGRAD:!0r @APRS 144.390Mhz AVRT9B_v1.21_9
20260323052020KE0VWY-10>APVRT9,TCPIP*,qAC,T2CSNGRAD:!0r @APRS 144.390Mhz AVRT9B_v1.21_9
20260323055016KE0VWY-10>APVRT9,TCPIP*,qAC,T2CSNGRAD:!0r @APRS 144.390Mhz AVRT9B_v1.21_9
20260323062011KE0VWY-10>APVRT9,TCPIP*,qAC,T2CSNGRAD:!0r @APRS 144.390Mhz AVRT9B_v1.21_9
20260323065006KE0VWY-10>APVRT9,TCPIP*,qAC,T2CSNGRAD:!0r @APRS 144.390Mhz AVRT9B_v1.21_9
20260323072004KE0VWY-10>APVRT9,TCPIP*,qAC,T2CSNGRAD:!0r @APRS 144.390Mhz AVRT9B_v1.21_9
20260323075003KE0VWY-10>APVRT9,TCPIP*,qAC,T2CSNGRAD:!0r @APRS 144.390Mhz AVRT9B_v1.21_9