APRS Packet Errors for YO5ZB-4 (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
20250717155721YO5ZB-4>APRS,WIDE2-1,qAR,DB0AFU-10:!0000.00N/00000.00W>796 339 426 1179 239 41 240 a0 rt240
20250717160430YO5ZB-4>APRS,WIDE2-1,qAS,DL9LAF:!0000.00N/00000.00W>791 74 -35 25 41 a1 rt240
20250717161254YO5ZB-4>APRS,WIDE2-1,qAR,PD1RAC-10:!0000.00N/00000.00W>783 79 -36 25 41 a2 rt240
20250717180242YO5ZB-4>APRS,WIDE2-1,qAR,DB0ELB:!0000.00N/00000.00W>794 339 427 1180 239 41 240 a0 rt240
20250717180950YO5ZB-4>APRS,WIDE2-1,qAS,DL9LAF:!0000.00N/00000.00W>813 59 -26 25 41 a1 rt240
20250717181814YO5ZB-4>APRS,WIDE2-1,qAR,DB0PCH:!0000.00N/00000.00W>837 70 -26 25 41 a2 rt240
20250717181905YO5ZB-4>APRS,OZ9DIM-1,WIDE2*,qAR,OZ1IEP-3:!0000.00N/00000.00W>837 70 -26 25 41 a2 rt240
20250717200710YO5ZB-4>APRS,DB0LSB-1,WIDE2*,qAR,DB0HBS:!0000.00N/00000.00W>758 339 428 1177 239 41 240 a0 rt240
20250717201520YO5ZB-4>APRS,WIDE2-1,qAR,DG5IBS-4:!0000.00N/00000.00W>727 32 25 25 41 a1 rt240
20250717202502YO5ZB-4>APRS,WIDE2-1,qAR,DG5IBS-4:!0000.00N/00000.00W>732 32 33 0 41 a2 rt240
20250717202542YO5ZB-4>APRS,DB0OL-10*,qAR,DB0PDF-10:!0000.00N/00000.00W>732 32 33 0 41 a2 rt240Mę
20250717202542YO5ZB-4>APRS,DB0OL-10*,qAR,DB0WHV:!0000.00N/00000.00W>732 32 33 0 41 a2 rt240