APRS Packet Errors for KE0PVI (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
20250123080123KE0PVI>APRS,TCPIP*,qAC,NINTH:@230801z3831.09N/09440.51W_225/NaNg000t023r000p000P000h93b09889 VISR3924 400
20250123080623KE0PVI>APRS,TCPIP*,qAC,NINTH:@230806z3831.09N/09440.51W_225/NaNg000t023r000p000P000h93b09889 VISR3924 400
20250123082123KE0PVI>APRS,TCPIP*,qAC,EIGHTH:@230821z3831.09N/09440.51W_270/NaNg000t026r000p000P000h92b09889 VISR3924 400
20250123082623KE0PVI>APRS,TCPIP*,qAC,SECOND:@230826z3831.09N/09440.51W_270/NaNg000t026r000p000P000h92b09889 VISR3924 400
20250123083123KE0PVI>APRS,TCPIP*,qAC,FIRST:@230831z3831.09N/09440.51W_270/NaNg000t026r000p000P000h92b09889 VISR3924 400
20250123083623KE0PVI>APRS,TCPIP*,qAC,FIFTH:@230836z3831.09N/09440.51W_270/NaNg000t026r000p000P000h92b09889 VISR3924 400
20250123102123KE0PVI>APRS,TCPIP*,qAC,NINTH:@231021z3831.09N/09440.51W_203/NaNg000t027r000p000P000h84b09899 VISR3924 400
20250123102623KE0PVI>APRS,TCPIP*,qAC,FOURTH:@231026z3831.09N/09440.51W_203/NaNg000t027r000p000P000h84b09899 VISR3924 400
20250123103123KE0PVI>APRS,TCPIP*,qAC,NINTH:@231031z3831.09N/09440.51W_203/NaNg000t027r000p000P000h84b09899 VISR3924 400
20250123103623KE0PVI>APRS,TCPIP*,qAC,FIFTH:@231036z3831.09N/09440.51W_203/NaNg000t027r000p000P000h84b09899 VISR3924 400