APRS Packet Errors for OK2ZAW-17 (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
20250703030550OK2ZAW-17>APLG0,qAS,OK1TPG-27:=50!5 n*7v$%+ruD&LR1,)b DiGi
20250703032050OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90^]16"/o[a sun
20250703040050OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.9001f75.35E J Rg%su> DiGi
20250703041550OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90NL01624>3%D&LoRa sun DiGi
20250703042050OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90NL0165.L&LoRa sn DiGi
20250703044050OK2ZAW-17>APLG0,qAS,OK1TPG-27:=506.NL01625.35ERiun DiGi
20250703044550OK2ZAW-17>APLG0,qAS,OK1TPG-27:=50Q2l90LL01625.35Lem sun DiGi
20250703051054OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90NL016<.3E&LoRa sun DiGi
20250703052050OK2ZAW-17>APLG0,qAS,OK1MX-12:=501$,91LL01625.35E&LoRa sun DiGi
20250703055050OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90NL01625.35,eXk sun DiGi
20250703062050OK2ZAW-17>APLG0,qAO,OK2R-12:=5016.90.hX9Fr$L?T;i_GаՅ-
20250703064050OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90N*5W65-06ef sun DiGi
20250703083050OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90NL0162.F&LoRa sun DiGi
20250703085550OK2ZAW-17>APLG0,qAS,OK1TPG-27:=500d65.$F&LoRq rt~`Gi