APRS Packet Errors for EA1GS (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
20191205170755EA1GS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GS-DP!4323.38N/-05-11.21rRNG0034 IPSC2-EA1Master MMDVM 436.4500 MHz
20191205172310EA1GS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GS-DP!4323.38N/-05-11.21rRNG0034 IPSC2-EA1Master MMDVM 436.4500 MHz
20191205173821EA1GS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GS-DP!4323.38N/-05-11.21rRNG0034 IPSC2-EA1Master MMDVM 436.4500 MHz
20191205175331EA1GS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GS-DP!4323.38N/-05-11.21rRNG0034 IPSC2-EA1Master MMDVM 436.4500 MHz
20191205180842EA1GS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GS-DP!4323.38N/-05-11.21rRNG0034 IPSC2-EA1Master MMDVM 436.4500 MHz
20191205182358EA1GS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GS-DP!4323.38N/-05-11.21rRNG0034 IPSC2-EA1Master MMDVM 436.4500 MHz
20191205183908EA1GS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GS-DP!4323.38N/-05-11.21rRNG0034 IPSC2-EA1Master MMDVM 436.4500 MHz
20191205185419EA1GS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GS-DP!4323.38N/-05-11.21rRNG0034 IPSC2-EA1Master MMDVM 436.4500 MHz
20191205190931EA1GS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GS-DP!4323.38N/-05-11.21rRNG0034 IPSC2-EA1Master MMDVM 436.4500 MHz
20191205192444EA1GS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GS-DP!4323.38N/-05-11.21rRNG0034 IPSC2-EA1Master MMDVM 436.4500 MHz
20191205193955EA1GS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GS-DP!4323.38N/-05-11.21rRNG0034 IPSC2-EA1Master MMDVM 436.4500 MHz
20191205195505EA1GS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GS-DP!4323.38N/-05-11.21rRNG0034 IPSC2-EA1Master MMDVM 436.4500 MHz
20191205201015EA1GS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GS-DP!4323.38N/-05-11.21rRNG0034 IPSC2-EA1Master MMDVM 436.4500 MHz
20191205202528EA1GS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GS-DP!4323.38N/-05-11.21rRNG0034 IPSC2-EA1Master MMDVM 436.4500 MHz
20191205204038EA1GS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GS-DP!4323.38N/-05-11.21rRNG0034 IPSC2-EA1Master MMDVM 436.4500 MHz
20191205205548EA1GS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GS-DP!4323.38N/-05-11.21rRNG0034 IPSC2-EA1Master MMDVM 436.4500 MHz
20191205211059EA1GS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GS-DP!4323.38N/-05-11.21rRNG0034 IPSC2-EA1Master MMDVM 436.4500 MHz
20191205212612EA1GS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GS-DP!4323.38N/-05-11.21rRNG0034 IPSC2-EA1Master MMDVM 436.4500 MHz
20191205214123EA1GS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GS-DP!4323.38N/-05-11.21rRNG0034 IPSC2-EA1Master MMDVM 436.4500 MHz
20191205215633EA1GS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GS-DP!4323.38N/-05-11.21rRNG0034 IPSC2-EA1Master MMDVM 436.4500 MHz
20191205221143EA1GS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GS-DP!4323.38N/-05-11.21rRNG0034 IPSC2-EA1Master MMDVM 436.4500 MHz
20191205222656EA1GS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GS-DP!4323.38N/-05-11.21rRNG0034 IPSC2-EA1Master MMDVM 436.4500 MHz
20191205224206EA1GS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GS-DP!4323.38N/-05-11.21rRNG0034 IPSC2-EA1Master MMDVM 436.4500 MHz
20191205225715EA1GS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA1GS-DP!4323.38N/-05-11.21rRNG0034 IPSC2-EA1Master MMDVM 436.4500 MHz