APRS Packet Errors for MB7UEK (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
20180423103205MB7UEK>APBPQ1,WIDE3-3,qAR,G4MKI-14:;G4MKI-11 *111111z5121.46N/00105.87EI HBXR32 X-Router Kent Coast (TCP/IP 44-Net) via G4MKI-3 on 144.950MHz
20180423111238MB7UEK>APBPQ1,WIDE3-3,qAR,G4MKI-14:;G4MKI-5 *111111z5121.46N/00105.87EI HERON:G4MKI-5 Uronode 2.8 (TCP/IP 44-Net) via G4MKI-3 on 144.950MHz
20180423113239MB7UEK>APBPQ1,WIDE3-3,qAR,G4MKI-14:;G4MKI-11 *111111z5121.46N/00105.87EI HBXR32 X-Router Kent Coast (TCP/IP 44-Net) via G4MKI-3 on 144.950MHz
20180423121313MB7UEK>APBPQ1,WIDE3-3,qAR,G4MKI-14:;G4MKI-5 *111111z5121.46N/00105.87EI HERON:G4MKI-5 Uronode 2.8 (TCP/IP 44-Net) via G4MKI-3 on 144.950MHz
20180423123314MB7UEK>APBPQ1,WIDE3-3,qAR,G4MKI-14:;G4MKI-11 *111111z5121.46N/00105.87EI HBXR32 X-Router Kent Coast (TCP/IP 44-Net) via G4MKI-3 on 144.950MHz
20180423132343MB7UEK>APBPQ1,WIDE3-3,qAR,G4MKI-14:;G4MKI-11 *111111z5121.46N/00105.87EI HBXR32 X-Router Kent Coast (TCP/IP 44-Net) via G4MKI-3 on 144.950MHz
20180423133347MB7UEK>APBPQ1,WIDE3-3,qAR,G4MKI-14:;G4MKI-11 *111111z5121.46N/00105.87EI HBXR32 X-Router Kent Coast (TCP/IP 44-Net) via G4MKI-3 on 144.950MHz
20180423144437MB7UEK>APBPQ1,WIDE3-3,qAR,G4MKI-14:;G4MKI-5 *111111z5121.46N/00105.87EI HERON:G4MKI-5 Uronode 2.8 (TCP/IP 44-Net) via G4MKI-3 on 144.950MHz