APRS Packet Errors for VK2KET (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
20250211074858VK2KET>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2KET-DP!32-0.00S/15100.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 430.1250 MHz
20250211082740VK2KET>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2KET-DP!32-0.00S/15100.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 430.1250 MHz
20250211090656VK2KET>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2KET-DP!32-0.00S/15100.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 430.1250 MHz
20250211094802VK2KET>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2KET-DP!32-0.00S/15100.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 430.1250 MHz
20250211095829VK2KET>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2KET-DP!32-0.00S/15100.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 430.1250 MHz
20250211103856VK2KET>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2KET-DP!32-0.00S/15100.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 430.1250 MHz
20250211111901VK2KET>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2KET-DP!32-0.00S/15100.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 430.1250 MHz
20250211115832VK2KET>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2KET-DP!32-0.00S/15100.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 430.1250 MHz
20250211123750VK2KET>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2KET-DP!32-0.00S/15100.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 430.1250 MHz
20250211131701VK2KET>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK2KET-DP!32-0.00S/15100.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 430.1250 MHz