APRS Packet Errors for VK8MS-DP (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
20260209115055VK8MS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK8MS-DP!1221.25S/13052.50ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20260209122723VK8MS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK8MS-DP!1221.25S/13052.50ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20260209130347VK8MS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK8MS-DP!1221.25S/13052.50ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20260209134006VK8MS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK8MS-DP!1221.25S/13052.50ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20260209141636VK8MS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK8MS-DP!1221.25S/13052.50ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20260209145241VK8MS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK8MS-DP!1221.25S/13052.50ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20260209152924VK8MS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK8MS-DP!1221.25S/13052.50ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20260209160540VK8MS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK8MS-DP!1221.25S/13052.50ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20260209164154VK8MS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK8MS-DP!1221.25S/13052.50ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz
20260209171801VK8MS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK8MS-DP!1221.25S/13052.50ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1750 MHz