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
20261021061519YO5ZD-10>APRS,WIDE2-1,qAR,PD1RAC-10:!0000.00N/00000.00W>670 43 63 46 41 m321 M116 r206
20261021061900YO5ZD-10>APRS,WIDE2-1,qAU,DO0KB:!0000.00N/00000.00W>611 44 60 287 41 m321 M116 r207
20261021063131YO5ZD-10>APRS,WIDE2-1,qAU,DO0KB:!0000.00N/00000.00W>686 55 56 141 41 a1 d0 h4
20261021064407YO5ZD-10>APRS,WIDE2-1,qAR,PD1RAC-10:!0000.00N/00000.00W>683 60 44 0 41 m321 M116 r207
20261021070125YO5ZD-10>APRS,WIDE2-1,qAR,PD1RAC-10:!0000.00N/00000.00W>702 74 40 1 41 a0 d0 h5
20261021070128YO5ZD-10>APRS,DB0OL-10*,qAR,DB0PDF-10:!0000.00N/00000.00W>702 74 40 1 41 a0 d0 h5ÇÝ
20261021071359YO5ZD-10>APRS,WIDE2-1,qAR,PD1RAC-10:!0000.00N/00000.00W>658 64 34 0 41 m321 M117 r208
20261021072635YO5ZD-10>APRS,WIDE2-1,qAR,PD1RAC-10:!0000.00N/00000.00W>685 69 29 7 41 m321 M117 r208
20261021072638YO5ZD-10>APRS,DB0OL-10*,qAR,DB0PDF-10:!0000.00N/00000.00W>685 69 29 7 41 m321 M117 r208Å
20261021074358YO5ZD-10>APRS,WIDE2-1,qAR,PD1RAC-10:!0000.00N/00000.00W>675 85 29 18 41 a0 d0 h5
20261021075638YO5ZD-10>APRS,WIDE2-1,qAR,PD1RAC-10:!0000.00N/00000.00W>697 88 27 311 41 m321 M116 r209
20261021075641YO5ZD-10>APRS,DB0OL-10*,qAR,DB0PDF-10:!0000.00N/00000.00W>697 88 27 311 41 m321 M116 r209Ì