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
20190421164317EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190421165951EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190421171626EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190421173301EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190421174950EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190421180626EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190421182300EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190421183935EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190421185617EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190421191254EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190421192930EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190421194603EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190421200242EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190421201916EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190421203550EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190421205225EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190421210906EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190421212544EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190421214218EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190421215850EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190421221530EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz