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
20190216080332EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190216081953EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190216083615EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190216085235EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190216091513EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190216093132EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190216094751EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190216100411EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190216102035EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190216103654EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190216105312EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190216110935EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190216112558EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190216114217EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190216115838EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190216121459EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190216123122EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190216124746EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190216130407EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190216132028EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190216133651EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz