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
20190217221322EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190217222944EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190217224605EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190217230225EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190217231843EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190217233502EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190217235124EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190218000742EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190218002402EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190218004022EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190218005643EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190218011302EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190218012921EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190218014540EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190218020200EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190218021817EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190218023435EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190218025052EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190218030715EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190218032334EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190218033953EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190218035610EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.34N/-08-41.52rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz