APRS Packet Errors for OK1FRN-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
20250530211341OK1FRN-9>APLT00,OK2ZAW-17*,qAS,OK1TPG-27:!5004-74N/01430.56E>/A=000768LoRa Tracker -"BAV. 1:7V DprqSI: -119 dBm DP_SNR: 1.75pLʰD SNR=-22dB RSSI=-77db
20250530214342OK1FRN-9>APLT00,OK2ZAW-17*,qAS,OK1TPG-27:!5004.7dK/04430.56E>/A=000779LoRa Tracker -!B`e/: 3.85V DP_RSSI: -119 dBm DP_SNR: 2.00 dB !wQ?!
20250530223841OK1FRN-9>APLT00,OK2ZAW-17*,qAS,OK1TPG-27:!5004.7~01730.57E>/A=000732LoRa Tracker - Bat.: 3.81V DP_RSSI: -q19ddFm DP_SNR: 2.75 dB !wM$!
20250530233342OK1FRN-9>APLT00,OK2ZAW-17*,qAS,OK1TPG-27:!5004.74/0a430.5 )% IޅmQA|6ﷅBQ):!"/ԠLP_RSSI: -118 dBm DP_SNR: 3.25 dB !wX>!
20250531010341OK1FRN-9>APLT00,OK2ZAW-17*,qAS,OK1TPG-27:!58=&4N/01430.56E>/A=000778LoRa Tracker - Bat.: 3.66D"BP_RSSI: -118 dBm DP_SNR: 3.50 dB !w[?!