APRS Packet Errors for XE2YBI (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
20190215203510XE2YBI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2YBI-DP!5000.00N/-0300.00ErRNG0034 IPSC2-Mexico MMDVM 438.1500 MHz
20190215205137XE2YBI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2YBI-DP!5000.00N/-0300.00ErRNG0034 IPSC2-Mexico MMDVM 438.1500 MHz
20190215210759XE2YBI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2YBI-DP!5000.00N/-0300.00ErRNG0034 IPSC2-Mexico MMDVM 438.1500 MHz
20190215212436XE2YBI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2YBI-DP!5000.00N/-0300.00ErRNG0034 IPSC2-Mexico MMDVM 438.1500 MHz
20190215214101XE2YBI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2YBI-DP!5000.00N/-0300.00ErRNG0034 IPSC2-Mexico MMDVM 438.1500 MHz
20190215215731XE2YBI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2YBI-DP!5000.00N/-0300.00EWrRNG0034 IPSC2-Mexico MMDVM 438.1500 MHz
20190215221353XE2YBI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2YBI-DP!5000.00N/-0300.00ErRNG0034 IPSC2-Mexico MMDVM 438.1500 MHz
20190215223037XE2YBI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2YBI-DP!5000.00N/-0300.00ErRNG0034 IPSC2-Mexico MMDVM 438.1500 MHz