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
20180618191442MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180618192845MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180618194411MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180618195933MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180618201500MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180618203020MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180618204549MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180618210110MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180618211639MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180618213158MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180618214724MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180618220246MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180618221812MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180618223334MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180618224901MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180618230422MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180618231950MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180618233508MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180618235038MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180619000557MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180619002125MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180619003644MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180619005210MB7UEK-2>APBPQ1,TCPIP*,qAC,T2CZECH:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz