APRS Packet Errors for YO5ZT-9 (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
20260922164428YO5ZT-9>APRS,WIDE2-1,qAR,HB9HSN-10:!0000.00N/00000.00W>258 68 21 322 42 a0 d0 h11
20260922165648YO5ZT-9>APRS,WIDE2-1,qAR,F4FEB-13:!0000.00N/00000.00W>222 65 21 321 42 m320 M122 r116
20260922170904YO5ZT-9>APRS,WIDE2-1,qAR,F1PGQ-1:!0000.00N/00000.00W>239 61 23 322 42 a2 d1 h11
20260922170939YO5ZT-9>APRS,F5ZQD-3,WIDE2*,qAR,F1GRH-10:!0000.00N/00000.00W>239 61 23 322 42 a2 d1 h11
20260922171331YO5ZT-9>APRS,WIDE2-1,qAR,F1PGQ-1:!0000.00N/00000.00W>218 60 29 316 42 m320 M122 r117
20260922172547YO5ZT-9>APRS,WIDE2-1,qAR,F1PGQ-1:!0000.00N/00000.00W>226 56 24 319 42 a1 d0 h11
20260922173810YO5ZT-9>APRS,WIDE2-1,qAR,F1PGQ-1:!0000.00N/00000.00W>200 49 28 180 42 m320 M122 r117
20260922174231YO5ZT-9>APRS,WIDE2-1,qAR,F6ZDB-3:!0000.00N/00000.00W>200 45 59 0 42 a0 d0 h11