APRS Packet Errors for DK8XY-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
20260208165830DK8XY-12>APRSMC,TCPIP*,qAR,DK0NDR-12:!5338.41N/01001.50E#meshcom Test#Torsten/B=100/A=000082
20260208172847DK8XY-12>APRSMC,TCPIP*,qAR,DK0NDR-12:!5338.41N/01001.50E#meshcom Test#Torsten/B=100/A=000082
20260208175850DK8XY-12>APRSMC,TCPIP*,qAR,DK0NDR-12:!5338.41N/01001.50E#meshcom Test#Torsten/B=100/A=000082
20260208182917DK8XY-12>APRSMC,TCPIP*,qAR,DK0NDR-12:!5338.41N/01001.50E#meshcom Test#Torsten/B=100/A=000082
20260208185919DK8XY-12>APRSMC,TCPIP*,qAR,DK0NDR-12:!5338.41N/01001.50E#meshcom Test#Torsten/B=100/A=000082
20260208192943DK8XY-12>APRSMC,TCPIP*,qAR,DK0NDR-12:!5338.41N/01001.50E#meshcom Test#Torsten/B=100/A=000082
20260208195956DK8XY-12>APRSMC,TCPIP*,qAR,DK0NDR-12:!5338.41N/01001.50E#meshcom Test#Torsten/B=100/A=000082
20260208213042DK8XY-12>APRSMC,TCPIP*,qAR,DK0NDR-12:!5338.41N/01001.50E#meshcom Test#Torsten/B=100/A=000082
20260208220057DK8XY-12>APRSMC,TCPIP*,qAR,DK0NDR-12:!5338.41N/01001.50E#meshcom Test#Torsten/B=100/A=000082
20260208223112DK8XY-12>APRSMC,TCPIP*,qAR,DK0NDR-12:!5338.41N/01001.50E#meshcom Test#Torsten/B=100/A=000082