APRS Packet Errors for VK2EDY (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
20251018020004VK2EDY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2EDY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.7000 MHz
20251018023719VK2EDY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2EDY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.7000 MHz
20251018031430VK2EDY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2EDY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.7000 MHz
20251018035105VK2EDY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2EDY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.7000 MHz
20251018042829VK2EDY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2EDY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.7000 MHz
20251018050521VK2EDY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2EDY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.7000 MHz
20251018054205VK2EDY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2EDY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.7000 MHz
20251018061904VK2EDY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2EDY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.7000 MHz
20251018065526VK2EDY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2EDY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.7000 MHz
20251018073230VK2EDY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2EDY-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 438.7000 MHz