APRS Packet Errors for VK8MT-3 (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
20260208151218	VK8MT-3>APDW18,TCPIP*,qAC,T2SYDNEY:!1222.62SG13051.72Ea2m SDR iGate (Pi3b+)
20260208154218	VK8MT-3>APDW18,TCPIP*,qAC,T2SYDNEY:!1222.62SG13051.72Ea2m SDR iGate (Pi3b+)
20260208161218	VK8MT-3>APDW18,TCPIP*,qAC,T2SYDNEY:!1222.62SG13051.72Ea2m SDR iGate (Pi3b+)
20260208164218	VK8MT-3>APDW18,TCPIP*,qAC,T2SYDNEY:!1222.62SG13051.72Ea2m SDR iGate (Pi3b+)
20260208171218	VK8MT-3>APDW18,TCPIP*,qAC,T2SYDNEY:!1222.62SG13051.72Ea2m SDR iGate (Pi3b+)
20260208174218	VK8MT-3>APDW18,TCPIP*,qAC,T2SYDNEY:!1222.62SG13051.72Ea2m SDR iGate (Pi3b+)
20260208181218	VK8MT-3>APDW18,TCPIP*,qAC,T2SYDNEY:!1222.62SG13051.72Ea2m SDR iGate (Pi3b+)
20260208184218	VK8MT-3>APDW18,TCPIP*,qAC,T2SYDNEY:!1222.62SG13051.72Ea2m SDR iGate (Pi3b+)
20260208191218	VK8MT-3>APDW18,TCPIP*,qAC,T2SYDNEY:!1222.62SG13051.72Ea2m SDR iGate (Pi3b+)
20260208194218	VK8MT-3>APDW18,TCPIP*,qAC,T2SYDNEY:!1222.62SG13051.72Ea2m SDR iGate (Pi3b+)
20260208201218	VK8MT-3>APDW18,TCPIP*,qAC,T2SYDNEY:!1222.62SG13051.72Ea2m SDR iGate (Pi3b+)
20260208204218	VK8MT-3>APDW18,TCPIP*,qAC,T2SYDNEY:!1222.62SG13051.72Ea2m SDR iGate (Pi3b+)