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
20190425050153G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190425051900G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190425053607G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190425055310G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190425061014G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190425062720G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190425064422G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190425070125G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190425071836G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190425073555G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190425075300G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190425081005G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190425082725G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190425084435G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190425090138G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190425091846G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190425093606G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190425095323G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190425101041G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190425102751G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz
20190425104455G6JUP>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)G6JUP-DP!5456.74N/-01-36.63rRNG0034 IPSC2-Scotland MMDVM 434.3000 MHz