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
20190719225906EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.82N/-08-41.10rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190719231555EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.82N/-08-41.10rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190719233239EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.82N/-08-41.10rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190719234925EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.82N/-08-41.10rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190720000614EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.82N/-08-41.10rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190720002304EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.82N/-08-41.10rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190720003949EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.82N/-08-41.10rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190720005636EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.82N/-08-41.10rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190720011327EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.82N/-08-41.10rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190720013015EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.82N/-08-41.10rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190720014700EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.82N/-08-41.10rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190720020345EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.82N/-08-41.10rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190720022033EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.82N/-08-41.10rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190720023716EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.82N/-08-41.10rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190720025400EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.82N/-08-41.10rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190720031046EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.82N/-08-41.10rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190720032731EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.82N/-08-41.10rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190720034416EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.82N/-08-41.10rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190720040100EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.82N/-08-41.10rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190720041745EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.82N/-08-41.10rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190720043433EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.82N/-08-41.10rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20190720045117EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.82N/-08-41.10rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz