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
20191017032206EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191017033714EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191017035225EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191017040734EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191017042244EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191017043752EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191017045305EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191017050813EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191017052321EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191017053829EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191017055340EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191017060848EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191017062356EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191017063905EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191017065416EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191017070924EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191017072433EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191017073942EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191017075454EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191017081003EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191017082511EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191017084020EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191017085533EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz