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
20190222010813MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190222012437MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190222014058MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190222015722MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190222021345MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190222023007MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190222024628MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190222030256MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190222031919MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190222033540MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190222035202MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190222040826MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190222042448MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190222044110MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190222045733MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190222051357MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190222053020MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190222054645MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190222060307MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190222061932MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190222063557MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz
20190222065219MB6IYS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)MB6IYS-DP!5057.06N/-02-36.72rRNG0034 IPSC2-EA1Master MMDVM 431.0875 MHz