APRS Packet Errors for CT1JIB (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
20190823114731CT1JIB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)CT1JIB-DP!3835.46N/-08-55.30rRNG0034 IPSC2-BRAZIL MMDVM 430.0000@+10.0 MHz
20190823120437CT1JIB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)CT1JIB-DP!3835.46N/-08-55.30rRNG0034 IPSC2-BRAZIL MMDVM 430.0000@+10.0 MHz
20190823122142CT1JIB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)CT1JIB-DP!3835.46N/-08-55.30rRNG0034 IPSC2-BRAZIL MMDVM 430.0000@+10.0 MHz
20190823123859CT1JIB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)CT1JIB-DP!3835.46N/-08-55.30rRNG0034 IPSC2-BRAZIL MMDVM 430.0000@+10.0 MHz
20190823125613CT1JIB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)CT1JIB-DP!3835.46N/-08-55.30rRNG0034 IPSC2-BRAZIL MMDVM 430.0000@+10.0 MHz
20190823131325CT1JIB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)CT1JIB-DP!3835.46N/-08-55.30rRNG0034 IPSC2-BRAZIL MMDVM 430.0000@+10.0 MHz
20190823133024CT1JIB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)CT1JIB-DP!3835.46N/-08-55.30rRNG0034 IPSC2-BRAZIL MMDVM 430.0000@+10.0 MHz
20190823134749CT1JIB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)CT1JIB-DP!3835.46N/-08-55.30rRNG0034 IPSC2-BRAZIL MMDVM 430.0000@+10.0 MHz
20190823140507CT1JIB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)CT1JIB-DP!3835.46N/-08-55.30rRNG0034 IPSC2-BRAZIL MMDVM 430.0000@+10.0 MHz
20190823142214CT1JIB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)CT1JIB-DP!3835.46N/-08-55.30rRNG0034 IPSC2-BRAZIL MMDVM 430.0000@+10.0 MHz
20190823143926CT1JIB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)CT1JIB-DP!3835.46N/-08-55.30rRNG0034 IPSC2-BRAZIL MMDVM 430.0000@+10.0 MHz
20190823145635CT1JIB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)CT1JIB-DP!3835.46N/-08-55.30rRNG0034 IPSC2-BRAZIL MMDVM 430.0000@+10.0 MHz
20190823151346CT1JIB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)CT1JIB-DP!3835.46N/-08-55.30rRNG0034 IPSC2-BRAZIL MMDVM 430.0000@+10.0 MHz
20190823153100CT1JIB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)CT1JIB-DP!3835.46N/-08-55.30rRNG0034 IPSC2-BRAZIL MMDVM 430.0000@+10.0 MHz
20190823154807CT1JIB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)CT1JIB-DP!3835.46N/-08-55.30rRNG0034 IPSC2-BRAZIL MMDVM 430.0000@+10.0 MHz
20190823160529CT1JIB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)CT1JIB-DP!3835.46N/-08-55.30rRNG0034 IPSC2-BRAZIL MMDVM 430.0000@+10.0 MHz
20190823162234CT1JIB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)CT1JIB-DP!3835.46N/-08-55.30rRNG0034 IPSC2-BRAZIL MMDVM 430.0000@+10.0 MHz
20190823163947CT1JIB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)CT1JIB-DP!3835.46N/-08-55.30rRNG0034 IPSC2-BRAZIL MMDVM 430.0000@+10.0 MHz
20190823165653CT1JIB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)CT1JIB-DP!3835.46N/-08-55.30rRNG0034 IPSC2-BRAZIL MMDVM 430.0000@+10.0 MHz
20190823171406CT1JIB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)CT1JIB-DP!3835.46N/-08-55.30rRNG0034 IPSC2-BRAZIL MMDVM 430.0000@+10.0 MHz
20190823173115CT1JIB>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)CT1JIB-DP!3835.46N/-08-55.30rRNG0034 IPSC2-BRAZIL MMDVM 430.0000@+10.0 MHz