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
20260126074221OK2ZAW-17>APLG0,qAO,OK1BF-10:=5016.900:>5.35&LoRр~*DiGi
20260126081723OK2ZAW-17>APLG0,qAO,OK2AF-10:=5010(90NL01625.35e gcwv K
20260126081723OK2ZAW-17>APLG0,qAO,OK2R-12:=5016.90.LVwr65.35E&LoRa sun DiGi
20260126083221OK2ZAW-17>APLG0,qAO,OK0DPH-10:=5016.90NL>85.35E&Li2!5v0z@ 
20260126093224OK2ZAW-17>APLG0,qAO,OK2AF-10:=5016"5NL241.WsDzg sun FiGI
20260126093224OK2ZAW-17>APLG0,qAO,OK2R-12:=5016.90NL0162&3uyj%%`)F
20260126094724OK2ZAW-17>APLG0,qAO,OK2AF-10:=5016.90NL01625.35@cZ  M
20260126104226OK2ZAW-17>APLG0,qAO,OK2AF-10:=501~bq&pq,aQ+S i
20260126112720OK2ZAW-17>APLG0,qAO,OK2AF-10:=501&.0 NL0162.5EvoRa sun DiGi:
20260126113220OK2ZAW-17>APLG0,qAO,OK2AF-10:=5016.90NL1%>r!D&IjWa sun wiDY
20260126114220OK2ZAW-17>APLG0,qAO,OK1KKY-17:=5016.90NL675.>{#Уǭ,b GjGi
20260126114220OK2ZAW-17>ApLG0,qAO,OK2AF-10:=501V&90NN(1625v35E|iPW#um`Aco
20260126115220OK2ZAW-17>APLG0,qAO,OK2AF-10:=501P(90NL01625.35E&oRa#sun DcGi