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
20190216081713EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190216083346EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190216085025EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190216090654EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190216092324EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190216094007EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190216095652EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190216101351EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190216103028EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190216104708EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190216110336EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190216112029EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190216113717EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190216115409EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190216121106EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190216122752EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190216124449EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190216130136EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190216131831EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190216133521EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz