APRS Packet Errors for VK4ECW (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
20250918111518	VK4ECW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4ECW-DP!2730.00S/153-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 441.0000 MHz
20250918122925	VK4ECW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4ECW-DP!2730.00S/153-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 441.0000 MHz
20250918130610	VK4ECW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4ECW-DP!2730.00S/153-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 441.0000 MHz
20250918141959	VK4ECW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4ECW-DP!2730.00S/153-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 441.0000 MHz
20250918145645	VK4ECW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4ECW-DP!2730.00S/153-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 441.0000 MHz
20250918153327	VK4ECW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4ECW-DP!2730.00S/153-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 441.0000 MHz
20250918161012	VK4ECW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4ECW-DP!2730.00S/153-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 441.0000 MHz
20250918164654	VK4ECW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4ECW-DP!2730.00S/153-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 441.0000 MHz