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
20190118170146EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190118171755EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190118173422EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190118175037EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190118180642EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190118182245EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190118183920EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190118185622EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190118191300EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190118192916EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190118194532EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190118200154EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190118201759EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190118203410EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190118205025EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190118210632EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190118212231EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190118213838EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190118215438EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190118221046EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190118222652EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190118224250EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz