APRS Packet Errors for EC5ZY (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
20190220082542EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190220084232EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190220085918EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190220091600EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190220093245EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190220094930EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190220100607EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190220102249EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190220103941EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190220105637EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190220111327EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190220113028EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190220114721EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190220120405EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190220122045EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190220123727EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190220125435EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190220131114EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190220132757EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190220134433EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190220140114EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190220141749EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz