APRS Packet Errors for SP6GG-9 (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
20260209092349SP6GG-9>APDW19,TCPIP*,qAC,T2PERTH:!5103.65NR01611.15E&Jawor RX iGate SP6GG 144.800MHz
20260209095349SP6GG-9>APDW19,TCPIP*,qAC,T2PERTH:!5103.65NR01611.15E&Jawor RX iGate SP6GG 144.800MHz
20260209102349SP6GG-9>APDW19,TCPIP*,qAC,T2PERTH:!5103.65NR01611.15E&Jawor RX iGate SP6GG 144.800MHz
20260209105349SP6GG-9>APDW19,TCPIP*,qAC,T2PERTH:!5103.65NR01611.15E&Jawor RX iGate SP6GG 144.800MHz
20260209112349SP6GG-9>APDW19,TCPIP*,qAC,T2PERTH:!5103.65NR01611.15E&Jawor RX iGate SP6GG 144.800MHz
20260209115349SP6GG-9>APDW19,TCPIP*,qAC,T2PERTH:!5103.65NR01611.15E&Jawor RX iGate SP6GG 144.800MHz
20260209122349SP6GG-9>APDW19,TCPIP*,qAC,T2PERTH:!5103.65NR01611.15E&Jawor RX iGate SP6GG 144.800MHz
20260209125349SP6GG-9>APDW19,TCPIP*,qAC,T2PERTH:!5103.65NR01611.15E&Jawor RX iGate SP6GG 144.800MHz
20260209132349SP6GG-9>APDW19,TCPIP*,qAC,T2PERTH:!5103.65NR01611.15E&Jawor RX iGate SP6GG 144.800MHz
20260209135349SP6GG-9>APDW19,TCPIP*,qAC,T2PERTH:!5103.65NR01611.15E&Jawor RX iGate SP6GG 144.800MHz
20260209142349SP6GG-9>APDW19,TCPIP*,qAC,T2PERTH:!5103.65NR01611.15E&Jawor RX iGate SP6GG 144.800MHz
20260209145349SP6GG-9>APDW19,TCPIP*,qAC,T2PERTH:!5103.65NR01611.15E&Jawor RX iGate SP6GG 144.800MHz