APRS Packet Errors for VK5DR (last 24 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
20250711123529VK5DR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5DR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
20250711131230VK5DR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5DR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
20250711134942VK5DR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5DR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
20250711142659VK5DR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5DR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
20250711150355VK5DR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5DR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
20250711154120VK5DR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5DR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
20250711161828VK5DR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5DR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
20250711165538VK5DR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5DR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
20250711173245VK5DR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5DR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
20250711181015VK5DR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5DR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
20250711192511VK5DR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5DR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
20250711200219VK5DR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5DR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
20250711203933VK5DR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5DR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
20250711211736VK5DR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5DR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
20250711215540VK5DR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5DR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
20250711231031VK5DR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5DR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
20250711234814VK5DR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5DR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
20250712002617VK5DR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5DR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
20250712010411VK5DR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5DR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
20250712033355VK5DR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5DR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
20250712041122VK5DR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5DR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
20250712044850VK5DR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5DR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
20250712052644VK5DR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5DR-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz