APRS Packet Errors for N4AN (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
20250420172547N4AN>APK102,KF4LZA-1*,WIDE2-1,qAR,KN4TGQ-10:=2605.7N/08006.38W_158/019g t078r000p000P 10174
20250420184602N4AN>APK102,KF4LZA-1*,WIDE2-1,qAR,KN4TGQ-10:=2605.75N/0800.38W_126/02g 78r000p000P h65b10167KDvs
20250420201621N4AN>APK102,KF4LZA-1*,WIDE2-1,qAR,KN4TGQ-10:=2605N/08006.38W_007r000p000P h69b1015
20250420201627N4AN>APK102,WIDE1-1,WIDE2-1,qAR,KN4TGQ-10:=2605.75N/0800.g pD5.774/023g t76KDvs