APRS Packet Errors for MB7UEK-2 (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
20180621025615MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180621031144MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180621032702MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180621034228MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180621035748MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180621041314MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180621042835MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180621044359MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180621045918MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180621051444MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180621053002MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180621054529MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180621060049MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180621061619MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180621063138MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180621064703MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180621070225MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180621071750MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180621073311MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180621074837MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180621080358MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180621081927MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180621083446MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz