APRS Packet Errors for OK1UOJ (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
20260514022148OK1UOJ>APRS,OK2ZAW-17*,qAO,OK0BAF-10:!4957.90O/016P539E_225/002g003t049h100b10042_BATT=4.06V DP_RSSI: -121 dBm DP_SNR: -5.50 dB
20260514024932OK1UOJ>APRS,OK2ZAW-17*,qAO,OK1BF-10:!4957.90N/01605.39E_2
20260514025846OK1UOJ>APRS,OK2ZAW-17*,qAS,OK1TPG-27:!4957.90N/0"3=Er22/002g003t048h100b10040_BATT=4.06V DP_RSSI: ;2 dBm DP_SNR $750 dB 9 SNR=-21dB RSSI=-77db
20260514032630OK1UOJ>APRS,OK2ZAW-17*,qAO,OK2R-12:!4957.ί0Qv0]NU )rv/04W60Tr048hk2_@ATT=4.06V DP_RSSI: -122 dBm DP_SNR: -8.75 dB
20260514040806OK1UOJ>APRS,OK2ZAW-17*,qAO,OK1BF-10:!4957.90N/09?
20260514042634OK1UOJ>APRS,OK2ZAW-17*,qAO,OK1BF-10:!4957.90N/0a:ES5&m;UɎc6%1WL?vp
20260514044941OK1UOJ>APRS,OK2ZAW-17*,qAO,OK1BF-10:!4957.90N/01605.39E_12 g3
20260514051247OK1UOJ>APRS,OK2ZAW-17*,qAO,OK2R-12:!4957.90N/0QPV5N39E_180/001a00Rr048hq+M>*e,(c&bz"V8|ָQSI: -122 dBm DP_SNR: -7.00 dB
20260514063559OK1UOJ>APRS,OK2ZAW-17*,qAO,OK2R-12:!41=.1PN/0:059A_r22/003g005^u}=G+!T.D7@#kSI: -122 drmDP_3.R: -6.DBr^
20260514072214OK1UOJ>APRS,OK2ZAW-17*,qAS,OK1TPG-27:!97,;0N/01605.39E_206/003b0e`q054h100b10044_BATT=4.07V DP_RycLۇ=Áj:i?~Z?5 dB
20260514072651OK1UOJ>APRS,OK2ZAW-17*,qAO,OK0BAF-10:!4957.90N/01605.39E_221/00"d006u054h100b10044_BATT=4.07V DP_RSSI: -122 dBm DP_SNR: -9.50 dB