APRS Packet Errors for VK4ADF (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
20250122022443VK4ADF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4ADF-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 430.1250 MHz
20250122030233VK4ADF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4ADF-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 430.1250 MHz
20250122034023VK4ADF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4ADF-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 430.1250 MHz
20250122041819VK4ADF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4ADF-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 430.1250 MHz
20250122045606VK4ADF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4ADF-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 430.1250 MHz
20250122053353VK4ADF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4ADF-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 430.1250 MHz
20250122061140VK4ADF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4ADF-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 430.1250 MHz
20250122064941VK4ADF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4ADF-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 430.1250 MHz
20250122072735VK4ADF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4ADF-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 430.1250 MHz
20250122080540VK4ADF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4ADF-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 430.1250 MHz