APRS Packet Errors for OK2ZAW-2 (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
20251226143848OK2ZAW-2>APLRG1,OK2ZAW-17*,qAO,OE5XGL-11:!JUH. DP_RSSI: -120 dBm DP_SNR: -21.25 dB !R.HRa LKx!APRS
20251226143848OK2ZAW-2>APLRG1,OK2ZAW-17*,qAO,OK2AF-10:!JUH. DP_RSSI: -120 dBm DP_SNR: -21.25 dB !R.HRa LKx!APRS
20251226143849OK2ZAW-2>APLRG1,OK2ZAW-17*,qAO,OK2R-12:!JUH. DP_RSSI: -120 dBm DP_SNR: -21.25 dB !2.G`tk{s߸a
20251226145855OK2ZAW-2>APLRG1,OK2ZAW-17*,qAS,OK1TPG-27:!L KT |t*ChYV*@Nb.t ۲-x1 SNR=-22dB RSSI=-53db
20251226145855OK2ZAW-2>APLRG1,OK2ZAW-17*,qAS,OK1TPG-27:!L KT |t*ChYV*@Nb.t ۲-x1 SNR=-22dB RSSI=-53db
20251226170126OK2ZAW-2>APLRG1,OK2ZAW-17*,qAR,OK4MD-13:;ER-OK0BZR*111111z4934N6HQ01556.26E0439.400MHz T079 R21k [Svx] S}sk4 OK8GKck DP_RSSI: -120 dBm DP_SNR: -19.75 dB