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
20190215202550EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190215204237EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190215205927EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190215211615EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190215213254EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190215214930EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190215220604EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190215222243EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190215223933EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190215225611EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190215231249EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190215232928EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190215234609EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190216000242EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190216001916EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190216003552EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190216005225EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz
20190216010852EA5GTX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GTX-DP!3806.25N/000-47.50rRNG0034 IPSC2-EA4Master MMDVM 435.5000 MHz