APRS Packet Errors for DL6KDS-99 (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
20260208164848	DL6KDS-99>APRSGW,TCPIP*,qAR,DL6KDS-99:!5038.10N/01100.02E-/A=001719
20260208171903	DL6KDS-99>APRSGW,TCPIP*,qAR,DL6KDS-99:!5038.10N/01100.02E-/A=001719
20260208174922	DL6KDS-99>APRSGW,TCPIP*,qAR,DL6KDS-99:!5038.10N/01100.02E-/A=001719
20260208181937	DL6KDS-99>APRSGW,TCPIP*,qAR,DL6KDS-99:!5038.10N/01100.02E-/A=001719
20260208184952	DL6KDS-99>APRSGW,TCPIP*,qAR,DL6KDS-99:!5038.10N/01100.02E-/A=001719
20260208192007	DL6KDS-99>APRSGW,TCPIP*,qAR,DL6KDS-99:!5038.10N/01100.02E-/A=001719
20260208195026	DL6KDS-99>APRSGW,TCPIP*,qAR,DL6KDS-99:!5038.10N/01100.02E-/A=001719
20260208202041	DL6KDS-99>APRSGW,TCPIP*,qAR,DL6KDS-99:!5038.10N/01100.02E-/A=001719
20260208205053	DL6KDS-99>APRSGW,TCPIP*,qAR,DL6KDS-99:!5038.10N/01100.02E-/A=001719
20260208212108	DL6KDS-99>APRSGW,TCPIP*,qAR,DL6KDS-99:!5038.10N/01100.02E-/A=001719
20260208215123	DL6KDS-99>APRSGW,TCPIP*,qAR,DL6KDS-99:!5038.10N/01100.02E-/A=001719
20260208222138	DL6KDS-99>APRSGW,TCPIP*,qAR,DL6KDS-99:!5038.10N/01100.02E-/A=001719