APRS Packet Errors for DL2AKT-98 (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
20260209092717	DL2AKT-98>APRSMC,TCPIP*,qAR,DL2AKT-99:!5052.70N/01107.22E[MeshCom-Thueringen#Jens/B=100/A=001385
20260209095737	DL2AKT-98>APRSMC,TCPIP*,qAR,DL2AKT-99:!5052.70N/01107.22E[MeshCom-Thueringen#Jens/B=100/A=001385
20260209102747	DL2AKT-98>APRSMC,TCPIP*,qAR,DL2AKT-99:!5052.70N/01107.22E[MeshCom-Thueringen#Jens/B=100/A=001385
20260209105802	DL2AKT-98>APRSMC,TCPIP*,qAR,DL2AKT-99:!5052.70N/01107.22E[MeshCom-Thueringen#Jens/B=100/A=001385
20260209112817	DL2AKT-98>APRSMC,TCPIP*,qAR,DL2AKT-99:!5052.70N/01107.22E[MeshCom-Thueringen#Jens/B=100/A=001385
20260209115832	DL2AKT-98>APRSMC,TCPIP*,qAR,DL2AKT-99:!5052.70N/01107.22E[MeshCom-Thueringen#Jens/B=100/A=001385
20260209122850	DL2AKT-98>APRSMC,TCPIP*,qAR,DL2AKT-99:!5052.70N/01107.22E[MeshCom-Thueringen#Jens/B=100/A=001385
20260209125902	DL2AKT-98>APRSMC,TCPIP*,qAR,DL2AKT-99:!5052.70N/01107.22E[MeshCom-Thueringen#Jens/B=100/A=001385
20260209135942	DL2AKT-98>APRSMC,TCPIP*,qAR,DL2AKT-99:!5052.70N/01107.22E[MeshCom-Thueringen#Jens/B=088/A=001385
20260209150004	DL2AKT-98>APRSMC,TCPIP*,qAR,DL2AKT-99:!5052.70N/01107.22E[MeshCom-Thueringen#Jens/B=075/A=001385