APRS Packet Errors for EA2BKH (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
20190716060503EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190716062142EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190716063825EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190716065503EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190716071143EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190716072823EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190716074504EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190716080143EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190716081824EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190716083505EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190716085147EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190716090827EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190716092507EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190716094147EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190716095831EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190716101514EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190716103153EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190716104834EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190716110516EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190716112159EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190716113838EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190716115517EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz