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
20180419210404MB7UEK>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
20180419212415MB7UEK>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
20180419220437MB7UEK>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
20180419222459MB7UEK>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
20180419223454MB7UEK>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
20180419225505MB7UEK>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
20180419225515MB7UEK>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
20180419230511MB7UEK>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
20180419231517MB7UEK>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
20180419232522MB7UEK>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
20180419232532MB7UEK>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
20180419234535MB7UEK>APBPQ1,MB7UH*,WIDE3-2,qAR,M0BPQ-1:;G4MKI-11 *111111z5121.46N/00105.87EI HBXR32 X-Router Kent Coast (TCP/IP 44-Net) via G4MKI-3 on 144.950MHz
20180419235541MB7UEK>APBPQ1,MB7UH*,WIDE3-2,qAR,M0BPQ-1:;G4MKI-11 *111111z5121.46N/00105.87EI HBXR32 X-Router Kent Coast (TCP/IP 44-Net) via G4MKI-3 on 144.950MHz
20180419235550MB7UEK>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
20180420000545MB7UEK>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
20180420001550MB7UEK>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
20180420002556MB7UEK>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
20180420002608MB7UEK>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
20180420003605MB7UEK>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
20180420004609MB7UEK>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
20180420005613MB7UEK>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
20180420010619MB7UEK>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
20180420011624MB7UEK>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
20180420012630MB7UEK>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
20180420013636MB7UEK>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
20180420014641MB7UEK>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
20180420015647MB7UEK>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
20180420020653MB7UEK>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