APRS Packet Errors for VK3XQ-DP (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
20260209145241VK3XQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3XQ-DP!3749.89S/14518.53ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20260209152923VK3XQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3XQ-DP!3749.89S/14518.53ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20260209160540VK3XQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3XQ-DP!3749.89S/14518.53ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20260209164154VK3XQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3XQ-DP!3749.89S/14518.53ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20260209171801VK3XQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3XQ-DP!3749.89S/14518.53ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20260209175403VK3XQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3XQ-DP!3749.89S/14518.53ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20260209183005VK3XQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3XQ-DP!3749.89S/14518.53ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20260209190625VK3XQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3XQ-DP!3749.89S/14518.53ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20260209194253VK3XQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3XQ-DP!3749.89S/14518.53ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20260209201932VK3XQ>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3XQ-DP!3749.89S/14518.53ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz