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
20190219090420EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190219092059EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190219093739EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190219095409EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190219101054EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190219102752EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190219104430EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190219110116EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190219111812EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190219113503EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190219115154EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190219120834EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190219122519EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190219124206EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190219125855EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190219131541EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190219133229EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190219134920EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190219140557EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190219142238EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190219143924EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz