APRS Packet Errors for YO5ZM-6 (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
20260116134100YO5ZM-6>APRS,WIDE2-1,qAR,WC4PEM-12:!0000.00N/00000.00W>326 70 -72 420 44 a4 d0 83
20260116140523YO5ZM-6>APRS,WIDE2-1,qAR,KK4JMW:!0000.00N/00000.00W>343 323 83 -19 1432 0 44 a11 d0 83
20260116142946YO5ZM-6>APRS,WIDE2-1,qAR,WY2C-1:!0000.00N/00000.00W>118 82 -53 397 44
20260116144839YO5ZM-6>APRS,WIDE2-1,qAR,WY2C-1:!0000.00N/00000.00W>452 75 -95 443 43
20260116151017YO5ZM-6>APRS,WIDE2-1,qAR,K4ROM-3:!0000.00N/00000.00W>320 78 -59 403 44
20260116153153YO5ZM-6>APRS,WIDE2-1,qAR,K4ROM-3:!0000.00N/00000.00W>317 323 84 -106 1432 0 44
20260116175056YO5ZM-6>APRS,WIDE2-1,qAR,N2MH-14:!0000.00N/00000.00W>358 91 -96 442 44 a4 d0 85