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
20191117220805EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191117222314EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191117223826EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191117225335EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191117230844EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191117232353EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191117233905EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191117235415EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191118000924EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191118002433EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191118003946EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191118005455EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191118011005EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191118012513EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191118014025EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191118015534EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191118021043EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191118022552EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191118024106EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191118025616EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191118031125EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191118032634EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191118034146EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20191118035655EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4225.85N/-08-41.74rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz