APRS Packet Errors for VK2XG (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
20250330184529	VK2XG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2XG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 430.1250@+19.4 MHz
20250330192436	VK2XG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2XG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 430.1250@+19.4 MHz
20250330200315	VK2XG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2XG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 430.1250@+19.4 MHz
20250330204249	VK2XG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2XG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 430.1250@+19.4 MHz
20250330212225	VK2XG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2XG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 430.1250@+19.4 MHz
20250330220224	VK2XG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2XG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 430.1250@+19.4 MHz
20250330224148	VK2XG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2XG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 430.1250@+19.4 MHz
20250330232155	VK2XG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2XG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 430.1250@+19.4 MHz
20250331000059	VK2XG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2XG-DP!5000.00N/003-0.00WrRNG0034 IPSC2-VKHOTSPOT MMDVM 430.1250@+19.4 MHz