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
20190318235627EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190319001252EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190319002917EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190319004542EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190319010209EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190319011834EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190319013459EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190319015124EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190319020753EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190319022418EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190319024043EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190319025709EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190319031336EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190319033001EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190319034626EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190319040250EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190319041918EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190319043543EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190319045208EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190319050832EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190319052501EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz
20190319054127EA5SW>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5SW-DP!3917.40N/000-13.80rRNG0034 IPSC2-EA5Master MMDVM 439.9625 MHz