APRS Packet Errors for YO5ZO-3 (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
20260615062116YO5ZO-3>APRS,WIDE2-1,qAR,TB4DSC-10:!0000.00N/00000.00W>596 80 25 314 43
20260615073152YO5ZO-3>APRS,WIDE2-1,qAR,SV1AMY-3:!0000.00N/00000.00W>561 74 26 315 43 m314 M135 r250
20260615074157YO5ZO-3>APRS,WIDE2-1,qAR,SV1AMY-3:!0000.00N/00000.00W>573 75 24 316 43
20260615084228YO5ZO-3>APRS,WIDE2-1,qAO,YM5SKE-10:!0000.00N/00000.00W>536 73 24 315 43
20260615085233YO5ZO-3>APRS,WIDE2-1,qAO,YM5SKE-10:!0000.00N/00000.00W>520 70 25 314 43
20260615093336YO5ZO-3>APRS,WIDE2-1,qAO,YM5SKE-10:!0000.00N/00000.00W>525 69 26 315 43
20260615094341YO5ZO-3>APRS,WIDE2-1,qAO,YM5SKE-10:!0000.00N/00000.00W>503 73 26 315 43
20260615104412YO5ZO-3>APRS,WIDE2-1,qAO,YM5SKE-10:!0000.00N/00000.00W>502 77 24 314 43 a55 d0 h32
20260615105417YO5ZO-3>APRS,WIDE2-1,qAS,YM5KKE-10:!0000.00N/00000.00W>525 72 25 314 43
20260615115448YO5ZO-3>APRS,WIDE2-1,qAO,YM5SKE-10:!0000.00N/00000.00W>578 76 23 314 43
20260615120453YO5ZO-3>APRS,WIDE2-1,qAS,YM5KKE-10:!0000.00N/00000.00W>584 87 24 315 43