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
20191015170829EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191015172340EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191015173850EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191015175400EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191015180914EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191015182425EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191015183936EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191015185447EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191015191000EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191015192511EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191015194020EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191015195531EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191015201044EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191015202556EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191015204103EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191015205612EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191015211124EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191015212633EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191015214142EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191015215651EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191015221204EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191015222713EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191015224222EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191015225730EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz