APRS Packet Errors for DF4ND-24 (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
20260209120501DF4ND-24>APRSMC,TCPIP*,qAR,DH0TG-2:!4929.17N/01040.16E#/B=100/A=001398
20260209123516DF4ND-24>APRSMC,TCPIP*,qAR,DF4ND-99:!4929.17N/01040.16E#/B=100/A=001398
20260209130532DF4ND-24>APRSMC,TCPIP*,qAR,DL2NEQ-1:!4929.17N/01040.16E#/B=022/A=001398
20260209133551DF4ND-24>APRSMC,TCPIP*,qAR,DF4ND-99:!4929.17N/01040.16E#/A=001398
20260209140600DF4ND-24>APRSMC,TCPIP*,qAR,DH0TG-2:!4929.17N/01040.16E#/B=100/A=001398
20260209143615DF4ND-24>APRSMC,TCPIP*,qAR,DL2NEQ-1:!4929.17N/01040.16E#/B=100/A=001398
20260209150630DF4ND-24>APRSMC,TCPIP*,qAR,DF4ND-99:!4929.17N/01040.16E#/B=093/A=001398
20260209153647DF4ND-24>APRSMC,TCPIP*,qAR,DL2NEQ-1:!4929.17N/01040.16E#/B=100/A=001398
20260209160705DF4ND-24>APRSMC,TCPIP*,qAR,DF4ND-99:!4929.17N/01040.16E#/B=100/A=001398
20260209163715DF4ND-24>APRSMC,TCPIP*,qAR,DF4ND-99:!4929.17N/01040.16E#/B=100/A=001398
20260209170728DF4ND-24>APRSMC,TCPIP*,qAR,DL2NEQ-1:!4929.17N/01040.16E#/B=100/A=001398
20260209173742DF4ND-24>APRSMC,TCPIP*,qAR,DF4ND-99:!4929.17N/01040.16E#/A=001398