APRS Packet Errors for EA5CH (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
20190420130158EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190420131853EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190420133554EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190420135254EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190420140951EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190420142650EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190420144358EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190420150051EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190420151742EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190420153441EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190420155148EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190420160856EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190420162603EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190420164311EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190420170004EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190420171656EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190420173404EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190420175121EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190420180845EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190420182601EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190420184333EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz