APRS Packet Errors for EA5RCE (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
20190421161212EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421162943EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421164647EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421172112EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421175514EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421181219EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421182917EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421184638EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421190401EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421192058EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421193756EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421195503EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88EWrRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421201153EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421202843EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421204546EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421210253EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421212013EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421213707EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz
20190421215355EA5RCE>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5RCE-DP!3955.93N/000-9.88ErRNG0034 IPSC2-EA4Master MMDVM 435.1250 MHz