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
20260126072829YO5ZV>APRS,WIDE2-1,qAU,DO0KB:!0000.00N/00000.00W>372 50 58 280 43 a1 d0 17
20260126073846YO5ZV>APRS,WIDE2-1,qAR,PD1RAC-10:!0000.00N/00000.00W>384 56 31 290 43 a2 d1 17
20260126073849YO5ZV>APRS,DB0OL-10*,qAR,DB0PDF-10:!0000.00N/00000.00W>384 56 31 290 43 a2 d1 17 U
20260126075535YO5ZV>APRS,DC4ML-7,WIDE2*,qAR,DB0SEP-1:!0000.00N/00000.00W>372 50 58 280 43 a1 d0 17
20260126081950YO5ZV>APRS,WIDE2-1,qAR,PD1RAC-10:!0000.00N/00000.00W>376 70 9 280 43 a6 d0 18
20260126083002YO5ZV>APRS,WIDE2-1,qAR,PD1RAC-10:!0000.00N/00000.00W>391 78 9 284 43 a7 d0 18
20260126083003YO5ZV>APRS,OK0BR-1*,qAR,OE5XIM-10:!0000.00N/00000.00W>391 78 9 284 43 a7 d0 8