APRS Packet Errors for YO5ZX-12 (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
20260416140612YO5ZX-12>APRS,WIDE2-1,qAR,UB3AVW-1:!0000.00N/00000.00W>920 80 20 318 42
20260416141716YO5ZX-12>APRS,WIDE2-1,qAR,UB3AVW-1:!0000.00N/00000.00W>889 85 23 321 42
20260416151230YO5ZX-12>APRS,WIDE2-1,qAS,UB3IBX-2:!0000.00N/00000.00W>877 317 78 19 1286 0 42 2
20260416152324YO5ZX-12>APRS,WIDE2-1,qAR,UB3AVW-1:!0000.00N/00000.00W>875 74 22 316 42