APRS Packet Errors for YD3ADB-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
20260209150213	YD3ADB-10>APDW18,qAR,YH3NPX-2:!0717.49S11246.87E#PHG2230UKDC-ORARI APRS IGATE
20260209153212	YD3ADB-10>APDW18,qAR,YH3NPX-2:!0717.49S11246.87E#PHG2230UKDC-ORARI APRS IGATE
20260209160212	YD3ADB-10>APDW18,qAR,YH3NPX-2:!0717.49S11246.87E#PHG2230UKDC-ORARI APRS IGATE
20260209163212	YD3ADB-10>APDW18,qAR,YH3NPX-2:!0717.49S11246.87E#PHG2230UKDC-ORARI APRS IGATE
20260209170213	YD3ADB-10>APDW18,qAR,YH3NPX-2:!0717.49S11246.87E#PHG2230UKDC-ORARI APRS IGATE
20260209173212	YD3ADB-10>APDW18,qAR,YH3NPX-2:!0717.49S11246.87E#PHG2230UKDC-ORARI APRS IGATE
20260209180212	YD3ADB-10>APDW18,qAR,YH3NPX-2:!0717.49S11246.87E#PHG2230UKDC-ORARI APRS IGATE
20260209183213	YD3ADB-10>APDW18,qAR,YH3NPX-2:!0717.49S11246.87E#PHG2230UKDC-ORARI APRS IGATE
20260209190212	YD3ADB-10>APDW18,qAR,YH3NPX-2:!0717.49S11246.87E#PHG2230UKDC-ORARI APRS IGATE
20260209193212	YD3ADB-10>APDW18,qAR,YH3NPX-2:!0717.49S11246.87E#PHG2230UKDC-ORARI APRS IGATE
20260209200213	YD3ADB-10>APDW18,qAR,YH3NPX-2:!0717.49S11246.87E#PHG2230UKDC-ORARI APRS IGATE
20260209203213	YD3ADB-10>APDW18,qAR,YH3NPX-2:!0717.49S11246.87E#PHG2230UKDC-ORARI APRS IGATE