APRS Packet Errors for G4MKI-3 (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
20180523163939G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180523165500G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180523171029G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180523172551G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180523174117G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180523175639G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180523181205G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180523182724G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180523184251G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180523185810G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180523191335G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180523192852G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180523194418G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180523195937G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180523201501G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180523203021G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180523204546G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180523210106G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180523211629G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180523213147G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180523214715G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180523220233G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180523221759G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz