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
20190124080339EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190124081929EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190124083522EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190124085112EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190124090700EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190124092251EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190124093844EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190124095434EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190124101023EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190124102614EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190124104207EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190124105757EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190124111346EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190124112936EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190124114528EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190124120124EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190124121714EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190124123305EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190124124858EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190124130454EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190124132043EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190124133635EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz
20190124135226EC2UW>APZDMR,QTH,TCPIP*,qAU,T2EUSKADI:)EC2UW-DP!432686700.00N/-294rRNG0034 IPSC2-EA2Master MMDVM 431.0000 MHz