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
20250314183642NO1P-9>APK102,WIDE1-1,WIDE2-1,qAR,W1DMR-4:=09H6.0 N/134E9.0 _119/005g t058r000p000P h23b10196KDvs
20250314190644NO1P-9>APK102,WIDE1-1,WIDE2-1,qAR,W1DMR-4:=09H6.0 N/134E9.0 _092/006g t058r000p000P h21b10191KDvs
20250314192145NO1P-9>APK102,WIDE1-1,WIDE2-1,qAR,W1DMR-4:=09H6.0 N/134E9.0 _138/008g t059r000p000P h21b10190KDvs
20250314195146NO1P-9>APK102,WIDE1-1,WIDE2-1,qAR,W1DMR-4:=09H6.0 N/134E9.0 _083/002g t058r000p000P h21b10191KDvs
20250314200647NO1P-9>APK102,WIDE1-1,WIDE2-1,qAR,W1DMR-4:=09H6.0 N/134E9.0 _134/005g t058r000p000P h19b10190KDvs
20250314203148NO1P-9>APK102,WIDE1-1,WIDE2-1,qAR,W1DMR-4:=09H6.0 N/134E9.0 _163/004g t055r000p000P h19b10188KDvs
20250314211150NO1P-9>APK102,WIDE1-1,WIDE2-1,qAR,W1DMR-4:=09H6.0 N/134E9.0 _211/003g t054r000p000P h21b10192KDvs
20250314213651NO1P-9>APK102,WIDE1-1,WIDE2-1,qAR,W1DMR-4:=09H6.0 N/134E9.0 _182/001g t052r000p000P h25b10192KDvs