APRS Packet Errors for N0GIK (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
20260208150018N0GIK>APX218,TCPIP*,qAC,T2MCI:=4136.03N/09401.19Wx
20260208153019N0GIK>APX218,TCPIP*,qAC,T2MCI:=4136.03N/09401.19Wx
20260208160020N0GIK>APX218,TCPIP*,qAC,T2MCI:=4136.03N/09401.19Wx
20260208163021N0GIK>APX218,TCPIP*,qAC,T2MCI:=4136.03N/09401.19Wx
20260208170022N0GIK>APX218,TCPIP*,qAC,T2MCI:=4136.03N/09401.19Wx
20260208173023N0GIK>APX218,TCPIP*,qAC,T2MCI:=4136.03N/09401.19Wx
20260208180024N0GIK>APX218,TCPIP*,qAC,T2MCI:=4136.03N/09401.19Wx
20260208183025N0GIK>APX218,TCPIP*,qAC,T2MCI:=4136.03N/09401.19Wx
20260208190026N0GIK>APX218,TCPIP*,qAC,T2MCI:=4136.03N/09401.19Wx
20260208193027N0GIK>APX218,TCPIP*,qAC,T2MCI:=4136.03N/09401.19Wx
20260208200028N0GIK>APX218,TCPIP*,qAC,T2MCI:=4136.03N/09401.19Wx
20260208203029N0GIK>APX218,TCPIP*,qAC,T2MCI:=4136.03N/09401.19Wx