APRS Packet Errors for EA5AYB (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
20190116112234EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190116113833EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190116115430EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190116121036EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190116122641EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190116124234EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190116125835EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190116131425EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190116133025EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190116134620EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190116140221EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190116141819EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190116143413EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190116145015EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190116150624EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190116152219EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190116153813EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190116155405EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190116160955EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190116162547EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190116164146EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190116165745EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz
20190116171336EA5AYB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5AYB-DP!3724.92N/-01-34.56rRNG0034 IPSC2-EA1Master MMDVM 439.5000 MHz