APRS Packet Errors for SQ5MBG-1 (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
20170820191100SQ5MBG-1>APMI04,WIDE2-2,qAR,SR5NWU:@201911z5213.46N/02122.48E_067/000g000t057r000p000P...h89b10120
20170820192601SQ5MBG-1>APMI04-1,WIDE2-2,qAR,SR5NWU:!5213.46N / 02122.48E&PGH0000DigiW1-1 + IGate U=V.
20170820201104SQ5MBG-1>APMI04-1,WIDE2-2,qAR,SR5NWU:!5213.46N / 02122.48E&PGH0000DigiW1-1 + IGate U=V.
20170820214109SQ5MBG-1>APMI04-1,WIDE2-2,qAR,SR5NWU:!5213.46N / 02122.48E&PGH0000DigiW1-1 + IGate U=V.
20170820221111SQ5MBG-1>APMI04,WIDE2-2,qAR,SR5NWU:@202211z5213.46N/02122.48E_112/000g000t055r000p000P...h91b10114
20170820224112SQ5MBG-1>APMI04,WIDE2-2,qAR,SR5NWU:@202241z5213.46N/02122.48E_112/000g000t055r000p000P...h90b10113
20170820231114SQ5MBG-1>APMI04,WIDE2-2,qAR,SR5NWU:@202311z5213.46N/02122.48E_112/000g000t055r000p000P...h91b10113
20170820232615SQ5MBG-1>APMI04,WIDE2-2,qAR,SR5NWU:@202326z5213.46N/02122.48E_112/000g000t055r000p000P...h91b10114
20170820234116SQ5MBG-1>APMI04,WIDE2-2,qAR,SR5NWU:@202341z5213.46N/02122.48E_112/000g000t055r000p000P...h91b10112
20170821001118SQ5MBG-1>APMI04,WIDE2-2,qAR,SR5NWU:@210011z5213.46N/02122.48E_112/000g000t055r000p000P...h91b10110
20170821004120SQ5MBG-1>APMI04,WIDE2-2,qAR,SR5NWU:@210041z5213.46N/02122.48E_112/000g000t056r000p000P...h91b10110