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
20190422063202EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422064833EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422070509EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422072142EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422073817EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422075626EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422081302EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422082937EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422084609EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422090253EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422091928EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422093604EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422095239EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422100915EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422102547EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422104223EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422105900EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422105900EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 430.4625 MHz
20190422111537EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422111538EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 430.4625 MHz
20190422113212EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422113212EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 430.4625 MHz
20190422114847EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422114847EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 430.4625 MHz
20190422120530EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz