APRS Packet Errors for ASKERDE (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
20260208130805	ASKERDE>APRS,TCPIP*,qAC,T2CHILE:=3826.33N2711.59Ej TA3CHP Askerlikte kalan gün: 0
20260208133805	ASKERDE>APRS,TCPIP*,qAC,T2SYDNEY:=3826.33N2711.59Ej TA3CHP Askerlikte kalan gün: 0
20260208140805	ASKERDE>APRS,TCPIP*,qAC,T2CHILE:=3826.33N2711.59Ej TA3CHP Askerlikte kalan gün: 0
20260208143806	ASKERDE>APRS,TCPIP*,qAC,T2PERTH:=3826.33N2711.59Ej TA3CHP Askerlikte kalan gün: 0
20260208150806	ASKERDE>APRS,TCPIP*,qAC,T2CHILE:=3826.33N2711.59Ej TA3CHP Askerlikte kalan gün: 0
20260208153806	ASKERDE>APRS,TCPIP*,qAC,T2CHILE:=3826.33N2711.59Ej TA3CHP Askerlikte kalan gün: 0
20260208160806	ASKERDE>APRS,TCPIP*,qAC,T2SYDNEY:=3826.33N2711.59Ej TA3CHP Askerlikte kalan gün: 0
20260208163806	ASKERDE>APRS,TCPIP*,qAC,T2PANAMA:=3826.33N2711.59Ej TA3CHP Askerlikte kalan gün: 0
20260208170806	ASKERDE>APRS,TCPIP*,qAC,T2CHILE:=3826.33N2711.59Ej TA3CHP Askerlikte kalan gün: 0
20260208173806	ASKERDE>APRS,TCPIP*,qAC,T2PANAMA:=3826.33N2711.59Ej TA3CHP Askerlikte kalan gün: 0
20260208180806	ASKERDE>APRS,TCPIP*,qAC,T2CHILE:=3826.33N2711.59Ej TA3CHP Askerlikte kalan gün: 0
20260208183806	ASKERDE>APRS,TCPIP*,qAC,T2ROMANIA:=3826.33N2711.59Ej TA3CHP Askerlikte kalan gün: 0