APRS Packet Errors for YO5ZD-10 (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
20260922164307YO5ZD-10>APRS,WIDE2-1,qAR,F4BQH-13:!0000.00N/00000.00W>985 65 25 318 41 a0 d0 h10
20260922165527YO5ZD-10>APRS,WIDE2-1,qAR,F5LHI-11:!0000.00N/00000.00W>978 64 21 319 41 a1 d0 h10
20260922170747YO5ZD-10>APRS,WIDE2-1,qAR,F5LHI-11:!0000.00N/00000.00W>974 67 22 319 41 a2 d1 h11
20260922170849YO5ZD-10>APRS,F6KPC-3,WIDE2*,qAR,F1ZIA:!0000.00N/00000.00W>974 67 22 319 41 a2 d1 h11
20260922171216YO5ZD-10>APRS,WIDE2-1,qAR,F5LHI-11:!0000.00N/00000.00W>944 65 25 309 41 a0 d0 h11
20260922171330YO5ZD-10>APRS,F6KPC-3,WIDE2*,qAR,F1ZIA:!0000.00N/00000.00W>944 65 25 309 41 a0 d0 h11
20260922172433YO5ZD-10>APRS,WIDE2-1,qAR,F6ZDB-3:!0000.00N/00000.00W>946 57 20 316 41 a1 d0 h11
20260922173656YO5ZD-10>APRS,WIDE2-1,qAR,F6ZDB-3:!0000.00N/00000.00W>954 48 28 311 41 a2 d0 h11
20260922173746YO5ZD-10>APRS,F6KPC-3,WIDE2*,qAR,F1ZIA:!0000.00N/00000.00W>954 48 28 311 41 a2 d0 h11
20260922174120YO5ZD-10>APRS,WIDE2-1,qAR,F4BQH-13:!0000.00N/00000.00W>924 47 51 291 41 m320 M119 r68