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
20260208145353	N0GIK>APX218,TCPIP*,qAC,T2MCI:)443.950IA!/9Q(<6E5mr N0DYB AVOCA T:110
20260208152105	N0GIK>APX218,TCPIP*,qAC,T2MCI:)443.950IA!/9Q(<6E5mr N0DYB AVOCA T:110
20260208155249	N0GIK>APX218,TCPIP*,qAC,T2MCI:)443.950IA!/9Q(<6E5mr N0DYB AVOCA T:110
20260208162143	N0GIK>APX218,TCPIP*,qAC,T2MCI:)443.950IA!/9Q(<6E5mr N0DYB AVOCA T:110
20260208164946	N0GIK>APX218,TCPIP*,qAC,T2MCI:)443.950IA!/9Q(<6E5mr N0DYB AVOCA T:110
20260208171533	N0GIK>APX218,TCPIP*,qAC,T2MCI:)443.950IA!/9Q(<6E5mr N0DYB AVOCA T:110
20260208173705	N0GIK>APX218,TCPIP*,qAC,T2MCI:)443.950IA!/9Q(<6E5mr N0DYB AVOCA T:110
20260208180940	N0GIK>APX218,TCPIP*,qAC,T2MCI:)443.950IA!/9Q(<6E5mr N0DYB AVOCA T:110
20260208183055	N0GIK>APX218,TCPIP*,qAC,T2MCI:)443.950IA!/9Q(<6E5mr N0DYB AVOCA T:110
20260208185750	N0GIK>APX218,TCPIP*,qAC,T2MCI:)443.950IA!/9Q(<6E5mr N0DYB AVOCA T:110
20260208192229	N0GIK>APX218,TCPIP*,qAC,T2MCI:)443.950IA!/9Q(<6E5mr N0DYB AVOCA T:110
20260208195306	N0GIK>APX218,TCPIP*,qAC,T2MCI:)443.950IA!/9Q(<6E5mr N0DYB AVOCA T:110
20260208201346	N0GIK>APX218,TCPIP*,qAC,T2MCI:)443.950IA!/9Q(<6E5mr N0DYB AVOCA T:110