APRS Packet Errors for VK4GMI (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
20241223194426VK4GMI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4GMI-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 434.1500 MHz
20241223202313VK4GMI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4GMI-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 434.1500 MHz
20241223210148VK4GMI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4GMI-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 434.1500 MHz
20241223213951VK4GMI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4GMI-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 434.1500 MHz
20241223221807VK4GMI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4GMI-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 434.1500 MHz
20241223225623VK4GMI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4GMI-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 434.1500 MHz
20241223233539VK4GMI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4GMI-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 434.1500 MHz
20241224001426VK4GMI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4GMI-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 434.1500 MHz
20241224005231VK4GMI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4GMI-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 434.1500 MHz
20241224013035VK4GMI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4GMI-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 434.1500 MHz