APRS Packet Errors for VK2TIM (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
20241121083323VK2TIM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2TIM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 431.9500 MHz
20241121091207VK2TIM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2TIM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 431.9500 MHz
20241121094953VK2TIM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2TIM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 431.9500 MHz
20241121102809VK2TIM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2TIM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 431.9500 MHz
20241121110618VK2TIM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2TIM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 431.9500 MHz
20241121114405VK2TIM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2TIM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 431.9500 MHz
20241121122143VK2TIM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2TIM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 431.9500 MHz
20241121125859VK2TIM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2TIM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 431.9500 MHz
20241121133554VK2TIM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2TIM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 431.9500 MHz
20241121141310VK2TIM>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2TIM-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 431.9500 MHz