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
20190422170410EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422172044EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422173718EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422175355EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422181031EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422182706EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422184341EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422190018EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422191652EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422193328EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422195001EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422200637EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422202311EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422203944EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422205618EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422211300EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422212936EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422214611EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422220244EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422221921EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422223553EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190422225226EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz