APRS Packet Errors for DL1ND-12 (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
20260208132829DL1ND-12>APRSMC,TCPIP*,qAR,DF4ND-99:!4928.62N/01043.39E#MeshCom GW#Klaus/B=021/A=001129
20260208135851DL1ND-12>APRSMC,TCPIP*,qAR,DF4ND-99:!4928.62N/01043.39E#MeshCom GW#Klaus/B=025/A=001129
20260208142905DL1ND-12>APRSMC,TCPIP*,qAR,DL2NEQ-1:!4928.62N/01043.39E#MeshCom GW#Klaus/B=048/A=001129
20260208145920DL1ND-12>APRSMC,TCPIP*,qAR,DL2NEQ-1:!4928.62N/01043.39E#MeshCom GW#Klaus/B=055/A=001129
20260208152933DL1ND-12>APRSMC,TCPIP*,qAR,DF4ND-99:!4928.62N/01043.39E#MeshCom GW#Klaus/B=062/A=001129
20260208155948DL1ND-12>APRSMC,TCPIP*,qAR,DF4ND-99:!4928.62N/01043.39E#MeshCom GW#Klaus/B=029/A=001129
20260208163003DL1ND-12>APRSMC,TCPIP*,qAR,DF4ND-99:!4928.62N/01043.39E#MeshCom GW#Klaus/B=040/A=001129
20260208170018DL1ND-12>APRSMC,TCPIP*,qAR,DF4ND-99:!4928.62N/01043.39E#MeshCom GW#Klaus/B=055/A=001129
20260208173036DL1ND-12>APRSMC,TCPIP*,qAR,DF4ND-99:!4928.62N/01043.39E#MeshCom GW#Klaus/B=036/A=001129
20260208180051DL1ND-12>APRSMC,TCPIP*,qAR,DF4ND-99:!4928.62N/01043.39E#MeshCom GW#Klaus/B=044/A=001129
20260208183106DL1ND-12>APRSMC,TCPIP*,qAR,DF4ND-99:!4928.62N/01043.39E#MeshCom GW#Klaus/B=044/A=001129
20260208190121DL1ND-12>APRSMC,TCPIP*,qAR,DF4ND-99:!4928.62N/01043.39E#MeshCom GW#Klaus/B=033/A=001129