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
20190116075810EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116081357EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116082946EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116084532EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116090119EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116091706EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116093255EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116094842EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116100428EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116102015EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116103604EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116105151EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116110737EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190116112330EA5SW>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
20190116134538EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz