APRS Packet Errors for YO5ZP-6 (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
20260126072250YO5ZP-6>APRS,WIDE2-1,qAR,PD1RAC-10:!0000.00N/00000.00W>957 51 59 279 43 a1 d0 15
20260126072253YO5ZP-6>APRS,DB0OL-10*,qAR,DB0PDF-10:!0000.00N/00000.00W>957 51 59 279 43 a1 d0 151B
20260126073307YO5ZP-6>APRS,WIDE2-1,qAO,DB0RSR-10:!0000.00N/00000.00W>962 53 52 286 43 a2 d0 15
20260126080412YO5ZP-6>APRS,WIDE2-1,qAR,PD1RAC-10:!0000.00N/00000.00W>887 76 16 324 43 a6 d4 15
20260126080433YO5ZP-6>APRS,WIDE2-1,qAR,PD1RAC-10:!0000.00N/00000.00W>877 76 16 323 43 a7 d5 15
20260126080434YO5ZP-6>APRS,OK0BR-1*,qAR,OE5XIM-10:!0000.00N/00000.00W>8;7 /6 16 323 43 a7 d5 15
20260126085604YO5ZP-6>APRS,WIDE2-1,qAR,PD1RAC-10:!0000.00N/00000.00W>756 314 16 17 1395 0 43 2
20260126090618YO5ZP-6>APRS,WIDE2-1,qAR,PD1RAC-10:!0000.00N/00000.00W>889 88 19 315 43