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
20240518025935OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90.z
20240518030436OK2ZAW-17>APLG0,qAO,OK2CME-12:=50&90NL0162<.L&LoRa sun DiGi
20240518031437OK2ZAW-17>APLG0,qAO,OK2CME-12:=501=xt,ss`Ke:
20240518041435OK2ZAW-17>APLG0,qAS,OK1TPG-27:=50*8(oYxrC:X
20240518045435OK2ZAW-17>APLG0,qAS,OK0HCS-1:=5016.90NL01625.35&LeXs DiGi
20240518054435OK2ZAW-17>APLG0,qAS,OK1TPG-27:=50២c=^}]
20240518054936OK2ZAW-17>APLG0,qAO,OK2CME-12:=5016$90NL01625.35E&LoRa sun DiGi
20240518062435OK2ZAW-17>APLG0,qAR,OK1JRA-2:=5016.90NL01625.35u&_4d sun DiGi
20240518063435OK2ZAW-17>rcLD3,qAR,OK1JRA-2:=5016.90./e1345,35E&LoRa sun DiGi
20240518064935OK2ZAW-17>APLG0,qAO,OK2CME-12:=5016.90NL0162.M JiTg sun DiGi
20240518071435OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90 >"8~w/½Ca 
20240518072936OK2ZAW-17>APLG0,qAO,OK2CME-12:=501;L0625.35E&LoRa sun DiGi
20240518074936OK2ZAW-17>APLG0,qAO,OK2CME-12:=5016.81NL01625.35/EfRa yunDc
20240518075936OK2ZAW-17>APLG0,qAO,OK2CME-12:=501% 9OL`1325n75%_ʘ}fiBN8
20240518082935OK2ZAW-17>APLG0,qAR,OK1JRA-2:=5016.90Nl03