APRS Packet Errors for VK2RT (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
20250417151148	VK2RT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2RT-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250417154918	VK2RT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2RT-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250417162706	VK2RT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2RT-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250417170435	VK2RT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2RT-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250417174211	VK2RT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2RT-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250417182002	VK2RT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2RT-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250417185725	VK2RT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2RT-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250417193453	VK2RT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2RT-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250417201221	VK2RT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2RT-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz
20250417205020	VK2RT>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2RT-DP!27-0.00S/13300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1250 MHz