APRS Packet Errors for G6JUP (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
20190219083529G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190219085200G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190219090833G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190219092507G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190219094143G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190219095818G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190219101446G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190219103120G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190219104753G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190219110425G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190219112101G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190219113733G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190219115401G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190219121031G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190219122749G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190219124425G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190219130102G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190219131738G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190219133408G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190219135048G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190219140719G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190219142349G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz