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
20180522115100MB7UEK>APBPQ1,WIDE3-3,qAO,GB3EK-10:;G4MKI-11 *111111z5121.46N/00105.87EI HBXR32 X-Router Kent Coast (TCP/IP 44-Net) via G4MKI-3 on 144.950MHz
20180522121111MB7UEK>APBPQ1,WIDE3-3,qAO,GB3EK-10:;G4MKI-11 *111111z5121.46N/00105.87EI HBXR32 X-Router Kent Coast (TCP/IP 44-Net) via G4MKI-3 on 144.950MHz
20180522122117MB7UEK>APBPQ1,WIDE3-3,qAO,GB3EK-10:;G4MKI-11 *111111z5121.46N/00105.87EI HBXR32 X-Router Kent Coast (TCP/IP 44-Net) via G4MKI-3 on 144.950MHz
20180522124129MB7UEK>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
20180522125135MB7UEK>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
20180522131146MB7UEK>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
20180522133158MB7UEK>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
20180522133208MB7UEK>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
20180522134203MB7UEK>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
20180522140215MB7UEK>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
20180522141220MB7UEK>APBPQ1,WIDE3-3,qAO,GB3EK-10:;G4MKI-11 *111111z5121.46N/00105.87EI HBXR32 X-Router Kent Coast (TCP/IP 44-Net) via G4MKI-3 on 144.950MHz
20180522142226MB7UEK>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
20180522143234MB7UEK>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
20180522143243MB7UEK>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
20180522145244MB7UEK>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
20180522150300MB7UEK>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
20180522151255MB7UEK>APBPQ1,WIDE3-3,qAO,GB3EK-10:;G4MKI-11 *111111z5121.46N/00105.87EI HBXR32 X-Router Kent Coast (TCP/IP 44-Net) via G4MKI-3 on 144.950MHz
20180522153306MB7UEK>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
20180522153316MB7UEK>APBPQ1,WIDE3-3,qAO,GB3EK-10:;G4MKI-5 *111111z5121.46N/00105.87EI HERON:G4MKI-5 Uronode 2.8 (TCP/IP 44-Net) via G4MKI-3 on 144.950MHz
20180522154312MB7UEK>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
20180522155318MB7UEK>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
20180522160323MB7UEK>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
20180522160335MB7UEK>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
20180522161329MB7UEK>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
20180522162335MB7UEK>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
20180522163340MB7UEK>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
20180522163354MB7UEK>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
20180522165352MB7UEK>APBPQ1,WIDE3-3,qAO,GB3EK-10:;G4MKI-11 *111111z5121.46N/00105.87EI HBXR32 X-Router Kent Coast (TCP/IP 44-Net) via G4MKI-3 on 144.950MHz
20180522170358MB7UEK>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
20180522171403MB7UEK>APBPQ1,WIDE3-3,qAO,GB3EK-10:;G4MKI-11 *111111z5121.46N/00105.87EI HBXR32 X-Router Kent Coast (TCP/IP 44-Net) via G4MKI-3 on 144.950MHz
20180522172409MB7UEK>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
20180522173428MB7UEK>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
20180522174420MB7UEK>APBPQ1,WIDE3-3,qAO,GB3EK-10:;G4MKI-11 *111111z5121.46N/00105.87EI HBXR32 X-Router Kent Coast (TCP/IP 44-Net) via G4MKI-3 on 144.950MHz