APRS Packet Errors for YO5ZV (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
20260224062925YO5ZV>APRS,WIDE2-1,qAR,JH0ZMR:!0000.00N/00000.00W>802 83 -23 355 43
20260224063817YO5ZV>APRS,WIDE2-1,qAR,JH0ZMR:!0000.00N/00000.00W>827 82 -29 358 43
20260224065014YO5ZV>APRS,WIDE2-1,qAR,JH0ZMR:!0000.00N/00000.00W>838 77 -49 337 43
20260224065912YO5ZV>APRS,WIDE2-1,qAR,JG1FVF:!0000.00N/00000.00W>829 74 -52 393 43
20260224070211YO5ZV>APRS,WIDE2-1,qAR,JA7IIZ-10:!0000.00N/00000.00W>822 314 399 -66 1384 0 43
20260224071405YO5ZV>APRS,WIDE2-1,qAR,JH0ZMR:!0000.00N/00000.00W>831 80 -38 337 43
20260224072642YO5ZV>APRS,WIDE2-1,qAR,JR0YBR-10:!0000.00N/00000.00W>856 70 -16 294 43
20260224073017YO5ZV>APRS,WIDE2-1,qAR,JA7IIZ-10:!0000.00N/00000.00W>823 83 -14 349 43
20260224081804YO5ZV>APRS,WIDE2-1,qAR,JR0YBR-10:!0000.00N/00000.00W>858 54 -10 275 43