APRS Packet Errors for DA6PLH-7 (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
20260209173941	DA6PLH-7>APAT81,WIDE1-1,WIDE2-1,qAO,DB0KX-2:!5117.54N/00630.95E7000/000/A=000118Baddy Mobil by AT878
20260209174518	DA6PLH-7>APAT81,WIDE1-1,WIDE2-1,qAO,DB0KX-2:!5117.54N/00630.95E7000/000/A=000134Baddy Mobil by AT878
20260209174829	DA6PLH-7>APAT81,WIDE1-1,WIDE2-1,qAO,DB0KX-2:!5117.54N/00630.95E7000/000/A=000134Baddy Mobil by AT878
20260209175144	DA6PLH-7>APAT81,WIDE1-1,WIDE2-1,qAO,DB0KX-2:!5117.54N/00630.95E7000/000/A=000134Baddy Mobil by AT878
20260209175317	DA6PLH-7>APAT81,WIDE1-1,WIDE2-1,qAO,DB0KX-2:!5117.54N/00630.95E7000/000/A=000134Baddy Mobil by AT878
20260209175639	DA6PLH-7>APAT81,WIDE1-1,WIDE2-1,qAO,DB0KX-2:!5117.54N/00630.95E7000/000/A=000173Baddy Mobil by AT878
20260209175814	DA6PLH-7>APAT81,WIDE1-1,WIDE2-1,qAO,DB0KX-2:!5117.54N/00630.95E7000/000/A=000160Baddy Mobil by AT878
20260209175902	DA6PLH-7>APAT81,DB0KX-2,DB0OTV-2*,qAS,DB0ML-10:!5117.54N/00630.95E7000/000/A=000160Baddy Mobil by AT878
20260209175950	DA6PLH-7>APAT81,WIDE1-1,WIDE2-1,qAO,DB0KX-2:!5117.54N/00630.95E7000/000/A=000164Baddy Mobil by AT878
20260209180304	DA6PLH-7>APAT81,WIDE1-1,WIDE2-1,qAO,DB0KX-2:!5117.54N/00630.95E7000/000/A=000141Baddy Mobil by AT878