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
20181212060851EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.35N/-08-41.58rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20181212062402EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.35N/-08-41.58rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20181212063909EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.35N/-08-41.58rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20181212065418EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.35N/-08-41.58rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20181212070925EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.35N/-08-41.58rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20181212072435EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.35N/-08-41.58rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20181212073943EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.35N/-08-41.58rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20181212075459EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.35N/-08-41.58rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20181212081008EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.35N/-08-41.58rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20181212082526EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.35N/-08-41.58rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20181212084043EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.35N/-08-41.58rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20181212085601EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.35N/-08-41.58rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20181212091112EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.35N/-08-41.58rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20181212092624EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.35N/-08-41.58rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20181212094134EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.35N/-08-41.58rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20181212095645EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.35N/-08-41.58rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20181212101153EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.35N/-08-41.58rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20181212102704EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.35N/-08-41.58rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20181212104219EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.35N/-08-41.58rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20181212105734EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.35N/-08-41.58rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20181212111246EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.35N/-08-41.58rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20181212112758EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.35N/-08-41.58rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20181212114309EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.35N/-08-41.58rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz
20181212115820EB1AIR>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EB1AIR-DP!4226.35N/-08-41.58rRNG0034 IPSC2-EA1Master MMDVM 439.8375 MHz