APRS Packet Errors for VK4ZZ-4 (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
20260208165827VK4ZZ-4>APU25N,TCPIP*,qAC,T2PERTH:=1917.36SG14645.94E&RX iGate 10147.6kHz
20260208172826VK4ZZ-4>APU25N,TCPIP*,qAC,T2PERTH:=1917.36SG14645.94E&RX iGate 10147.6kHz
20260208175827VK4ZZ-4>APU25N,TCPIP*,qAC,T2PERTH:=1917.36SG14645.94E&RX iGate 10147.6kHz
20260208182828VK4ZZ-4>APU25N,TCPIP*,qAC,T2PERTH:=1917.36SG14645.94E&RX iGate 10147.6kHz
20260208185828VK4ZZ-4>APU25N,TCPIP*,qAC,T2PERTH:=1917.36SG14645.94E&RX iGate 10147.6kHz
20260208192828VK4ZZ-4>APU25N,TCPIP*,qAC,T2PERTH:=1917.36SG14645.94E&RX iGate 10147.6kHz
20260208195827VK4ZZ-4>APU25N,TCPIP*,qAC,T2PERTH:=1917.36SG14645.94E&RX iGate 10147.6kHz
20260208202828VK4ZZ-4>APU25N,TCPIP*,qAC,T2PERTH:=1917.36SG14645.94E&RX iGate 10147.6kHz
20260208205828VK4ZZ-4>APU25N,TCPIP*,qAC,T2PERTH:=1917.36SG14645.94E&RX iGate 10147.6kHz
20260208212827VK4ZZ-4>APU25N,TCPIP*,qAC,T2PERTH:=1917.36SG14645.94E&RX iGate 10147.6kHz
20260208215829VK4ZZ-4>APU25N,TCPIP*,qAC,T2PERTH:=1917.36SG14645.94E&RX iGate 10147.6kHz
20260208222828VK4ZZ-4>APU25N,TCPIP*,qAC,T2PERTH:=1917.36SG14645.94E&RX iGate 10147.6kHz