APRS Packet Errors for VK4CMP (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
20260402195941VK4CMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4CMP-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 442.0000 MHz
20260402203528VK4CMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4CMP-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 442.0000 MHz
20260402211114VK4CMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4CMP-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 442.0000 MHz
20260402214745VK4CMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4CMP-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 442.0000 MHz
20260402222408VK4CMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4CMP-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 442.0000 MHz
20260402230014VK4CMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4CMP-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 442.0000 MHz
20260402233638VK4CMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4CMP-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 442.0000 MHz
20260403001245VK4CMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4CMP-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 442.0000 MHz
20260403004840VK4CMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4CMP-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 442.0000 MHz
20260403012440VK4CMP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4CMP-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 442.0000 MHz