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
20180722131137MB7UEK>APBPQ1,MB7UH*,WIDE3-2,qAR,MB7UHA:;G4MKI-11 *111111z5121.46N/00105.87EI HBXR32 X-Router Kent Coast (TCP/IP 44-Net) via G4MKI-3 on 144.950MHz
20180722131146MB7UEK>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
20180722133147MB7UEK>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
20180722134154MB7UEK>APBPQ1,MB7UH*,WIDE3-2,qAR,F1ZVV:;G4MKI-11 *111111z5121.46N/00105.87EI HBXR32 X-Router Kent Coast (TCP/IP 44-Net) via G4MKI-3 on 144.950MHz
20180722135159MB7UEK>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
20180722141210MB7UEK>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
20180722141221MB7UEK>APBPQ1,MB7UH*,WIDE3-2,qAR,F1ZVV:;G4MKI-5 *111111z5121.46N/00105.87EI HERON:G4MKI-5 Uronode 2.8 (TCP/IP 44-Net) via G4MKI-3 on 144.950MHz
20180722142216MB7UEK>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
20180722144227MB7UEK>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
20180722144238MB7UEK>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
20180722145235MB7UEK>APBPQ1,MB7UH*,WIDE3-2,qAR,MB7UHA:;G4MKI-11 *111111z5121.46N/00105.87EI HBXR32 X-Router Kent Coast (TCP/IP 44-Net) via G4MKI-3 on 144.950MHz
20180722150239MB7UEK>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
20180722151255MB7UEK>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
20180722152250MB7UEK>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
20180722155308MB7UEK>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
20180722162325MB7UEK>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
20180722174421MB7UEK>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
20180722175416MB7UEK>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
20180722180422MB7UEK>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
20180722181428MB7UEK>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