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
20260512093019OK2ZAW-17>APLG0,qAS,OK1TPG-27:=501e96ML01625.35E&LoRa({(DiGi
20260512095019OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5014 9LL01625.35Do^1fVe
20260512100519OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90^M 0v75.c5E&LoRa sun B A
20260512102019OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90L9125.35E&Lo[a0stn DIGK
20260512103019OK2ZAW-17>APLG0,qAS,OK1TPG-27:=501 0"n1$.##Ij n,DiGi
20260512104519OK2ZAW-17>APLG0,qAS,OK1TPG-27:=506&,075=5.35E&LoRr} DiGi
20260512111019OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90NL01625.3$E&LoRa sun DiGi
20260512111519OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5090NL01625.35E&LoRa sun DiGi
20260512120519OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90NL3125.35Fo)n@$!i
20260512131019OK2ZAW-17>APLG0,qAS,OK1TPG-27:=50>1FL01624.34E&LoRa sun DiGi
20260512131019OK2ZAW-17>APLG0,qAO,OK2R-12:=50!7/) .L63P<.3
20260512132519OK2ZAW-17>APLG0,qAO,OK2R-12:=50161NL016"4>3%D&LoRa sunDGa
20260512134019OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90NM !&& 5%F@o>g sun DiGi
20260512142024OK2ZAW-17>APLG0,qAO,OK2R-12:=5016.90NL016"5>3$D&LoRa suni
20260512150019OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90=>5.35E&LoRa sun DiGi