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
20200527191615EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!42438400.00N/00841rRNG0034 IPSC2-EA1Master MMDVM 431.0375 MHz
20200527194631EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!42438400.00N/00841rRNG0034 IPSC2-EA1Master MMDVM 431.0375 MHz
20200527201649EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!42438400.00N/00841rRNG0034 IPSC2-EA1Master MMDVM 431.0375 MHz
20200527204704EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!42438400.00N/00841rRNG0034 IPSC2-EA1Master MMDVM 431.0375 MHz
20200527211721EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!42438400.00N/00841rRNG0034 IPSC2-EA1Master MMDVM 431.0375 MHz
20200527214738EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!42438400.00N/00841rRNG0034 IPSC2-EA1Master MMDVM 431.0375 MHz
20200527221754EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!42438400.00N/00841rRNG0034 IPSC2-EA1Master MMDVM 431.0375 MHz
20200527224809EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!42438400.00N/00841rRNG0034 IPSC2-EA1Master MMDVM 431.0375 MHz
20200527231822EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!42438400.00N/00841rRNG0034 IPSC2-EA1Master MMDVM 431.0375 MHz
20200527234835EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!42438400.00N/00841rRNG0034 IPSC2-EA1Master MMDVM 431.0375 MHz