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
20190217162540EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190217164217EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190217165856EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190217171556EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190217173242EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190217174940EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190217180620EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190217182252EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190217183954EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190217185655EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190217191339EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190217193014EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190217194654EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190217200345EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190217202017EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190217203651EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190217205322EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190217211002EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190217212641EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190217214312EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190217220023EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz