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
20190624160836EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190624162511EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190624164148EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190624165823EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190624171457EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190624173133EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190624174813EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190624180447EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190624182121EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190624183755EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190624185433EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190624191108EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190624192743EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190624194417EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190624200055EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190624201729EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190624203403EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190624205037EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190624210714EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190624212348EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190624214023EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190624215657EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz