APRS Packet Errors for VK5OG (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
20250715201806	VK5OG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5OG-DP!00-0.00N/00002.40ErRNG0034 IPSC2-VKHOTSPOT MMDVM 440.0000 MHz
20250715205536	VK5OG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5OG-DP!00-0.00N/00002.40ErRNG0034 IPSC2-VKHOTSPOT MMDVM 440.0000 MHz
20250715213339	VK5OG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5OG-DP!00-0.00N/00002.40ErRNG0034 IPSC2-VKHOTSPOT MMDVM 440.0000 MHz
20250715221122	VK5OG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5OG-DP!00-0.00N/00002.40ErRNG0034 IPSC2-VKHOTSPOT MMDVM 440.0000 MHz
20250715224912	VK5OG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5OG-DP!00-0.00N/00002.40ErRNG0034 IPSC2-VKHOTSPOT MMDVM 440.0000 MHz
20250715232653	VK5OG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5OG-DP!00-0.00N/00002.40ErRNG0034 IPSC2-VKHOTSPOT MMDVM 440.0000 MHz
20250716000425	VK5OG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5OG-DP!00-0.00N/00002.40ErRNG0034 IPSC2-VKHOTSPOT MMDVM 440.0000 MHz
20250716004148	VK5OG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5OG-DP!00-0.00N/00002.40ErRNG0034 IPSC2-VKHOTSPOT MMDVM 440.0000 MHz
20250716011949	VK5OG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5OG-DP!00-0.00N/00002.40ErRNG0034 IPSC2-VKHOTSPOT MMDVM 440.0000 MHz
20250716015746	VK5OG>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK5OG-DP!00-0.00N/00002.40ErRNG0034 IPSC2-VKHOTSPOT MMDVM 440.0000 MHz