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
20191017231217EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20191017232723EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20191017234229EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20191017235738EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20191018001245EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20191018002751EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20191018004258EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20191018005807EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20191018011313EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20191018012820EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20191018014326EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20191018015835EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20191018021342EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20191018022848EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20191018024354EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20191018025904EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20191018031410EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20191018032916EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20191018034423EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20191018035932EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20191018041439EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20191018042945EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20191018044452EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz
20191018050001EB5ABV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB5ABV-DP!3837.38N/000-34.50rRNG0034 IPSC2-EA-RPTR MMDVM 430.4125 MHz