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
20190221003527EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190221005153EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190221010824EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190221012453EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190221014121EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190221015748EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190221021418EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190221023047EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190221024715EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190221030345EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190221032014EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190221033644EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190221035312EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190221040941EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190221042610EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190221044240EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190221045907EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190221051533EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190221053204EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190221054831EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190221060503EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz
20190221062129EC5ZY>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EC5ZY-DP!3732.96N/-01-10.37rRNG0034 IPSC2-EA4Master MMDVM 144.8250 MHz