APRS Packet Errors for VK2BRC (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
20250701002109	VK2BRC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2BRC-DP!35-0.00S/15000.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
20250701005825	VK2BRC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2BRC-DP!35-0.00S/15000.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
20250701013538	VK2BRC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2BRC-DP!35-0.00S/15000.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
20250701021324	VK2BRC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2BRC-DP!35-0.00S/15000.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
20250701025043	VK2BRC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2BRC-DP!35-0.00S/15000.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
20250701032800	VK2BRC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2BRC-DP!35-0.00S/15000.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
20250701040522	VK2BRC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2BRC-DP!35-0.00S/15000.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
20250701044252	VK2BRC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2BRC-DP!35-0.00S/15000.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz
20250701052019	VK2BRC>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2BRC-DP!35-0.00S/15000.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 438.8000 MHz