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
20190916153422EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190916154929EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190916160437EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190916161948EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190916163456EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190916165004EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190916170511EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190916172021EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190916173529EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190916175036EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190916180543EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190916182053EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190916183601EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190916185108EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190916190616EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190916192126EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190916193633EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190916195140EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190916200647EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190916202156EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190916203703EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190916205211EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190916210718EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20190916212228EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz