APRS Packet Errors for DL5XL-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
20260209122523DL5XL-4>APLRG1,WIDE1-1,qAO,DB0OL-12:!L3PO
20260209122528DL5XL-4>APLRG1,DB0OL-10*,qAR,DB0PDF-10:!L3PO
20260209132524DL5XL-4>APLRG1,WIDE1-1,qAO,DB0OL-12:!L3PO
20260209132528DL5XL-4>APLRG1,DB0OL-10*,qAR,DB0PDF-10:!L3PO
20260209142528DL5XL-4>APLRG1,WIDE1-1,qAO,DB0OL-12:!L3PO
20260209142532DL5XL-4>APLRG1,DB0OL-10*,qAR,DB0PDF-10:!L3PO
20260209152529DL5XL-4>APLRG1,WIDE1-1,qAS,DG4BRT-11:!L3PO
20260209162532DL5XL-4>APLRG1,WIDE1-1,qAR,DB0BHV-L4:!L3PO
20260209172533DL5XL-4>APLRG1,WIDE1-1,qAS,DG4BRT-11:!L3PO
20260209172536DL5XL-4>APLRG1,DB0OL-10*,qAR,DB0PDF-10:!L3PO