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
20190222040826EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190222042448EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190222044110EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190222045733EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190222051357EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190222053020EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190222054645EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190222060307EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190222061932EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190222063557EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190222065219EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190222070844EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190222072513EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190222074138EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190222075801EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190222081424EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190222083050EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190222084717EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190222090344EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190222092008EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190222093638EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190222095305EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz