APRS Packet Errors for XE2CE (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
20190219173637	XE2CE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CE-DP!3200.00N/-11700.00rRNG0034 IPSC2-Mexico MMDVM 433.1500 MHz
20190219175306	XE2CE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CE-DP!3200.00N/-11700.00rRNG0034 IPSC2-Mexico MMDVM 433.1500 MHz
20190219180929	XE2CE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CE-DP!3200.00N/-11700.00rRNG0034 IPSC2-Mexico MMDVM 433.1500 MHz
20190219182553	XE2CE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CE-DP!3200.00N/-11700.00rRNG0034 IPSC2-Mexico MMDVM 433.1500 MHz
20190219203746	XE2CE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CE-DP!3200.00N/-11700.00rRNG0034 IPSC2-Mexico MMDVM 433.1500 MHz
20190219205418	XE2CE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CE-DP!3200.00N/-11700.00rRNG0034 IPSC2-Mexico MMDVM 433.1500 MHz
20190219211100	XE2CE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CE-DP!3200.00N/-11700.00rRNG0034 IPSC2-Mexico MMDVM 433.1500 MHz
20190219212730	XE2CE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CE-DP!3200.00N/-11700.00rRNG0034 IPSC2-Mexico MMDVM 433.1500 MHz
20190219223403	XE2CE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2CE-DP!3200.00N/-11700.00rRNG0034 IPSC2-Mexico MMDVM 433.1500 MHz