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
20190421103059EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190421104811EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190421110512EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190421112225EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190421113915EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190421115610EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190421121327EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190421123028EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190421124715EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190421130409EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190421132101EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190421133752EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190421135447EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190421141152EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190421142902EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190421144550EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190421150250EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190421152027EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190421153752EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190421155502EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190421161212EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz