APRS Packet Errors for DL9KX-13 (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
20260208144742DL9KX-13>APRSGW,TCPIP*,qAR,DL9KX-13:!4749.64N/01242.02E-DL9KX @ HOME/B=100/A=002136
20260208151742DL9KX-13>APRSGW,TCPIP*,qAR,DL9KX-13:!4749.64N/01242.02E-DL9KX @ HOME/B=100/A=002126
20260208154742DL9KX-13>APRSGW,TCPIP*,qAR,DL9KX-13:!4749.64N/01242.03E-DL9KX @ HOME/B=100/A=002133
20260208161742DL9KX-13>APRSGW,TCPIP*,qAR,DL9KX-13:!4749.64N/01242.03E-DL9KX @ HOME/B=100/A=002096
20260208164742DL9KX-13>APRSGW,TCPIP*,qAR,DL9KX-13:!4749.65N/01242.04E-DL9KX @ HOME/B=100/A=002100
20260208171742DL9KX-13>APRSGW,TCPIP*,qAR,DL9KX-13:!4749.64N/01242.03E-DL9KX @ HOME/B=100/A=002110
20260208174743DL9KX-13>APRSGW,TCPIP*,qAR,DL9KX-13:!4749.64N/01242.02E-DL9KX @ HOME/B=100/A=002205
20260208181743DL9KX-13>APRSGW,TCPIP*,qAR,DL9KX-13:!4749.64N/01242.03E-DL9KX @ HOME/B=100/A=002142
20260208184743DL9KX-13>APRSGW,TCPIP*,qAR,DL9KX-13:!4749.64N/01242.03E-DL9KX @ HOME/B=100/A=002182
20260208191744DL9KX-13>APRSGW,TCPIP*,qAR,DL9KX-13:!4749.64N/01242.03E-DL9KX @ HOME/B=100/A=002152
20260208194744DL9KX-13>APRSGW,TCPIP*,qAR,DL9KX-13:!4749.65N/01242.00E-DL9KX @ HOME/B=100/A=002146
20260208201744DL9KX-13>APRSGW,TCPIP*,qAR,DL9KX-13:!4749.66N/01242.02E-DL9KX @ HOME/B=100/A=002149