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
20190818134522EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190818140201EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190818141838EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190818143518EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190818145155EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190818150832EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190818152510EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190818154152EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190818155829EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190818161507EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190818163144EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190818164825EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190818170503EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190818172140EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190818173818EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190818175500EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190818181139EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190818182819EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190818184457EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190818190139EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190818191817EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz
20190818193455EA2BKH>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA2BKH-DP!3800.00N/-9500.00ErRNG0034 IPSC2-EA5Master MMDVM 439.0000 MHz