Key takeaways
- Decoder and feeder are two different things: The decoder reads the SDR stick, the feeder sends the data to a service. Only one program can use the stick at a time – all other feeders attach to its data stream.
- fr24feed and PiAware come with their own decoders: Both work on their own, but can also dock onto a decoder that is already running. RBFeeder, the Plane Finder client and the ADS-B Exchange scripts are designed from the start to read along.
- Local interfaces differ greatly: PiAware shows a live map with SkyAware, fr24feed a status page on port 8754, pfclient a web interface on port 30053. The best-looking local map is usually delivered by tar1090.
- All-in-one solutions save work: The adsb.im image and the Ultrafeeder container supply dozens of networks from one interface or one configuration file, respectively – including the commercial services.
- What you get in return depends on the service, not the program: Whether you run fr24feed the classic way or in a container does not matter – what counts is that the station is linked to your account and delivers.
Contents
- 1.The short answer
- 2.First, understand: decoder, feeder, interface
- 3.fr24feed (Flightradar24)
- 4.PiAware (FlightAware)
- 5.RBFeeder (AirNav Radar)
- 6.Plane Finder client (pfclient)
- 7.ADS-B Exchange and the community networks
- 8.All-in-one solutions: adsb.im and Ultrafeeder
- 9.All programs compared
- 10.Which variant suits you?
- 11.Typical pitfalls in parallel operation
- 12.Range beats software
- 13.Conclusion
Your Raspberry Pi hangs by the skylight, the SDR stick is slightly hot, and the first Mode S messages are rushing through the console. Now comes the question every station operator has at some point: which feeder program do you install – and how many of them? Flightradar24, FlightAware, AirNav Radar, Plane Finder, ADS-B Exchange and OpenSky each have their own software, and there are all-in-one solutions that do everything at once. This comparison looks under the hood: how do the programs work, what do they show you locally, how do they get along with each other and what reward is behind each service?
Your antenna listens in – Planetrack collects what you see
In Planetrack you post every sighting with photo, aircraft type, registration, airline, airport and spot and file it in your hangar. Planetrack is launching soon – join the waitlist and get early access.
The short answer
For a single network, you use the service’s official program: PiAware for FlightAware, fr24feed for Flightradar24. Both come with their own decoder and run after a few minutes. For several networks, you build on a neutral decoder such as readsb and attach RBFeeder, the Plane Finder client, fr24feed and the ADS-B Exchange scripts to it. If you want to spare yourself the command line, reach for the adsb.im image with a web interface; if you like Docker, the Ultrafeeder container. Which subscriptions you get as a feeder is independent of the type of installation; the details are in What feeders get in return.
First, understand: decoder, feeder, interface
Before you compare programs, it helps to look at the division of labor on your Pi. At the very bottom sits the decoder. It controls the SDR stick, evaluates the signals on 1090 MHz and turns them into messages with identifier, position, altitude and speed. Well-known decoders are dump1090-fa (part of PiAware) and readsb. On top of that sit the feeders: small programs that tap the decoder’s data stream and send it, encrypted or compressed, to their service. The third layer is the interface – a local map or status page in the browser.
The crux: an SDR stick can only be addressed by one program at a time. All the others have to read along over the network, usually in Beast format. If you have understood that, you also understand why some installations slow each other down and others run peacefully side by side. The hardware side is explained in Building your own ADS-B receiver, and suitable sticks are compared in SDR sticks for ADS-B compared.
The second crux is MLAT. For aircraft that do not transmit an ADS-B position, each service calculates the position from time differences between several stations – on its own servers. Each network therefore needs its own MLAT client and your exact antenna position. The basics are in MLAT and multilateration explained.
fr24feed (Flightradar24)
fr24feed is decoder and feeder in one. If a DVB-T stick is plugged directly into the Pi, the software starts its bundled decoder. If another decoder is already running, fr24feed reads its data over the network – in the wizard you then choose Mode-S Beast via network with host 127.0.0.1 and port 30005. According to the manual, the program supports Linux on ARM and x86 hardware as well as common DVB-T sticks, Mode-S Beast, and SBS- and AVR-compatible receivers. According to Flightradar24, AirNav’s receivers are expressly not compatible because their data stream is encrypted.
It is installed by a script that sets up the package repository and starts the signup wizard. Your station is identified by a 16-character sharing key, which is valid for only one machine at a time. Locally you get a plain status page on port 8754 – no map, but reception status and connection info. Important in multi-feeder operation: Flightradar24 advises turning MLAT off in fr24feed as soon as the same data also goes to other networks. In return there is the Contributor Plan, as long as the station is online and sharing. All of it step by step: Setting up fr24feed.
PiAware (FlightAware)
PiAware is FlightAware’s feeder software and takes the data of the in-house decoder dump1090-fa. FlightAware stresses that the station is based on free open-source software. There are two ways: a ready-made SD card image that brings everything along, or package installation on an existing Raspberry Pi OS. According to FlightAware, installation on a Pi that is already running takes less than five minutes.
PiAware is strong at local display: SkyAware shows you a live map of the traffic your antenna hears on your home network. On the statistics page at FlightAware you see range, message rates and leaderboards. For this to work, you have to claim the station for your account, that is, link it via the feeder ID. For MLAT, FlightAware needs the exact position and antenna height, both of which you enter on the statistics page. The reward is the free Enterprise account with up to eight months of flight history, unlimited alerts and registrations for scheduled flights. The way from an empty Pi to a finished station: Setting up PiAware.
PiAware as a basis for other feeders
Many stations start with PiAware and later attach fr24feed or RBFeeder to the data stream of dump1090-fa. That works well as long as all other programs only read along and do not address the stick themselves.
RBFeeder (AirNav Radar)
The service is now called AirNav Radar, but the program still carries the old name: RBFeeder, after RadarBox. According to AirNav, it can take data directly from an RTL stick or from an existing decoder such as dump1090, but also from Virtual Radar Server, ModeSdeco or ModesMixer. The main platform is the Raspberry Pi, for which AirNav provides installation instructions; afterward you claim the station for your account through a “claim” process.
With AirNav, MLAT is a separate building block: with the additional mlat-client you take part in multilateration. RBFeeder does not come with a local map of its own – but it is pleasantly undemanding as a reader-along. As a thank-you, AirNav unlocks a Business account for feeders. What the service can do otherwise is shown in RadarBox explained, and how to use the map and app in Using AirNav RadarBox.
Plane Finder client (pfclient)
The Plane Finder ADS-B client, pfclient for short, is the most platform-open program in the field: it is available for Linux, macOS and Windows. It works with many common receivers and decoders and supports MLAT as well as ADS-B. After installation, you reach a web interface on port 30053 on the local network, through which a wizard asks for location and data source. At the end you receive a share code that you enter on planefinder.net in the receiver management.
Through the web interface you keep an eye on the status and data source of your station. As a reward, according to the help center, there is Plane Finder Premium on all platforms, plus leaderboards. More on the app and feeder program: Plane Finder at a glance.
Instead of just data: an alert for your dream aircraft
Planetrack notifies you when a registration, type, airline or special livery from your list is on approach or lands. Planetrack is launching soon – join the waitlist and get early access.
ADS-B Exchange and the community networks
ADS-B Exchange does not rely on a complete program of its own but on feed scripts that attach to an existing decoder – according to the project page, readsb, dump1090-fa and PiAware are supported. The script sets up two system services: one for the data stream and one for MLAT. If you wish, it sends the calculated MLAT positions back to your local decoder so that they also appear on your own map. According to the project, the scripts do not interfere with existing feeders.
Optionally you install a stats package that gives you an online map with only your antenna’s receptions, and a local map based on tar1090. There is no subscription – instead, ADS-B Exchange shows the data largely unfiltered. adsb.fi, adsb.lol and airplanes.live work similarly. Setup is described in Feeding ADS-B Exchange and community networks, the differences between the networks in Unfiltered community trackers compared and the service itself in ADS-B Exchange explained.
The OpenSky Network plays a special role: a nonprofit research network that gives feeders a higher API quota instead of a subscription. If you deliver at least 30 percent of the time each month, you get 8,000 instead of 4,000 credits per day. More in OpenSky Network explained.
All-in-one solutions: adsb.im and Ultrafeeder
If you want to supply several networks, you do not have to install each program individually. Two community projects bundle everything.
The adsb.im image is an open-source feeder image for single-board computers such as the Raspberry Pi. It is also available as an app for DietPi and as an installation script for current Debian or Ubuntu systems on ARM64 or x86. Setup runs entirely through a web interface: click station name, antenna position, time zone and the networks you want, done. According to the project page, the choices include adsb.lol, adsb.fi, airplanes.live, ADS-B Exchange, FlightAware, Flightradar24, AirNav Radar, Plane Finder, OpenSky and Planespotters.net, among others. Map and statistics graphs are built in.
Ultrafeeder from the sdr-enthusiasts is the Docker route. The container combines readsb as the decoder, tar1090 as the map, graphs1090 as statistics and a separate mlat-client instance for each MLAT server entered. Commercial services run in their own companion containers, which fetch their data from the central one. All settings are in a Compose file and an .env file. The guide: Feeding multiple networks at once with Ultrafeeder.
The classic middle path without Docker is readsb with tar1090 as a neutral basis. The installation script replaces dump1090-fa and SkyAware and automatically switches fr24feed and RBFeeder to the new decoder; with PiAware, you had better check the changeover beforehand. Details in Installing readsb and tar1090.
All programs compared
| Program | Service | Own decoder | Local interface | MLAT | Reward |
|---|---|---|---|---|---|
| fr24feed | Flightradar24 | yes, optional | Status page, port 8754 | yes, turn off in multi-feeder operation | Contributor Plan |
| PiAware | FlightAware | yes (dump1090-fa) | SkyAware map | yes, with location and height | Enterprise account |
| RBFeeder | AirNav Radar | can use RTL stick directly | – | via mlat-client | Business account |
| pfclient | Plane Finder | works with existing receivers | Web interface, port 30053 | yes | Premium |
| Feed scripts | ADS-B Exchange | no, requires a decoder | optional tar1090, stats map | yes, own service | no subscription |
| adsb.im image | many networks | yes | Web interface with map | per network | depending on the network |
| Ultrafeeder | many networks | yes (readsb) | tar1090, graphs1090 | per network | depending on the network |
As of October 2026. The providers change programs, names and packages regularly – before a fresh installation, it is worth looking at the current documentation.
Official standalone programs
- Quick start with one network
- Support and docs straight from the provider
- PiAware and fr24feed run without another decoder
- Little knowledge of Linux needed
Where they reach their limits
- Several decoders fight over the stick
- Each program has its own configuration and updates
- MLAT settings have to be coordinated
- Local interfaces are inconsistent
Which variant suits you?
Beginners with one network
Flash the PiAware image or install fr24feed by script. Further feeders can be attached to the data stream later.
Several networks, little command line
The adsb.im image: all networks at the click of a mouse, map and statistics included. You simply enter existing sharing keys and feeder IDs.
Tinkerers with many services
readsb with tar1090 as a basis or straight to Ultrafeeder with Docker. Maximum control, but a bit more learning.
Typical pitfalls in parallel operation
1. Two programs on the stick
If fr24feed starts its own decoder while dump1090-fa or readsb is already running, one of the two gets no data. In that case, switch fr24feed to Beast via network.
2. MLAT twice or wrong
Each network calculates MLAT itself. Enter the same exact position including antenna height everywhere and, with fr24feed, follow the recommendation to turn MLAT off in multi-feeder operation.
3. Data loops
If a decoder reads its own output back in, a loop results. The readsb instructions expressly warn against connecting back to 127.0.0.1:30005.
4. Lost identifiers
Back up your sharing key, feeder ID and share code before you set up anew. Otherwise the station starts from zero, and the reward has to be unlocked again.
Ready-made receivers are not always open
Devices that a service ships as free hardware are often tailored to its network. AirNav’s receivers, for example, do not work with fr24feed according to Flightradar24. For a station that supplies many networks, an open SDR stick is the more flexible choice; alternatives are shown in Buying plug-and-play receivers.
Is your feeder station running cleanly?
- Exactly one decoder occupies my SDR stick.
- All other feeders read the data stream over the network.
- My antenna position and height are entered exactly everywhere.
- MLAT is deliberately switched on or off per network.
- Each station is linked to my account at the respective service.
- I have backed up my sharing key, feeder ID and share code.
- I regularly check the statistics or status page of my feeders.
Range beats software
As different as the programs are – the number of aircraft on your map is decided mainly by hardware. An antenna mounted high and unobstructed, short cables and a filter against cellular interference do more than any software change. You will find tips in Boosting ADS-B range, Finding the best antenna location and Measuring reception performance. Whether receiving and sharing the data is allowed where you live is clarified in Is receiving and sharing ADS-B data legal?.
A station near an airport is the most fun, for example around Munich Airport or Hamburg Airport. There you hear final approaches and often even ground traffic. At the Munich Airport visitors’ hill or at the Affenfelsen in Hamburg, you then use the services’ feeder accounts to time the next exciting approach – and in the evening, with the long history, you match your photos as described in Matching sightings with ADS-B logs.
From the radar to the fence
On the spot map, Planetrack shows you directions, best light, ratings and community photos, plus weather, wind and runways at the airport – and the sun position planner tells you when you should stand where. Planetrack is launching soon – join the waitlist and get early access.
Conclusion
Every feeder program has its quirks: fr24feed is decoder and feeder in one, PiAware shines with SkyAware and clear statistics, RBFeeder is an undemanding reader-along, pfclient even runs on Windows and macOS, and the ADS-B Exchange scripts rely on an existing decoder. What matters is less which program you choose than how you combine them: one decoder on the stick, all the others read along, MLAT set deliberately per network. If you do not want to build that by hand, adsb.im and Ultrafeeder offer convenient all-in-one solutions.
In brief
For one network, the official program is enough; for many networks, a neutral decoder such as readsb or an all-in-one solution such as adsb.im or Ultrafeeder is the better basis. You get the reward – Contributor Plan, Enterprise, Business or Premium – regardless of the type of installation, as long as the station is linked and delivers.
Summary
- For getting started with just one network, the service’s official program is usually the fastest route, such as the PiAware image or the fr24feed installation script.
- If you want to supply several networks, you are better off using a neutral decoder such as readsb and attaching the services’ feeders to it.
- In parallel use, MLAT is the biggest stumbling block: Flightradar24 recommends turning MLAT off in fr24feed as soon as the same data also goes to other networks.
- The feeder accounts of the commercial services only apply as long as the station delivers data; community networks trade open data and statistics instead of subscriptions.
Frequently asked questions
Which feeder program is the best?
There is no single best program, because each one only supplies its own service. The question is rather which foundation you choose. For a single network, the official package is ideal. For several networks, a neutral decoder such as readsb with tar1090 or an all-in-one solution such as the adsb.im image or the Ultrafeeder container is the cleaner basis.
Can I run several feeder programs on one Raspberry Pi?
Yes, that is the normal case. One decoder occupies the SDR stick and provides the data stream on the network, typically in Beast format on port 30005. fr24feed, RBFeeder, the Plane Finder client and the ADS-B Exchange scripts read this stream. You just have to make sure that no second program tries to address the stick directly.
What happens to PiAware if I install readsb?
According to the instructions, the readsb installation script removes the dump1090-fa decoder, because only one program can use the stick, and replaces the local map SkyAware with tar1090. The script automatically switches fr24feed and RBFeeder to the new decoder. With PiAware, you should check before the changeover whether the station still receives data afterward.
Does a feeder program also run on Windows?
Partly. The Plane Finder client is available for macOS and Windows as well as Linux. In its manual, Flightradar24 lists fr24feed for Linux on ARM and x86 hardware, and PiAware is tailored to the Raspberry Pi. In practice, most stations therefore run on a Raspberry Pi or a small Linux computer.
Do I have to run a separate MLAT client for each network?
Yes, each service calculates MLAT on its own servers. PiAware and the Plane Finder client include MLAT, with AirNav Radar the mlat-client adds participation, and the ADS-B Exchange scripts set up their own MLAT service. Ultrafeeder starts a separate mlat-client instance for each MLAT server entered. Only with fr24feed is the recommendation to turn MLAT off when feeding multiple services.
Do I lose my feeder account if I switch software?
Not if you take the identifier with you. With Flightradar24 that is the sharing key, with FlightAware the feeder ID, with Plane Finder the share code. If you switch from a classic installation to Docker, for example, you enter the existing values so that statistics and rewards are preserved.
Read more in App comparisons
- Photo editing on your smartphone: Lightroom Mobile, Snapseed and more for aircraft photos
- Flightradar24 Silver, Gold and Business: what the subscription tiers offer
- Flightradar24 vs. FlightAware: data sources, features and subscriptions compared
- Aviation radio apps and web streams: LiveATC and alternatives compared
- Official airport apps: what arrival and departure data does for spotters
- Flight diary apps compared: log and analyze your own flights
Related airports & manufacturers
Airports, manufacturers, airline groups and alliances – who is behind them and what you should know as a spotter.
Munich Airport
Germany’s second-largest airport and Lufthansa’s second hub: two parallel 4,000-meter runways in the Erdinger Moos, a Terminal 2 just for Lufthansa and Star Alliance – and, with the visitors’ park, one of the most convenient spotting places in the country.
AirportHamburg Airport
In the middle of the city, in the same place since 1911, with two runways that cross: Hamburg is not a hub, but an airport with plenty of European traffic, Emirates long-haul, Lufthansa Technik next door – and the Affenfelsen as its best-known spotting spot.
Related spotting locations
Specific vantage points with the runway configuration, light times, coordinates and an honest take on whether the trip is worth it.
Munich Airport visitors’ hill (Besucherhügel)
The best-known vantage point at Lufthansa’s Munich hub: from the visitors’ hill in the Besucherpark you look out over the airport grounds from above – with its own S-Bahn stop right next door.
Spotting hillAffenfelsen (“Monkey Rock”) at Hamburg Airport
The best-known spotting point at Hamburg Airport: from the Affenfelsen on Holtkoppel you look over the fence onto runway 15/33 without a ladder – with a kiosk café right next door and the morning sun at your back.
You might also like
What feeders get in return: free subscriptions from FR24, FlightAware, AirNav Radar and Plane Finder
Your own ADS-B station pays off in subscriptions: Flightradar24, FlightAware, AirNav Radar (formerly RadarBox) and Plane Finder reward feeders differently. The comparison shows what you get, which conditions apply and how to combine all the benefits with one receiver.
ADS-B, MLAT & receiversSetting up fr24feed: the Flightradar24 feeder on a Raspberry Pi
From a Raspberry Pi with an SDR stick to an active Flightradar24 station: install script, signup wizard, sharing key, receiver type, running alongside PiAware and the free account for feeders, step by step.
ADS-B, MLAT & receiversPiAware setup: the FlightAware feeder on a Raspberry Pi
From a blank Raspberry Pi to a claimed FlightAware station: flash the SD image or install the package, set up Wi-Fi, claim the feeder ID, set your location for MLAT and fix typical errors.