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
20180820162453MB7UEK-2>APBPQ1,TCPIP*,qAC,T2DENMARK:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180820164030MB7UEK-2>APBPQ1,TCPIP*,qAC,T2DENMARK:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180820165605MB7UEK-2>APBPQ1,TCPIP*,qAC,T2DENMARK:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180820171141MB7UEK-2>APBPQ1,TCPIP*,qAC,T2DENMARK:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180820172716MB7UEK-2>APBPQ1,TCPIP*,qAC,T2DENMARK:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180820174253MB7UEK-2>APBPQ1,TCPIP*,qAC,T2DENMARK:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180820175827MB7UEK-2>APBPQ1,TCPIP*,qAC,T2DENMARK:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180820181407MB7UEK-2>APBPQ1,TCPIP*,qAC,T2DENMARK:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180820182941MB7UEK-2>APBPQ1,TCPIP*,qAC,T2DENMARK:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180820184518MB7UEK-2>APBPQ1,TCPIP*,qAC,T2DENMARK:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180820190053MB7UEK-2>APBPQ1,TCPIP*,qAC,T2DENMARK:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180820191631MB7UEK-2>APBPQ1,TCPIP*,qAC,T2DENMARK:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180820193209MB7UEK-2>APBPQ1,TCPIP*,qAC,T2DENMARK:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180820194741MB7UEK-2>APBPQ1,TCPIP*,qAC,T2DENMARK:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180820200318MB7UEK-2>APBPQ1,TCPIP*,qAC,T2DENMARK:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180820201852MB7UEK-2>APBPQ1,TCPIP*,qAC,T2DENMARK:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180820203426MB7UEK-2>APBPQ1,TCPIP*,qAC,T2DENMARK:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180820205000MB7UEK-2>APBPQ1,TCPIP*,qAC,T2DENMARK:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180820210533MB7UEK-2>APBPQ1,TCPIP*,qAC,T2DENMARK:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180820212108MB7UEK-2>APBPQ1,TCPIP*,qAC,T2DENMARK:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180820213641MB7UEK-2>APBPQ1,TCPIP*,qAC,T2DENMARK:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180820215215MB7UEK-2>APBPQ1,TCPIP*,qAC,T2DENMARK:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz
20180820220748MB7UEK-2>APBPQ1,TCPIP*,qAC,T2DENMARK:;G4MKI-5 *111111z5121.46N/00105.87EI URONode [44.131.164.3] via G4MKI-3 on 144.950MHz