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
20190222045405EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190222051036EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190222052706EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190222054337EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190222060013EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190222061645EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190222063316EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190222064952EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190222070627EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190222072259EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190222073939EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190222075613EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190222081300EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190222082947EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190222084640EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190222090330EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190222092016EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190222093658EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190222095343EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190222101022EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190222102705EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz
20190222104342EA5CH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5CH-DP!3825.88N/000-23.80rRNG0034 IPSC2-EA4Master MMDVM 433.4500 MHz