APRS Packet Errors for DF4ND-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
20260208131708DF4ND-99>APRSGW,TCPIP*,qAR,DF4ND-99:!4929.16N/01040.17E#/A=001217
20260208134724DF4ND-99>APRSGW,TCPIP*,qAR,DF4ND-99:!4929.16N/01040.17E#/A=001227
20260208141739DF4ND-99>APRSGW,TCPIP*,qAR,DF4ND-99:!4929.16N/01040.18E#/A=001214
20260208144754DF4ND-99>APRSGW,TCPIP*,qAR,DF4ND-99:!4929.16N/01040.17E#/A=001214
20260208151809DF4ND-99>APRSGW,TCPIP*,qAR,DF4ND-99:!4929.16N/01040.18E#/A=001191
20260208154824DF4ND-99>APRSGW,TCPIP*,qAR,DF4ND-99:!4929.16N/01040.18E#/A=001207
20260208154850DF4ND-99>APRSMC,TCPIP*,qAR,DB0NH-3:!4929.16N/01040.18E#/A=001207
20260208161840DF4ND-99>APRSGW,TCPIP*,qAR,DF4ND-99:!4929.16N/01040.18E#/A=001217
20260208164903DF4ND-99>APRSMC,TCPIP*,qAR,DH0TG-2:!4929.17N/01040.18E#/A=001234
20260208170026DF4ND-99>APRSGW,TCPIP*,qAR,DF4ND-99:!4929.16N/01040.18E#/B=100/A=001217
20260208173041DF4ND-99>APRSGW,TCPIP*,qAR,DF4ND-99:!4929.17N/01040.18E#/B=100/A=001234
20260208183116DF4ND-99>APRSGW,TCPIP*,qAR,DF4ND-99:!4929.16N/01040.18E#/A=001214