APRS Packet Errors for XE2BVI (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
20240518145824	XE2BVI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2BVI-DP!5000.00N/003-0.00WrRNG0034 IPSC2-Mexico MMDVM 435.1500 MHz
20240518152854	XE2BVI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2BVI-DP!5000.00N/003-0.00WrRNG0034 IPSC2-Mexico MMDVM 435.1500 MHz
20240518155922	XE2BVI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2BVI-DP!5000.00N/003-0.00WrRNG0034 IPSC2-Mexico MMDVM 435.1500 MHz
20240518162951	XE2BVI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2BVI-DP!5000.00N/003-0.00WrRNG0034 IPSC2-Mexico MMDVM 435.1500 MHz
20240518170020	XE2BVI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2BVI-DP!5000.00N/003-0.00WrRNG0034 IPSC2-Mexico MMDVM 435.1500 MHz
20240518173049	XE2BVI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2BVI-DP!5000.00N/003-0.00WrRNG0034 IPSC2-Mexico MMDVM 435.1500 MHz
20240518180119	XE2BVI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2BVI-DP!5000.00N/003-0.00WrRNG0034 IPSC2-Mexico MMDVM 435.1500 MHz
20240518183149	XE2BVI>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)XE2BVI-DP!5000.00N/003-0.00WrRNG0034 IPSC2-Mexico MMDVM 435.1500 MHz