APRS Packet Errors for MB6JD (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
20190319111246MB6JD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6JD-DP!5528.70N/-02-33.29rRNG0034 IPSC2-Scotland MMDVM 144.8250 MHz
20190319112948MB6JD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6JD-DP!5528.70N/-02-33.29rRNG0034 IPSC2-Scotland MMDVM 144.8250 MHz
20190319120140MB6JD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6JD-DP!5528.70N/-02-33.29rRNG0034 IPSC2-DVScotland MMDVM 144.8250 MHz
20190319121837MB6JD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6JD-DP!5528.70N/-02-33.29rRNG0034 IPSC2-DVScotland MMDVM 144.8250 MHz
20190319123547MB6JD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6JD-DP!5528.70N/-02-33.29rRNG0034 IPSC2-DVScotland MMDVM 144.8250 MHz
20190319125252MB6JD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6JD-DP!5528.70N/-02-33.29rRNG0034 IPSC2-DVScotland MMDVM 144.8250 MHz
20190319130951MB6JD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6JD-DP!5528.70N/-02-33.29rRNG0034 IPSC2-DVScotland MMDVM 144.8250 MHz
20190319132645MB6JD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6JD-DP!5528.70N/-02-33.29rRNG0034 IPSC2-DVScotland MMDVM 144.8250 MHz
20190319134341MB6JD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6JD-DP!5528.70N/-02-33.29rRNG0034 IPSC2-DVScotland MMDVM 144.8250 MHz
20190319140039MB6JD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6JD-DP!5528.70N/-02-33.29rRNG0034 IPSC2-DVScotland MMDVM 144.8250 MHz
20190319141736MB6JD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6JD-DP!5528.70N/-02-33.29rRNG0034 IPSC2-DVScotland MMDVM 144.8250 MHz
20190319143428MB6JD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6JD-DP!5528.70N/-02-33.29rRNG0034 IPSC2-DVScotland MMDVM 144.8250 MHz
20190319145119MB6JD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6JD-DP!5528.70N/-02-33.29rRNG0034 IPSC2-DVScotland MMDVM 144.8250 MHz
20190319150811MB6JD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6JD-DP!5528.70N/-02-33.29rRNG0034 IPSC2-DVScotland MMDVM 144.8250 MHz
20190319152506MB6JD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6JD-DP!5528.70N/-02-33.29rRNG0034 IPSC2-DVScotland MMDVM 144.8250 MHz
20190319155906MB6JD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6JD-DP!5528.70N/-02-33.29rRNG0034 IPSC2-DVScotland MMDVM 144.8250 MHz
20190319161601MB6JD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6JD-DP!5528.70N/-02-33.29rRNG0034 IPSC2-DVScotland MMDVM 144.8250 MHz
20190319163310MB6JD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6JD-DP!5528.70N/-02-33.29rRNG0034 IPSC2-DVScotland MMDVM 144.8250 MHz
20190319165005MB6JD>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6JD-DP!5528.70N/-02-33.29rRNG0034 IPSC2-DVScotland MMDVM 144.8250 MHz