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
20190418103724EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190418105405EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190418111042EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190418112716EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190418114354EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190418120030EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190418121703EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190418123341EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190418125017EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190418130654EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190418132330EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190418134004EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190418135647EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190418141328EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190418143009EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190418144647EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190418150328EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190418152006EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190418153642EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190418155317EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190418160956EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!0000.00N/000-0.00ErRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz