APRS Packet Errors for EA5GTX (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
20190422171752EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.58N/000-47.52rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190422173443EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.58N/000-47.52rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190422175156EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.58N/000-47.52rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190422180900EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.58N/000-47.52rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190422182621EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.58N/000-47.52rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190422184313EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.58N/000-47.52rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190422190030EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.58N/000-47.52rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190422191731EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.58N/000-47.52rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190422193439EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.58N/000-47.52rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190422195126EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.58N/000-47.52rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190422200819EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.58N/000-47.52rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190422202509EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.58N/000-47.52rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190422204151EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.58N/000-47.52rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190422205840EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.58N/000-47.52rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190422211544EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.58N/000-47.52rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190422213239EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.58N/000-47.52rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190422214942EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.58N/000-47.52rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190422220635EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.58N/000-47.52rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190422222324EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.58N/000-47.52rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190422224017EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.58N/000-47.52rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190422225705EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.58N/000-47.52rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz