APRS Packet Errors for VK7DAN (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
20251221235820	VK7DAN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK7DAN-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20251222003448	VK7DAN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK7DAN-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20251222011110	VK7DAN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK7DAN-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20251222014725	VK7DAN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK7DAN-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20251222022344	VK7DAN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK7DAN-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20251222030004	VK7DAN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK7DAN-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20251222033613	VK7DAN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK7DAN-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz
20251222041218	VK7DAN>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK7DAN-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1500 MHz