APRS Packet Errors for OK2ZAW-19 (last 24 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
20251013234515OK2ZAW-19>APRS,OK2PYA-2*,qAO,OK0BAF-10:!4936.50N/01605.04E_270/0p㸐"ݺ:Y,$Wkr<)E{
20251014002632OK2ZAW-19>APRS,OK2PYA-2*,qAO,OK0BAF-10:!4936:`%#!Wt
20251014005220OK2ZAW-19>APRS,OK2PYA-2*,qAO,OK0BAF-10:!4936.50N/9.04E_270/000g000t036h100b10245L338_ACU=338_ex-OL2R_fet-zaw3.0_solar+Meshtastic
20251014011808OK2ZAW-19>APRS,OK2PYA-2*,qAO,OK0BAF-10:!4936.50N/01605.p4A_4/08p
20251014012827OK2ZAW-19>APRS,OK2PYA-2*,qAO,OK0BAF-10:!493,7N5
20251014023023OK2ZAW-19>APRS,OK2PYA-2*,qAO,OK0BAF-10:!4936.50N/45.04E_270/000g001t03%h08)oV$̊O#8ul
20251014042355OK2ZAW-19>APRS,OK2PYA-2*,qAO,OK0BAF-10:!493,7"N.1&i5,T0aaf F1M7}j]0Ր
20251014043924OK2ZAW-19>APRS,OK2PYA-2*,qAO,OK0BAF-10:!4936.50N/01605.8ES470/000g001t036h10012t vEcLj5EN??bpzbw3.0_solar+Meshtasic
20251014064316OK2ZAW-19>APRS,OK2PYA-2*,qAO,OK0BAF-10:!493ƍdC+i1]Ƒ5&g
20251014094400OK2ZAW-19>APRS,OK2PYA-2*,qAO,OK0BAF-10:!493.50N/t}v8),6e7~1z0o815eb1280D337K=oi$0?–Law3^s~r)Z
20251014115823OK2ZAW-19>APRS,OK2PYA-2*,qAO,OK0BAF-10:!493N/01605.04E_270/001g002t046h100b893:L338_ACU=338_ex-OL2R_fet-zaw3.0_solar+Meshtastic