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
20190420103124G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190420104822G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190420110532G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190420112246G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190420113943G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190420115644G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190420121351G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190420123055G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190420124755G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190420130456G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190420132159G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190420133857G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190420135610G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190420141316G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190420143021G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190420144720G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190420150423G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190420152126G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190420153830G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190420155553G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190420161254G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz