APRS Packet Errors for VK2IPT (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
20250701071339VK2IPT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2IPT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1650@-10.0 MHz
20250701075153VK2IPT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2IPT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1650@-10.0 MHz
20250701082931VK2IPT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2IPT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1650@-10.0 MHz
20250701090740VK2IPT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2IPT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1650@-10.0 MHz
20250701094627VK2IPT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2IPT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1650@-10.0 MHz
20250701102607VK2IPT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2IPT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1650@-10.0 MHz
20250701110428VK2IPT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2IPT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1650@-10.0 MHz
20250701114157VK2IPT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2IPT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1650@-10.0 MHz
20250701121914VK2IPT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2IPT-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1650@-10.0 MHz