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
20190221181735EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190221183359EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190221185028EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190221190653EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190221192322EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190221193948EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190221195615EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190221201241EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190221202908EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190221204534EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190221210157EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190221211822EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190221213452EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190221215120EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190221220744EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190221222409EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190221224036EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190221225700EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190221231326EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190221232947EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190221234611EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190222000236EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz