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
20250715213122KE0PVI>APRS,TCPIP*,qAC,NINTH:@152131z3837.02N/09441.10W_360/NaNg000t093r000p000P000h53b09766 VISR3924 400
20250715213622KE0PVI>APRS,TCPIP*,qAC,NINTH:@152136z3837.02N/09441.10W_360/NaNg000t093r000p000P000h53b09766 VISR3924 400
20250715214122KE0PVI>APRS,TCPIP*,qAC,SECOND:@152141z3837.02N/09441.10W_360/NaNg000t093r000p000P000h53b09766 VISR3924 400
20250715214622KE0PVI>APRS,TCPIP*,qAC,SEVENTH:@152146z3837.02N/09441.10W_360/NaNg000t093r000p000P000h53b09766 VISR3924 400
20250716003622KE0PVI>APRS,TCPIP*,qAC,FIRST:@160036z3837.02N/09441.10W_135/NaNg000t090r000p000P000h59b09755 VISR3924 400
20250716004122KE0PVI>APRS,TCPIP*,qAC,FIRST:@160041z3837.02N/09441.10W_135/NaNg000t090r000p000P000h59b09755 VISR3924 400
20250716004624KE0PVI>APRS,TCPIP*,qAC,SEVENTH:@160046z3837.02N/09441.10W_135/NaNg000t090r000p000P000h59b09755 VISR3924 400
20250716005124KE0PVI>APRS,TCPIP*,qAC,FOURTH:@160051z3837.02N/09441.10W_135/NaNg000t090r000p000P000h59b09755 VISR3924 400