APRS Packet Errors for EB1AIR (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
20190215203727EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190215205350EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190215211011EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190215212630EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190215214248EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190215215907EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190215221528EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190215223149EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190215224809EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190215230428EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190215232050EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190215233709EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190215235328EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190216000949EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190216002612EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190216004231EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190216005850EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190216011510EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190216013134EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190216014751EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190216020410EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190216022032EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz