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
20191023015656EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191023021206EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191023022715EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191023024226EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191023025734EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191023031242EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191023032751EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191023034431EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191023035810EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191023041351EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191023042900EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191023044411EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191023045921EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191023051430EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191023052941EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191023054451EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191023060000EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191023061510EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191023063018EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191023064531EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191023070040EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191023071549EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191023073058EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191023074610EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz