APRS Packet Errors for EC2UW (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
20190116090952EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!4315.06N/-02-54.78rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190116092542EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!4315.06N/-02-54.78rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190116094130EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!4315.06N/-02-54.78rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190116095717EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!4315.06N/-02-54.78rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190116101305EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!4315.06N/-02-54.78rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190116102856EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!4315.06N/-02-54.78rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190116104442EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!4315.06N/-02-54.78rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190116110030EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!4315.06N/-02-54.78rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190116111617EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!4315.06N/-02-54.78rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190116113208EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!4315.06N/-02-54.78rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190116114756EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!4315.06N/-02-54.78rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190116120344EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!4315.06N/-02-54.78rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190116121931EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!4315.06N/-02-54.78rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190116123522EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!4315.06N/-02-54.78rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190116125109EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!4315.06N/-02-54.78rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190116130656EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!4315.06N/-02-54.78rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190116132244EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!4315.06N/-02-54.78rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190116133834EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!4315.06N/-02-54.78rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190116135422EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!4315.06N/-02-54.78rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190116141010EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!4315.06N/-02-54.78rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190116142558EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!4315.06N/-02-54.78rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190116144148EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!4315.06N/-02-54.78rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190116145736EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!4315.06N/-02-54.78rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz