APRS Packet Errors for OK2ZAW-21 (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
20260425140724OK2ZAW-21>APRS,OK2ZAW-17*,qAO,OK1BF-10:!4922.5N/01609.450%000g000t068h25b10152L438_ACU=438_Sv.oaofDs{w rYQBfluztic DP_RSSMz -122 dBm DPWnT:"-2.00 dB
20260425140827OK2ZAW-21>APRS,OK2ZAW-17*,qAO,OK1BF-10:!4924n*n,.lap 0>%53eQf"<68h25b10152L438_ACU=438_Sv.Hora_fet-zaw3.0_solar+Meshtastic DP_RSSI: -121 dBm DP_SNR: -2.00 dB
20260425141145OK2ZAW-21>APRS,OK2ZAW-17*,qAO,OK1BF-10:!4922.1>mz1E940p30
20260425142606OK2ZAW-21>APRS,OK2ZAW-17*,qAO,OK1BF-10:!4922vSƼ8i
20260425142848OK2ZAW-21>APRS,OK2ZAW-17*,qAO,OK1BF-10:!49ڤtVW6YL
20260425143049OK2ZAW-21>APRS,OK2ZAW-17*,qAO,OK1BF-10:!49T`TF/016y.0QC:5`500t067h23b10150L438_ACU=438_Sv jOPa_fetM"0_solar+Meshtastic DP_RSSI: -120 dBm DP_SNR: -3.00 dB
20260425143324OK2ZAW-21>APRS,OK2ZAW-17*,qAO,OK1BF-10:!4922.16N/0160/<43P:O
20260425144554OK2ZAW-21>APRS,OK2ZAW-17*,qAO,OK1BF-10:!4922.16N/01609.45E_000/0::g000t068h24b10151L438_ACU=438_Sv.Hora_fet-zaw3.0_solar+Meshtastic DP_RSSI: -121 dBm dR]UHR
20260425144958OK2ZAW-21>APRS,OK2ZAW-17*,qAO,OK1BF-10:!4922.16N+9[v=ZӢJAa~E]g10149L438_ACU=438_Sv.Hora_fet-zaw3.0_solar+Metic DP_RSSI: -121 dBm DP_SNR: -2.00 dB