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
20260520084550OK1UOJ>APRS,OK2ZAW-17*,qAO,OK1BF-10:!4957.)p^/ aú`¥"¯®þ.9/0p"f00µu068h72b10243_BATT=4.10V DP_RSSI: -122 dBm DP_SNR: -5.50 dB
20260520091343OK1UOJ>APRS,OK2ZAW-17*,qAO,OK1BF-10:!4:5:0G¶01605.39E_307/001g003t072h58b10243_BATT=4.10V DP_RSSI: -123 dBm DP_SNR: -7.25 dB
20260520093657OK1UOJ>APRS,OK2ZAW-17*,qAO,OK1BF-10:!4957.90N/01605.39E_185/00²ç0¸;|07;h53b10242_BATT=4.09V DP_RSSI: -122 dBm DP_SNR: -6.00 dB
20260520112829OK1UOJ>APRS,OK2ZAW-17*,qAO,OK2R-12:!4957.9F/01W ~`3xl:[0z5ß”, rEe{B!dL Ρi Ur/MsvUÒŒoSK
20260520113309OK1UOJ>APRS,OK2ZAW-17*,qAO,OK1BF-10:!7957.90N/01605.39E_2£®/0 Qˆ¶BÜ×µê5Q1
20260520120541OK1UOJ>APRS,OK2ZAW-17*,qAO,OK2R-12:!4957.90N/010?$39E_231/002g003t076h45b10233_BATT=4.07V DP_RSSI: -122 dBm DP_SNR: -4.75 dB
20260520123333OK1UOJ>APRS,OK2ZAW-17*,qAO,OK1BF-10:!4957.9L/ÃðN:9E_32
20260520133836OK1UOJ>APRS,OK2ZAW-17*,qAO,OK1BF-10:!4957.iU(J07605.39E_318/004g005t069h69b10233_BATT=4.09V DP_RSSI: -121 dBm DP_SH4`!~fz•"ÙrwZ{