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
20190216235249EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190217000908EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190217002529EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190217004144EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190217005803EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190217011424EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190217013051EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190217014705EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190217020317EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190217021938EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190217023624EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190217025251EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190217030930EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190217032605EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190217034232EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190217035858EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190217041525EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190217043152EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190217044816EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190217050440EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190217052106EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190217053735EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz