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
20180620040505MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180620042025MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180620043554MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180620045114MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180620050641MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180620052203MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180620053731MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180620055254MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180620060822MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180620062342MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180620063915MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180620065436MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180620071009MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180620072528MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180620074058MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180620075621MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180620081150MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180620082711MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180620084238MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180620085801MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180620091328MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180620092848MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180620094419MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz