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
20190818151752EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190818153430EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190818155107EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190818160743EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190818162420EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190818164059EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190818165736EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190818171414EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190818173051EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190818174731EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190818180409EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190818182047EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190818183725EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190818185406EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190818191043EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190818192722EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190818194359EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190818200040EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190818201717EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190818203355EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190818205032EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190818210712EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz