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
20260209104747DL9KX-13>APRSGW,TCPIP*,qAR,DL9KX-13:!4749.64N/01242.04E-DL9KX @ HOME/B=100/A=002152
20260209111747DL9KX-13>APRSGW,TCPIP*,qAR,DL9KX-13:!4749.64N/01242.04E-DL9KX @ HOME/B=100/A=002113
20260209114747DL9KX-13>APRSGW,TCPIP*,qAR,DL9KX-13:!4749.64N/01242.03E-DL9KX @ HOME/B=100/A=002156
20260209121747DL9KX-13>APRSGW,TCPIP*,qAR,DL9KX-13:!4749.64N/01242.03E-DL9KX @ HOME/B=100/A=002103
20260209124748DL9KX-13>APRSGW,TCPIP*,qAR,DL9KX-13:!4749.64N/01242.02E-DL9KX @ HOME/B=100/A=002149
20260209131748DL9KX-13>APRSGW,TCPIP*,qAR,DL9KX-13:!4749.64N/01242.02E-DL9KX @ HOME/B=100/A=002185
20260209134748DL9KX-13>APRSGW,TCPIP*,qAR,DL9KX-13:!4749.64N/01242.02E-DL9KX @ HOME/B=100/A=002133
20260209141748DL9KX-13>APRSGW,TCPIP*,qAR,DL9KX-13:!4749.64N/01242.02E-DL9KX @ HOME/B=100/A=002156
20260209144748DL9KX-13>APRSGW,TCPIP*,qAR,DL9KX-13:!4749.64N/01242.04E-DL9KX @ HOME/B=100/A=002182
20260209151748DL9KX-13>APRSGW,TCPIP*,qAR,DL9KX-13:!4749.64N/01242.03E-DL9KX @ HOME/B=100/A=002159
20260209154748DL9KX-13>APRSGW,TCPIP*,qAR,DL9KX-13:!4749.64N/01242.03E-DL9KX @ HOME/B=100/A=002178
20260209161749DL9KX-13>APRSGW,TCPIP*,qAR,DL9KX-13:!4749.64N/01242.03E-DL9KX @ HOME/B=100/A=002149