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
20260125173721OK2ZAW-17>APLG0,qAS,OK1TPG-27:=501N814w1A@¡wj DiGi
20260125174222OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90NL016
20260125180222OK2ZAW-17>APLG0,qAS,OK1TPG-27:=501.3DL5ac2=.35ELlR@u)l
20260125183221OK2ZAW-17>APLG0,qAS,OK1TPG-27:=501/81NL01625.35E&LoR&|npD99
20260125194730OK2ZAW-17>APLG0,qAO,OK1BF-10:=50q2j9tNC
20260125195221OK2ZAW-17>APLG0,qAS,OK1TPG-27:=501"90r0;T_Ac^&
20260125195721OK2ZAW-17>APLG0,qAS,OK1TPG-27:=501P.90HVP=&5M&LoRa sun DiGi
20260125200221OK2ZAW-17>APLG0,qAS,OK1TPG-27:=50qvn94Nl23b5+c0E&RQ|m
20260125203721OK2ZAW-17>APLG0,qAS,OK1TPG-27:=501,;2NL0162<.<ܿEf[asun DiGi
20260125205221OK2ZAW-17>APLG0,qAO,OK1KKY-17:=5016.90NL016"5.06E&LoRi}G c
20260125211221OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016,9LL01625.3E&LoR1% 9Thp
20260125213725OK2ZAW-17>APLG0,qAO,OK1BF-10:=5016.90HT25.35ELoRc
20260125214311OK2ZAW-17>APLG0,qAO,OK1BF-10:=501.;0NL01625.35E&LoPa sun DiGi
20260125215221OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90NL01625.35&oRk sunDai
20260125215231OK2ZAW-17>APLG0,qAO,OK1BF-10:=50qrj90JL01f<.E&LoRa sun DiGi
20260125215721OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90NL01625.3=M&LoRa sun Oi
20260125215724OK2ZAW-17>APLG0,qAO,OK1BF-10:=5016.90NL0162<.3<%FJRqx$eIGi
20260125221721OK2ZAW-17>APLG0,qAS,OK1TPG-27:=501"9006.0@i