APRS Packet Errors for XE2ITB (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
20190423162457XE2ITB>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2ITB-DP!2800.00N/184467440rRNG0034 IPSC2-Mexico MMDVM 438.5625@-5.0 MHz
20190423164135XE2ITB>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2ITB-DP!2800.00N/184467440rRNG0034 IPSC2-Mexico MMDVM 438.5625@-5.0 MHz
20190423165814XE2ITB>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2ITB-DP!2800.00N/184467440rRNG0034 IPSC2-Mexico MMDVM 438.5625@-5.0 MHz
20190423171500XE2ITB>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2ITB-DP!2800.00N/184467440rRNG0034 IPSC2-Mexico MMDVM 438.5625@-5.0 MHz
20190423173139XE2ITB>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2ITB-DP!2800.00N/184467440rRNG0034 IPSC2-Mexico MMDVM 438.5625@-5.0 MHz
20190423174825XE2ITB>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2ITB-DP!2800.00N/184467440rRNG0034 IPSC2-Mexico MMDVM 438.5625@-5.0 MHz
20190423180505XE2ITB>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2ITB-DP!2800.00N/184467440rRNG0034 IPSC2-Mexico MMDVM 438.5625@-5.0 MHz
20190423182210XE2ITB>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2ITB-DP!2800.00N/184467440rRNG0034 IPSC2-Mexico MMDVM 438.5625@-5.0 MHz
20190423183851XE2ITB>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2ITB-DP!2800.00N/184467440rRNG0034 IPSC2-Mexico MMDVM 438.5625@-5.0 MHz
20190423185529XE2ITB>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2ITB-DP!2800.00N/184467440rRNG0034 IPSC2-Mexico MMDVM 438.5625@-5.0 MHz
20190423191211XE2ITB>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2ITB-DP!2800.00N/184467440rRNG0034 IPSC2-Mexico MMDVM 438.5625@-5.0 MHz
20190423192856XE2ITB>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2ITB-DP!2800.00N/184467440rRNG0034 IPSC2-Mexico MMDVM 438.5625@-5.0 MHz
20190423194541XE2ITB>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2ITB-DP!2800.00N/184467440rRNG0034 IPSC2-Mexico MMDVM 438.5625@-5.0 MHz
20190423200220XE2ITB>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2ITB-DP!2800.00N/184467440rRNG0034 IPSC2-Mexico MMDVM 438.5625@-5.0 MHz
20190423201858XE2ITB>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2ITB-DP!2800.00N/184467440rRNG0034 IPSC2-Mexico MMDVM 438.5625@-5.0 MHz
20190423203545XE2ITB>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2ITB-DP!2800.00N/184467440rRNG0034 IPSC2-Mexico MMDVM 438.5625@-5.0 MHz
20190423205227XE2ITB>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2ITB-DP!2800.00N/184467440rRNG0034 IPSC2-Mexico MMDVM 438.5625@-5.0 MHz
20190423210909XE2ITB>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2ITB-DP!2800.00N/184467440rRNG0034 IPSC2-Mexico MMDVM 438.5625@-5.0 MHz
20190423212549XE2ITB>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2ITB-DP!2800.00N/184467440rRNG0034 IPSC2-Mexico MMDVM 438.5625@-5.0 MHz
20190423214240XE2ITB>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2ITB-DP!2800.00N/184467440rRNG0034 IPSC2-Mexico MMDVM 438.5625@-5.0 MHz
20190423215939XE2ITB>APZDMR,QTH,TCPIP*,qAU,T2MEXICO:)XE2ITB-DP!2800.00N/184467440rRNG0034 IPSC2-Mexico MMDVM 438.5625@-5.0 MHz