APRS Packet Errors for VK4YP (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
20250509084315VK4YP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4YP-DP!28-0.00S/15300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1000 MHz
20250509092216VK4YP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4YP-DP!28-0.00S/15300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1000 MHz
20250509100033VK4YP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4YP-DP!28-0.00S/15300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1000 MHz
20250509103837VK4YP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4YP-DP!28-0.00S/15300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1000 MHz
20250509111635VK4YP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4YP-DP!28-0.00S/15300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1000 MHz
20250509115434VK4YP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4YP-DP!28-0.00S/15300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1000 MHz
20250509123234VK4YP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4YP-DP!28-0.00S/15300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1000 MHz
20250509131020VK4YP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4YP-DP!28-0.00S/15300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1000 MHz
20250509134804VK4YP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4YP-DP!28-0.00S/15300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1000 MHz
20250509142527VK4YP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK4YP-DP!28-0.00S/15300.00ErRNG0034 IPSC2-VKHOTSPOT MMDVM 439.1000 MHz