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
20260124050222OK2ZAW-17>APLG0,qAS,OK1TPG-27:=50149N pq665>34*ϒa"Wun
20260124053722OK2ZAW-17>APLG0,qAO,OK1BF-10:=5016.90NL016>5.35E&LoRa sun @iGi
20260124055222OK2ZAW-17>APLG0,qAO,OK0DPH-10:=5016.90NL01623=u%_ba sun DGc
20260124063222OK2ZAW-17>APLG0,qAO,OK1BF-10:=5016.90NL016GFeR(sunpP,^
20260124064222OK2ZAW-17>ATLG0,qAO,OK1BF-10:=5016.90..45.35E&LoRa sun!G
20260124070222OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016$90DL01625.35E&/A qUn"GiBz
20260124074721OK2ZAW-17>APLG0,qAR,OK1KUN-2:=50181.*6W65 d(tf EhWi
20260124080722OK2ZAW-17>APLG0,qAR,OK1KUN-2:=5015 3ML01625>3%D&LoRas DiGi
20260124081721OK2ZAW-17>APLG0,qAS,OK1TPG-27:=5016.90NL01625.35oRh sun DiGi
20260124084722OK2ZAW-17>APLG0,qAS,OK1TPG-27:=50n(0N 1735>3E,oRb sun DNi
20260124084722OK2ZAW-17>APLG0,qAS,OK1CMJ-15:=5016.90NL0162<.3
20260124090227OK2ZAW-17>APLG0,qAO,OK2R-12:=5016.90Όj1_smnrucjT>U
20260124091221OK2ZAW-17>APLG0,qAR,OK1KUN-2:=5016,9,*0105*MJ=%%O!
20260124091222OK2ZAW-17>APLG0,qAO,OK1BF-10:=5016.90L0395E&LoRa sun DiGi