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
20190423095333EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190423101025EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190423102720EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190423104413EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190423110103EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190423111801EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190423113453EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190423115144EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190423120838EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190423122551EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190423124254EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190423125949EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190423131643EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190423133339EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190423135041EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190423140740EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190423142435EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190423144144EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190423145855EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190423151609EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190423153326EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz
20190423155102EA7JBK>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA7JBK-DP!3709.28N/-05-19.49rRNG0034 IPSC2-EA4Master MMDVM 435.1125 MHz