APRS Packet Errors for EB5ABV (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
20190624163758EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190624165433EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190624171110EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190624172744EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190624174419EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190624180053EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190624181730EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190624183405EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190624185039EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190624190713EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190624192350EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190624194024EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190624195658EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190624201332EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190624203009EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190624204643EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190624210317EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190624211951EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190624213628EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190624215303EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190624220937EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190624222611EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz