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
20260516102017OK2ZAW-17>APLG0,qAO,OK1BF-10:=5016.90NL016r q3N$z`%nK
20260516103017OK2ZAW-17>APLG0,qAO,OK0BAF-10:=50!&L01629.I&oRk sun DiGi
20260516114517OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.900^==.35ůTfZtidJ
20260516115022OK2ZAW-17>APLG0,qAO,OK0BAF-10:=5016n9pNL01625.35E)Job sun DiGi:
20260516120017OK2ZAW-17>APLG0,qAS,OK1TPG-27:=501D)hcL636վvka sunG
20260516120517OK2ZAW-17>APLG0,qAO,OK1BF-10:=5016.90^n" >rL?W$9jBic)
20260516121517OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90~ܐH&LoR sun DiGi
20260516123019OK2ZAW-17>APLG0,qAO,OK1BF-10:=5016.9016snwwDO;%#u;e !
20260516125017OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90NL016"4.3%EOoRb sun DiGi
20260516125017OK2ZAW-17>APLG0,qAO,OK0BAF-10:=5016.90Pv,n8NK(]n
20260516130518OK2ZAW-17>APLG0,qAS,OK1TPG-27:=50FL01625.35EeRk sunǫ
20260516134517OK2ZAW-17>APLG0,qAO,OK0BAF-10:=5016.90NL0162 /7d*/Qq5 b
20260516135017OK2ZAW-17>APLG0,qAO,OK1BF-10:=50!..) .Y,>-SdEY iH
20260516135517OK2ZAW-17>APLG0,qAO,OK1BF-10:=5016.90NL016"4+b!/hy*%)DiGi
20260516141022OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90NL65?35$@IjRa sun@B Gi
20260516142017OK2ZAW-17>APLG0,qAO,OK1BF-10:=5016.90NL01624/"%>X#]-AG
20260516144017OK2ZAW-17>APLG0,qAS,OK1TPG-27:=50<$3Րhz"A(cw)DiGi
20260516150517OK2ZAW-17>APLG0,qAO,OK1BF-10:=5016.90NL01625.35/7 namk