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
20180527233144G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180527234708G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180528000228G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180528001751G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180528003310G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180528004834G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180528010352G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180528011917G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180528013434G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180528015000G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180528022040G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180528023559G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180528025125G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180528030646G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180528032208G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180528033727G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180528035252G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180528040810G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180528042337G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180528043854G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180528045420G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180528050938G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180528052504G4MKI-3>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz