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
20190217220023EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190217221722EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190217223354EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190217225027EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190217230659EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190217232327EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190217233956EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190217235623EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190218001249EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190218002923EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190218004556EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190218010223EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190218011849EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190218013518EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190218015144EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190218020813EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190218022439EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190218024114EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190218025746EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190218031417EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190218033043EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190218034711EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz