APRS Packet Errors for 443.950IA (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
20260209085812	N0GIK>APX218,TCPIP*,qAC,T2MCI:)443.950IA!/9Q(<6E5mr N0DYB AVOCA T:110
20260209092757	N0GIK>APX218,TCPIP*,qAC,T2MCI:)443.950IA!/9Q(<6E5mr N0DYB AVOCA T:110
20260209095850	N0GIK>APX218,TCPIP*,qAC,T2MCI:)443.950IA!/9Q(<6E5mr N0DYB AVOCA T:110
20260209102545	N0GIK>APX218,TCPIP*,qAC,T2MCI:)443.950IA!/9Q(<6E5mr N0DYB AVOCA T:110
20260209105024	N0GIK>APX218,TCPIP*,qAC,T2MCI:)443.950IA!/9Q(<6E5mr N0DYB AVOCA T:110
20260209112350	N0GIK>APX218,TCPIP*,qAC,T2MCI:)443.950IA!/9Q(<6E5mr N0DYB AVOCA T:110
20260209114215	N0GIK>APX218,TCPIP*,qAC,T2MCI:)443.950IA!/9Q(<6E5mr N0DYB AVOCA T:110
20260209121143	N0GIK>APX218,TCPIP*,qAC,T2MCI:)443.950IA!/9Q(<6E5mr N0DYB AVOCA T:110
20260209124435	N0GIK>APX218,TCPIP*,qAC,T2MCI:)443.950IA!/9Q(<6E5mr N0DYB AVOCA T:110
20260209131329	N0GIK>APX218,TCPIP*,qAC,T2MCI:)443.950IA!/9Q(<6E5mr N0DYB AVOCA T:110
20260209134223	N0GIK>APX218,TCPIP*,qAC,T2MCI:)443.950IA!/9Q(<6E5mr N0DYB AVOCA T:110
20260209140446	N0GIK>APX218,TCPIP*,qAC,T2MCI:)443.950IA!/9Q(<6E5mr N0DYB AVOCA T:110
20260209143448	N0GIK>APX218,TCPIP*,qAC,T2MCI:)443.950IA!/9Q(<6E5mr N0DYB AVOCA T:110