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
20260320184041OK2ZAW-17>APLG0,qAO,OK2R-12:=5016.90NL01625.35ŦDGrZ` K G6J
20260320190541OK2ZAW-17>APLG0,qAO,OK2R-12:=501 ML01625.35&c^m%vpk0uZGI
20260320193041OK2ZAW-17>APLG0,qAO,OK1BF-10:=50!&?( 01vF4:qtC&nOpc sun DiGi
20260320201041OK2ZAW-17>APLG0,qAO,OK2R-12:=501- 0-f905.35E&LoRQ#@un DiGi
20260320202541OK2ZAW-17>APLG0,qAO,OK1BF-10:=5016.90^u 2,06:S)z L-K
20260320205541OK2ZAW-17>APLG0,qAO,OK1BF-10:=5016.90NL0162=.35E&LoRa sun`
20260320210044OK2ZAW-17>APLG0,qAO,OK0BAF-10:=5016.90n<.:5v z(3qnDJ|
20260320214541OK2ZAW-17>APLG0,qAO,OK1BF-10:=5016.90N q25.35E&LoRa sun DiGi
20260320215541OK2ZAW-17>APLG0,qAO,OK2R-12:=5016.90^O11p{34@&LoRa sun0x`
20260320222541OK2ZAW-17>APLG0,qAO,OK2R-12:=5016.90NL016=.E&LoRa sun DiGi
20260320224040OK2ZAW-17>APLG0,qAO,OK1BF-10:=5016.90NL01625.35La0be~Va
20260320224541OK2ZAW-17>APLG0,qAO,OK1BF-10:=501.90NHt=>5.35E&LoRa sun DGi
20260320225541OK2ZAW-17>APLG0,qAO,OK1BF-10:=5013LN"215.35E&LoRa sun i