APRS Packet Errors for EA7JBK (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
20190419065000EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190419065001EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 434.4500 MHz
20190419070654EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190419070654EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 434.4500 MHz
20190419072353EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190419072353EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 434.4500 MHz
20190419074100EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190419074100EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 434.4500 MHz
20190419075825EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190419075825EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 434.4500 MHz
20190419081537EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190419081537EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 434.4500 MHz
20190419083245EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190419083245EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 434.4500 MHz
20190419084946EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190419084946EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 434.4500 MHz
20190419090700EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190419090700EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 434.4500 MHz
20190419092416EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190419092416EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 434.4500 MHz
20190419094127EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190419094127EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 434.4500 MHz
20190419095841EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190419101558EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190419103317EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz