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
20250902165040OK2ZAW-17>APLG0,qAO,OK1KKY-17:=5016.90NL016‚.947oRÁ*JåÇ*FIGK
20250902173038OK2ZAW-17>APLG0,qAO,OK0BAF-10:=5016.90I`ac25.35E&LoRa sun DiGi
20250902180538OK2ZAW-17>APLG0,qAO,OK2R-12:=5016.90N; D#9g=5iy
20250902184038OK2ZAW-17>APLG0,qAO,OK0BAF-10:=5016.90NL016²5.35E&LoRa sun DiGi
20250902190040OK2ZAW-17>APLG0,qAO,OK0BAF-10:=506n0~O016±™NÕ™•ò¯ÂöÅéWÍb Éƒ
20250902204038OK2ZAW-17>APLG0,qAO,OK0BAF-10:=5016.90NL01625.35U7L~Ra sun Àá m
20250902211538OK2ZAW-17>APLG0,qAO,OK1KKY-17:=5016.90NL0167.37E&LoRa%&pn%DiGi
20250902212038OK2ZAW-17>APLG0,qAO,OK1KKY-17:=5016.90NL016‚´ž‘„fÕ™óXj2stLuKÇx
20250902214538OK2ZAW-17>APLG0,qAO,OK0BAF-10:=501 ML01625.35E&LoRa sun DiGi
20250902221538OK2ZAW-17>APLG0,qAO,OK1KKY-17:=501 0LL01625.35E&LoRa sun DiGiZ
20250902222038OK2ZAW-17>APLG0,qAO,OK1KKY-17:=5016.) OL01625.35E&LoRa sun DiGi