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
20250708002549OK2ZAW-17>APLG0,qAO,OK1KKY-17:=5016.90ÞL91625.35E&LoRa sun DiGi
20250708003049OK2ZAW-17>APLG0,qAO,OK1KKY-17:=5016;0LL01625.35E&LoRa"qul DiGi
20250708010549OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90NL016.17…æ€o^a sun DiGi
20250708011049OK2ZAW-17>APLG0,qAO,OK1KKY-17:=50‘6· “I1;<$ª5O¶LfRa sun DiGi
20250708012549OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90NL01627,7G&LoRa sun DiGi
20250708040549OK2ZAW-17>APLG0,qAS,OK1TPG-27:=50ñ6î5
20250708055549OK2ZAW-17>APLG0,qAO,OK1KKY-17:=501- 0NL01625.35E&LoRa sun DiGi
20250708060049OK2ZAW-17>APLG0,qAO,OK2R-12:=5016.90NeQP25.35E%LoRa sun DiGi