APRS Packet Errors for E25IHH-2 (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
20260208151935E25IHH-2>AESPG4,TCPIP*,qAC,APRSTH:=1758.26N/10152.52ErIndy Igate
20260208154945E25IHH-2>AESPG4,TCPIP*,qAC,APRSTH:=1758.26N/10152.52ErIndy Igate
20260208155058E25IHH-2>AESPG4,TCPIP*,qAC,APRSTH:=1758.26N/10152.52ErIndy Igate
20260208162108E25IHH-2>AESPG4,TCPIP*,qAC,APRSTH:=1758.26N/10152.52ErIndy Igate
20260208165118E25IHH-2>AESPG4,TCPIP*,qAC,APRSTH:=1758.26N/10152.52ErIndy Igate
20260208172127E25IHH-2>AESPG4,TCPIP*,qAC,APRSTH:=1758.26N/10152.52ErIndy Igate
20260208175137E25IHH-2>AESPG4,TCPIP*,qAC,APRSTH:=1758.26N/10152.52ErIndy Igate
20260208182147E25IHH-2>AESPG4,TCPIP*,qAC,APRSTH:=1758.26N/10152.52ErIndy Igate
20260208185157E25IHH-2>AESPG4,TCPIP*,qAC,APRSTH:=1758.26N/10152.52ErIndy Igate
20260208192207E25IHH-2>AESPG4,TCPIP*,qAC,APRSTH:=1758.26N/10152.52ErIndy Igate
20260208195217E25IHH-2>AESPG4,TCPIP*,qAC,APRSTH:=1758.26N/10152.52ErIndy Igate
20260208202227E25IHH-2>AESPG4,TCPIP*,qAC,APRSTH:=1758.26N/10152.52ErIndy Igate
20260208205349E25IHH-2>AESPG4,TCPIP*,qAC,APRSTH:=1758.26N/10152.52ErIndy Igate