APRS Packet Errors for NO1P-9 (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
20250124114513NO1P-9>APK102,WIDE1-1,WIDE2-1,qAR,KC1NWF:=09H6.0 N/134E9.0 _322/002g t011r000p000P h57b10186KDvs
20250124115013NO1P-9>APK102,WIDE1-1,WIDE2-1,qAR,KC1NWF:=09H6.0 N/134E9.0 _338/003g t011r000p000P h57b10186KDvs
20250124120014NO1P-9>APK102,WIDE1-1,WIDE2-1,qAR,KC1NWF:=09H6.0 N/134E9.0 _332/002g t011r000p000P h57b10186KDvs
20250124120514NO1P-9>APK102,WIDE1-1,WIDE2-1,qAR,KC1NWF:=09H6.0 N/134E9.0 _340/004g t011r000p000P h57b10186KDvs
20250124123015NO1P-9>APK102,WIDE1-1,WIDE2-1,qAR,KC1NWF:=09H6.0 N/134E9.0 _306/002g t010r000p000P h58b10188KDvs