mlat.uk is built by the people who feed it. Every receiver extends the picture of the skies and seas around it, and sharing yours takes a few minutes, even with only basic Docker knowledge.
Point your feeder at feed.mlat.uk and you’re contributing. No sign-up, no keys, no email address.
MLAT positions worked out by the network appear on your own map, and your station joins the Feeders map.
Only a masked IP and an approximate location are ever shown. See the privacy policy.
Contributed data is never sold. mlat.uk is run independently, for situational awareness only.
For your own Ultrafeeder-based Docker setup.
Add the following to the environment section of the Ultrafeeder service in your docker-compose.yml:
- ULTRAFEEDER_CONFIG=
adsb,feed.mlat.uk,30004,beast_reduce_plus_out;
mlat,feed.mlat.uk,31090;
mlathub,feed.mlat.uk,30104,beast_reduce_out;
Restart the container and Ultrafeeder will forward your anonymous ADS-B data, join the mlat.uk MLAT server, and share the MLAT results it collects from other networks.
Keep a ; between every entry, including any you already have for other networks. Without it, two entries run together and the MLAT client will not start. Before joining MLAT, check your receiver’s position and station name; see the MLAT tab.
For receivers running the ADSB.im image.
adsb,feed.mlat.uk,30004,beast_reduce_plus_out;mlat,feed.mlat.uk,31090;mlathub,feed.mlat.uk,30104,beast_reduce_out;
ADSB.im will now forward your anonymous data to feed.mlat.uk and join the MLAT server. There is no separate client to install. Check that the location and site name on the ADSB.im Basic setup page are accurate, as MLAT relies on them (see the MLAT tab).
If your ADSB.im image includes AIS-Catcher / Shipfeeder integration, you can share vessel data the same way:
ais-uk-<area code>, for example ais-uk-ne1.-u feed.mlat.uk 50001
Once saved, one station contributes both aircraft and vessel data to the network.
For vessel data from Shipfeeder or AIS-Catcher. Data is sent to feed.mlat.uk on UDP port 50001.
Add the following to your docker-compose file:
- UDP_FEEDS=feed.mlat.uk:50001
-u feed.mlat.uk 50001
feed.mlat.uk50001mlat.ukNMEAOnce saved, AIS-Catcher will forward your vessel data to feed.mlat.uk. Make sure your network allows outbound UDP to port 50001.
Join the mlat.uk MLAT network to help locate aircraft that don’t broadcast their own position.
Multilateration works out an aircraft’s position from the tiny differences in when several receivers hear the same signal. It needs at least three or four stations that can see the same aircraft, so coverage grows as more people in an area join.
READSB_LAT, READSB_LON and READSB_ALT (antenna height above sea level, for example READSB_ALT=45m) to within a few metres. A wrong position breaks the timing for everyone nearby, and the server will set that station aside.MLAT_USER in the format adsb-uk-<area code>, for example adsb-uk-ne27. It can only contain letters, numbers, - and _.feed.mlat.uk.A peer is another station your station can synchronise its clock with, which means one close enough to hear many of the same aircraft, usually within about 100–300 km. If there are none yet, your station stays connected and keeps sending data, but the server has nothing to compare it with, so it cannot work out any positions. Some feeders, including ADSB.im, may then show an MLAT warning. This is normal while you are the first in your area, and it clears as other people nearby join. Your ADS-B data is not affected, and neither is MLAT on other networks you feed. The MLAT peers column on the Feeders tab shows how many peers your station has.
Add this entry to ULTRAFEEDER_CONFIG, as shown on the Ultrafeeder tab:
mlat,feed.mlat.uk,31090;
Your Ultrafeeder log should show Handshake complete and a welcome message from mlat.uk. MLAT positions then appear on your own tar1090 map as well as on mlat.uk, and your station shows an MLAT badge on the Feeders tab.
Your exact position is only used by the server for the timing calculations and is never published. On the Feeders map, MLAT stations are shown somewhere within about 5–10 km of their receiver. To leave out your station name and that approximate position (your feeder is then placed by IP address, as other feeders are), add --privacy to the entry:
mlat,feed.mlat.uk,31090,--privacy;
For experienced users pointing a feeder directly at feed.mlat.uk. Only attempt this if you are familiar with your feeder’s configuration options.
Please do not forward from another aggregator. It will break MLAT.
Protocol: BEAST
Output format: beast_reduce_plus_out
ADS-B: adsb,feed.mlat.uk,30004,beast_reduce_plus_out;
MLAT server: mlat,feed.mlat.uk,31090;
MLAT hub: mlathub,feed.mlat.uk,30104,beast_reduce_out;
AIS: feed.mlat.uk:50001
ADS-B: --net-connector feed.mlat.uk,30004,beast_reduce_plus_out
MLAT hub: --net-connector feed.mlat.uk,30104,beast_reduce_out
MLAT server (mlat-client): --server feed.mlat.uk:31090
Not yet tested. Please let me know if these work for you.
Make sure your feeder can reach feed.mlat.uk and that firewall or NAT rules allow outbound traffic on TCP ports 30004, 30104 and 31090 (MLAT), and UDP 50001 for AIS.
Within a few minutes your station appears under the Feeders tab of the Telemetry page. The end of your public IP address identifies you, with a badge for each feed received: ADS-B, MLAT, MLAT Hub and AIS.
Any changes you make to your feeder are at your own risk. mlat.uk accepts no responsibility for problems caused by applying the information on this page. Having trouble? Email [email protected].
Telemetry provided by a network of volunteer contributors, augmented with data from public sources. Data: AISHub contributors, airplanes.live, CelesTrak. For personal, non-commercial situational awareness only, supplied “as-is” without warranty. No scraping, resale or redistribution of the data or service. Privacy Policy.
Enjoying the platform? Help keep mlat.uk online by buying me a coffee.
☕ Buy me a coffee