APRS Packet Errors for MB6IYS (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
20190118160818MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190118162411MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190118164017MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190118165637MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190118171249MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190118172842MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190118174435MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190118180028MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190118181628MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190118183255MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190118184855MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190118190505MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190118192108MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190118193719MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190118195315MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190118200911MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190118202511MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190118204105MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190118205654MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190118211252MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190118212849MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190118214514MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz