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
20241222055622KE0PVI>APRS,TCPIP*,qAC,EIGHTH:@220556z3831.09N/09440.51W_068/NaNg000t023r000p000P000h87b09902 VISR3924 400
20241222060122KE0PVI>APRS,TCPIP*,qAC,SIXTH:@220601z3831.09N/09440.51W_068/NaNg000t023r000p000P000h87b09902 VISR3924 400
20241222060622KE0PVI>APRS,TCPIP*,qAC,FIFTH:@220606z3831.09N/09440.51W_068/NaNg000t023r000p000P000h87b09902 VISR3924 400
20241222061122KE0PVI>APRS,TCPIP*,qAC,EIGHTH:@220611z3831.09N/09440.51W_068/NaNg000t023r000p000P000h87b09902 VISR3924 400
20241222064122KE0PVI>APRS,TCPIP*,qAC,EIGHTH:@220641z3831.09N/09440.51W_360/NaNg000t024r000p000P000h86b09898 VISR3924 400
20241222064622KE0PVI>APRS,TCPIP*,qAC,SIXTH:@220646z3831.09N/09440.51W_360/NaNg000t024r000p000P000h86b09898 VISR3924 400
20241222065122KE0PVI>APRS,TCPIP*,qAC,THIRD:@220651z3831.09N/09440.51W_360/NaNg000t024r000p000P000h86b09898 VISR3924 400
20241222065622KE0PVI>APRS,TCPIP*,qAC,FIRST:@220656z3831.09N/09440.51W_360/NaNg000t024r000p000P000h86b09898 VISR3924 400