APRS Packet Errors for HP3ICC-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
20260209093418	HP3ICC-2>APHPIA,TCPIP*,qAC,T2HAKATA:=0829.15NI08225.25W#144.390MHz APRS RX-Igate
20260209100444	HP3ICC-2>APHPIA,TCPIP*,qAC,T2HAKATA:=0829.15NI08225.25W#144.390MHz APRS RX-Igate
20260209103509	HP3ICC-2>APHPIA,TCPIP*,qAC,T2HAKATA:=0829.15NI08225.25W#144.390MHz APRS RX-Igate
20260209110536	HP3ICC-2>APHPIA,TCPIP*,qAC,T2HAKATA:=0829.15NI08225.25W#144.390MHz APRS RX-Igate
20260209113607	HP3ICC-2>APHPIA,TCPIP*,qAC,T2HAKATA:=0829.15NI08225.25W#144.390MHz APRS RX-Igate
20260209120624	HP3ICC-2>APHPIA,TCPIP*,qAC,T2HAKATA:=0829.15NI08225.25W#144.390MHz APRS RX-Igate
20260209123649	HP3ICC-2>APHPIA,TCPIP*,qAC,T2HAKATA:=0829.15NI08225.25W#144.390MHz APRS RX-Igate
20260209130714	HP3ICC-2>APHPIA,TCPIP*,qAC,T2HAKATA:=0829.15NI08225.25W#144.390MHz APRS RX-Igate
20260209133740	HP3ICC-2>APHPIA,TCPIP*,qAC,T2HAKATA:=0829.15NI08225.25W#144.390MHz APRS RX-Igate
20260209140805	HP3ICC-2>APHPIA,TCPIP*,qAC,T2HAKATA:=0829.15NI08225.25W#144.390MHz APRS RX-Igate
20260209143830	HP3ICC-2>APHPIA,TCPIP*,qAC,T2HAKATA:=0829.15NI08225.25W#144.390MHz APRS RX-Igate
20260209150856	HP3ICC-2>APHPIA,TCPIP*,qAC,T2HAKATA:=0829.15NI08225.25W#144.390MHz APRS RX-Igate