APRS Packet Errors for DD3QQ-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
20260209091937DD3QQ-12>APRSGW,TCPIP*,qAR,DD3QQ-12:!5156.57N/00736.46E#MeshCom 4#Kurt/B=100/A=000240
20260209094953DD3QQ-12>APRSGW,TCPIP*,qAR,DD3QQ-12:!5156.57N/00736.46E#MeshCom 4#Kurt/B=100/A=000240
20260209102008DD3QQ-12>APRSGW,TCPIP*,qAR,DD3QQ-12:!5156.57N/00736.46E#MeshCom 4#Kurt/B=100/A=000240
20260209105023DD3QQ-12>APRSGW,TCPIP*,qAR,DD3QQ-12:!5156.57N/00736.46E#MeshCom 4#Kurt/B=100/A=000240
20260209112041DD3QQ-12>APRSGW,TCPIP*,qAR,DD3QQ-12:!5156.57N/00736.46E#MeshCom 4#Kurt/B=100/A=000240
20260209115056DD3QQ-12>APRSGW,TCPIP*,qAR,DD3QQ-12:!5156.57N/00736.46E#MeshCom 4#Kurt/B=100/A=000240
20260209122112DD3QQ-12>APRSGW,TCPIP*,qAR,DD3QQ-12:!5156.57N/00736.46E#MeshCom 4#Kurt/B=100/A=000240
20260209125132DD3QQ-12>APRSGW,TCPIP*,qAR,DD3QQ-12:!5156.57N/00736.46E#MeshCom 4#Kurt/B=100/A=000240
20260209132148DD3QQ-12>APRSGW,TCPIP*,qAR,DD3QQ-12:!5156.57N/00736.46E#MeshCom 4#Kurt/B=100/A=000240
20260209135203DD3QQ-12>APRSGW,TCPIP*,qAR,DD3QQ-12:!5156.57N/00736.46E#MeshCom 4#Kurt/B=100/A=000240
20260209142223DD3QQ-12>APRSGW,TCPIP*,qAR,DD3QQ-12:!5156.57N/00736.46E#MeshCom 4#Kurt/B=100/A=000240
20260209145238DD3QQ-12>APRSGW,TCPIP*,qAR,DD3QQ-12:!5156.57N/00736.46E#MeshCom 4#Kurt/B=100/A=000240