APRS Packet Errors for VK3TUL (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
20251101042957VK3TUL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3TUL-DP!37424800.00N/14585rRNG0034 IPSC2-VKHOTSPOT MMDVM 433.5000 MHz
20251101050610VK3TUL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3TUL-DP!37424800.00N/14585rRNG0034 IPSC2-VKHOTSPOT MMDVM 433.5000 MHz
20251101054214VK3TUL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3TUL-DP!37424800.00N/14585rRNG0034 IPSC2-VKHOTSPOT MMDVM 433.5000 MHz
20251101061816VK3TUL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3TUL-DP!37424800.00N/14585rRNG0034 IPSC2-VKHOTSPOT MMDVM 433.5000 MHz
20251101065419VK3TUL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3TUL-DP!37424800.00N/14585rRNG0034 IPSC2-VKHOTSPOT MMDVM 433.5000 MHz
20251101073025VK3TUL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3TUL-DP!37424800.00N/14585rRNG0034 IPSC2-VKHOTSPOT MMDVM 433.5000 MHz
20251101080641VK3TUL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3TUL-DP!37424800.00N/14585rRNG0034 IPSC2-VKHOTSPOT MMDVM 433.5000 MHz
20251101084248VK3TUL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3TUL-DP!37424800.00N/14585rRNG0034 IPSC2-VKHOTSPOT MMDVM 433.5000 MHz
20251101091904VK3TUL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3TUL-DP!37424800.00N/14585rRNG0034 IPSC2-VKHOTSPOT MMDVM 433.5000 MHz
20251101095522VK3TUL>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)VK3TUL-DP!37424800.00N/14585rRNG0034 IPSC2-VKHOTSPOT MMDVM 433.5000 MHz