APRS Packet Errors for EA4GLS (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
20190319112022EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 438.5000 MHz
20190319115444EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 438.5000 MHz
20190319121146EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 438.5000 MHz
20190319122852EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 438.5000 MHz
20190319124555EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 438.5000 MHz
20190319130254EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 438.5000 MHz
20190319131952EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 438.5000 MHz
20190319133656EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 438.5000 MHz
20190319135347EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 438.5000 MHz
20190319141038EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 438.5000 MHz
20190319142738EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 438.5000 MHz
20190319144440EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 438.5000 MHz
20190319150126EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 438.5000 MHz
20190319151812EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 438.5000 MHz
20190319153506EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 438.5000 MHz
20190319155207EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 438.5000 MHz
20190319160910EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 438.5000 MHz
20190319162610EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 438.5000 MHz
20190319164308EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 438.5000 MHz
20190319170012EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 438.5000 MHz