APRS Packet Errors for DK6WH-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
20260209121151DK6WH-99>APRSMC,TCPIP*,qAR,DL2AKT-99:!5051.63N/01058.32E#MeshCom - Thueringen#Willi/B=100/A=001014
20260209124200DK6WH-99>APRSMC,TCPIP*,qAR,DL2AKT-99:!5051.63N/01058.32E#MeshCom - Thueringen#Willi/B=100/A=001014
20260209131210DK6WH-99>APRSMC,TCPIP*,qAR,DL2AKT-99:!5051.63N/01058.32E#MeshCom - Thueringen#Willi/B=100/A=001014
20260209141243DK6WH-99>APRSMC,TCPIP*,qAR,DL2AKT-99:!5051.63N/01058.32E#MeshCom - Thueringen#Willi/B=100/A=001014
20260209144302DK6WH-99>APRSMC,TCPIP*,qAR,DL2AKT-99:!5051.63N/01058.32E#MeshCom - Thueringen#Willi/B=100/A=001014
20260209151313DK6WH-99>APRSMC,TCPIP*,qAR,DL2AKT-99:!5051.63N/01058.32E#MeshCom - Thueringen#Willi/B=100/A=001014
20260209161344DK6WH-99>APRSMC,TCPIP*,qAR,DL2AKT-99:!5051.63N/01058.32E#MeshCom - Thueringen#Willi/B=100/A=001014
20260209164404DK6WH-99>APRSMC,TCPIP*,qAR,DL2AKT-99:!5051.63N/01058.32E#MeshCom - Thueringen#Willi/B=100/A=001014
20260209174439DK6WH-99>APRSMC,TCPIP*,qAR,DL2AKT-99:!5051.63N/01058.32E#MeshCom - Thueringen#Willi/B=100/A=001014