APRS Packet Errors for XE2EB-10 (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
20260208152750	XE2EB-10>APU25N,TCPIP*,qAC,T2ERFURT:=2537.53N/10017.05W-XE2EB-10 IGATE PMS TLM sur MTY NL
20260208155750	XE2EB-10>APU25N,TCPIP*,qAC,T2ERFURT:=2537.53N/10017.05W-XE2EB-10 IGATE PMS TLM sur MTY NL
20260208162736	XE2EB-10>APU25N,TCPIP*,qAC,T2CSNGRAD:=2537.53N/10017.05W-XE2EB-10 IGATE PMS TLM sur MTY NL
20260208165735	XE2EB-10>APU25N,TCPIP*,qAC,T2CSNGRAD:=2537.53N/10017.05W-XE2EB-10 IGATE PMS TLM sur MTY NL
20260208172738	XE2EB-10>APU25N,TCPIP*,qAC,T2CSNGRAD:=2537.53N/10017.05W-XE2EB-10 IGATE PMS TLM sur MTY NL
20260208175738	XE2EB-10>APU25N,TCPIP*,qAC,T2CSNGRAD:=2537.53N/10017.05W-XE2EB-10 IGATE PMS TLM sur MTY NL
20260208182736	XE2EB-10>APU25N,TCPIP*,qAC,T2CSNGRAD:=2537.53N/10017.05W-XE2EB-10 IGATE PMS TLM sur MTY NL
20260208185737	XE2EB-10>APU25N,TCPIP*,qAC,T2CSNGRAD:=2537.53N/10017.05W-XE2EB-10 IGATE PMS TLM sur MTY NL
20260208192736	XE2EB-10>APU25N,TCPIP*,qAC,T2CSNGRAD:=2537.53N/10017.05W-XE2EB-10 IGATE PMS TLM sur MTY NL
20260208195737	XE2EB-10>APU25N,TCPIP*,qAC,T2CSNGRAD:=2537.53N/10017.05W-XE2EB-10 IGATE PMS TLM sur MTY NL
20260208202737	XE2EB-10>APU25N,TCPIP*,qAC,T2CSNGRAD:=2537.53N/10017.05W-XE2EB-10 IGATE PMS TLM sur MTY NL