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
20190216082307G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.62rRNG0034 IPSC2-Scotland MMDVM 434.4000 MHz
20190216083949G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.62rRNG0034 IPSC2-Scotland MMDVM 434.4000 MHz
20190216085625G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.62rRNG0034 IPSC2-Scotland MMDVM 434.4000 MHz
20190216091303G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.62rRNG0034 IPSC2-Scotland MMDVM 434.4000 MHz
20190216092942G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.62rRNG0034 IPSC2-Scotland MMDVM 434.4000 MHz
20190216094614G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.62rRNG0034 IPSC2-Scotland MMDVM 434.4000 MHz
20190216100253G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.62rRNG0034 IPSC2-Scotland MMDVM 434.4000 MHz
20190216101928G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.62rRNG0034 IPSC2-Scotland MMDVM 434.4000 MHz
20190216103607G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.62rRNG0034 IPSC2-Scotland MMDVM 434.4000 MHz
20190216105246G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.62rRNG0034 IPSC2-Scotland MMDVM 434.4000 MHz
20190216110929G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.62rRNG0034 IPSC2-Scotland MMDVM 434.4000 MHz
20190216112606G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.62rRNG0034 IPSC2-Scotland MMDVM 434.4000 MHz
20190216114246G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.62rRNG0034 IPSC2-Scotland MMDVM 434.4000 MHz
20190216115924G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.62rRNG0034 IPSC2-Scotland MMDVM 434.4000 MHz
20190216121601G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.62rRNG0034 IPSC2-Scotland MMDVM 434.4000 MHz
20190216123244G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.62rRNG0034 IPSC2-Scotland MMDVM 434.4000 MHz
20190216124930G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.62rRNG0034 IPSC2-Scotland MMDVM 434.4000 MHz
20190216130607G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.62rRNG0034 IPSC2-Scotland MMDVM 434.4000 MHz
20190216132245G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.62rRNG0034 IPSC2-Scotland MMDVM 434.4000 MHz
20190216135607G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.62rRNG0034 IPSC2-Scotland MMDVM 434.4000 MHz