APRS Packet Errors for EA5GSD (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
20190418190221EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3800.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190418191920EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3800.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190418193626EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3800.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190418195335EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3800.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190418201025EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3800.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190418202718EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3800.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190418204408EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3800.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190418210058EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3800.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190418211749EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3800.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz
20190418213450EA5GSD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5GSD-DP!3800.00N/000-0.00ErRNG0034 IPSC2-EA4Master MMDVM 430.4750 MHz