APRS Packet Errors for YO5ZX-8 (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
20260922170404YO5ZX-8>APRS,F5ZCE-1,WIDE2*,qAR,F6DDS-3:!0000.00N/00000.00W>516 68 23 307 42 a2 d0 h11
20260922171240YO5ZX-8>APRS,F4KNE-5,WIDE2*,qAR,F1PGQ-1:!0000.00N/00000.00W>496 63 34 307 42 a0 d0 h11
20260922173726YO5ZX-8>APRS,F5KTJ-3,WIDE2*,qAR,F1ZCK-3:!0000.00N/00000.00W>516 49 24 94 42 a2 d0 h11
20260922174200YO5ZX-8>APRS,F5KTJ-3,WIDE2*,qAR,F1ZFG:!0000.00N/00000.00W>520 43 60 278 42 m320 M125 r69