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
20190818080622EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 431.1750 MHz
20190818082314EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 431.1750 MHz
20190818085705EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 431.1750 MHz
20190818091358EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 431.1750 MHz
20190818093054EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 431.1750 MHz
20190818094750EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 431.1750 MHz
20190818100442EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 431.1750 MHz
20190818102151EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 431.1750 MHz
20190818103849EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 431.1750 MHz
20190818105546EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 431.1750 MHz
20190818111244EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 431.1750 MHz
20190818112952EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 431.1750 MHz
20190818114658EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 431.1750 MHz
20190818120400EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 431.1750 MHz
20190818122102EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 431.1750 MHz
20190818123803EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 431.1750 MHz
20190818125501EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 431.1750 MHz
20190818131152EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 431.1750 MHz
20190818132853EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 431.1750 MHz
20190818134551EA4GLS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4GLS-DP!3843.56N/-05-32.77rRNG0034 IPSC2-EA4Master MMDVM 431.1750 MHz