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
20260206143910YO5ZV>APRS,WIDE2-1,qAO,DB0RSR-10:!0000.00N/00000.00W>393 92 -29 276 43
20260206144210YO5ZV>APRS,WIDE2-1,qAU,DO0KB:!0000.00N/00000.00W>400 91 -29 363 43
20260206150011YO5ZV>APRS,WIDE2-1,qAR,DB0OFI:!0000.00N/00000.00W>391 314 161 -28 1358 0 43
20260206150311YO5ZV>APRS,WIDE2-1,qAO,DB0RSR-10:!0000.00N/00000.00W>399 78 -28 276 43
20260206150517YO5ZV>APRS,DB0VOX,WIDE2-1*,qAO,DF1GP-10:!0000.00N/00000.00W>399 78 -28 276 43
20260206151553YO5ZV>APRS,WIDE2-1,qAO,DL1NUX-1:!0000.00N/00000.00W>405 81 -29 362 43
20260206151852YO5ZV>APRS,WIDE2-1,qAO,DB0RSR-10:!0000.00N/00000.00W>412 80 -28 365 43
20260206153650YO5ZV>APRS,WIDE2-1,qAO,DB0RSR-10:!0000.00N/00000.00W>399 80 -28 299 43
20260206153950YO5ZV>APRS,WIDE2-1,qAR,DB0EB-10:!0000.00N/00000.00W>409 78 -27 260 43
20260206155513YO5ZV>APRS,WIDE2-1,qAO,DB0RSR-10:!0000.00N/00000.00W>398 72 -23 265 43
20260206155812YO5ZV>APRS,WIDE2-1,qAO,DB0RSR-10:!0000.00N/00000.00W>399 314 162 -24 1358 0 43
20260206163702YO5ZV>APRS,WIDE2-1,qAR,DB0HAS-10:!0000.00N/00000.00W>376 27 -6 172 43
20260206171415YO5ZV>APRS,WIDE2-1,qAR,DB0EB-10:!0000.00N/00000.00W>374 314 164 20 1358 0 43
20260206195928YO5ZV>APRS,WIDE2-1,qAR,SR3NOW:!0000.00N/00000.00W>404 314 166 31 1358 0 43