APRS Packet Errors for EA5SW (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
20190116112329EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116113919EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116115505EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116121052EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116122639EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116124228EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116125815EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116131402EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116132948EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116134537EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116140124EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116141724EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116143311EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116144900EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116150446EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116152033EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116153620EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116155209EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116160755EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116162345EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116163932EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116165521EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116171108EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz