Why you might want to send flight data to more than one tracker

If you monitor aircraft for work—whether you're an aviation enthusiast, a researcher, or someone managing flight operations—you may want your data to reach multiple tracking platforms simultaneously. Flight trackers like Flightradar24, ADS-B Exchange, and others rely on data from ground receivers to build their maps. Sending your receiver's output to several services at once means your data contributes to multiple networks without requiring separate hardware or multiple receiver setups.

Most modern flight tracking software can be configured to forward data to multiple destinations using a single receiver. This saves you from buying additional equipment and lets you participate in different tracking communities at the same time. The process involves pointing your receiver software at multiple server addresses, each belonging to a different tracking service.

Key Takeaways

  • Most flight tracking software allows you to configure multiple data feeds by entering server addresses and port numbers for each service you want to send data to.
  • Common flight tracking platforms that accept data feeds include Flightradar24, ADS-B Exchange, RadarBox, and Planefinder, each with their own server addresses and port numbers.
  • You will need to know your receiver type (RTL-SDR, Mode-S Beast, etc.) because different software handles data forwarding differently.
  • Testing your connection to each service after configuration ensures your data is actually reaching the platforms and being displayed on their maps.

Understanding your receiver software and data format

Your flight tracking receiver outputs data in a standard format—usually Beast format or AVR format—that tracking services understand. The software running on your receiver (such as dump1090, readsb, or a proprietary program) is what actually processes the raw radio signals and converts them into this format. That same software is also responsible for sending the data out to external servers.

Before you configure multiple feeds, identify which software you're running. If you built your receiver from an RTL-SDR dongle, you're likely using dump1090 or readsb. If you have a commercial receiver like a Mode-S Beast or Radarcape, the manufacturer's software handles the data output. The configuration method differs slightly between these, but the principle is the same: you tell the software where to send the data, and it sends it there continuously.

Finding the server addresses and ports for each service

Each flight tracking service publishes the server address and port number where they accept data. These details are usually found on the service's website under sections labeled "Contribute Data," "Feeder Setup," or "How to Share." You will need both pieces of information—the address and the port—to configure your software correctly.

Flightradar24 accepts data on a specific server address and port that they provide when you register as a data contributor. ADS-B Exchange publishes their server details openly on their website. RadarBox, Planefinder, and other services do the same. Write down or bookmark these addresses before you begin configuration, because you will enter them one at a time into your receiver software. The port number is usually a four or five-digit number that tells your software which "door" on the server to use.

Configuring your receiver software for multiple feeds

The exact steps depend on which software you're running, but the general process is the same. Open your receiver software's configuration file or settings panel and locate the section for data output or network forwarding. This section will have fields for server address and port number. Instead of entering just one destination, you will add multiple entries—one for each tracking service you want to send data to.

If you're using dump1090 or readsb on a Linux system, you will typically edit a configuration file (often called a .conf file) and add multiple lines specifying each server. If you're using a graphical interface, you may see a list where you can add new destinations by clicking a button and entering the address and port. After you add each service, save your configuration and restart the software. The receiver should then begin sending data to all the addresses you specified.

Some software allows you to set different output formats for different destinations if needed, though most modern services accept the same format. Check the documentation for your specific software to see whether it supports multiple simultaneous feeds or whether you need to use an intermediate program that splits the data stream.

Testing your connections to each service

After configuration, do not assume your data is reaching all the services. Log into each tracking platform's website and search for your receiver's location or call sign. Most services display a map showing active feeders, and you should see your receiver listed there within a few minutes of starting the data feed. If you do not see your receiver on a particular service's map, the connection is not working.

Check the following if a connection fails: verify that you entered the server address and port number exactly as the service published them (spaces and capitalization matter), confirm that your internet connection is stable and not blocking the outgoing port, and review any error messages in your receiver software's log file. Some services require you to register or create an account before they will accept data from your receiver, so check whether that step is missing. If the problem persists, contact the tracking service's support to confirm their server address is current.

Managing bandwidth and system resources

Sending data to multiple services uses more bandwidth and processing power than sending to one. A typical ADS-B receiver generates between 50 and 200 kilobits per second of data, depending on how many aircraft are in range. Multiplying that by the number of services means your internet connection and your receiver hardware both work harder. For most home setups with a standard internet connection, this is not a problem—even five simultaneous feeds use less bandwidth than streaming a single video.

Monitor your receiver's CPU usage and network traffic after you add multiple feeds. If your receiver is a Raspberry Pi or similar small computer, adding too many feeds can cause it to lag or drop data. If you notice performance issues, reduce the number of services you're feeding, or upgrade to a more powerful computer. Most users find that three to five simultaneous feeds work well on standard home hardware without any noticeable slowdown.

Keeping your configuration updated

Tracking services occasionally change their server addresses or port numbers, usually with advance notice. Subscribe to email updates or check the websites of the services you feed regularly to catch these changes. If a service's server address changes and you do not update your configuration, your data will stop reaching that platform, and you may not notice for days or weeks.

Document your current configuration somewhere you can find it later—a text file or a note in your phone works fine. Include the service name, server address, port number, and the date you added it. When you need to troubleshoot or reconfigure, you will have a reference instead of having to hunt down each service's details again.

Frequently Asked Questions

Can I feed data to five or more services at the same time?

Yes, technically you can configure as many services as you want. However, each additional feed uses bandwidth and processing power. Most home setups handle three to five feeds comfortably. If you want to feed more than that, monitor your receiver's CPU and network usage to make sure it is not struggling.

Do I need different hardware for each tracking service?

No. A single receiver with properly configured software can send data to multiple services simultaneously. You do not need separate antennas, radios, or computers for each service.

What happens if one service's server goes down?

Your receiver software will attempt to reconnect to that service automatically, usually every few seconds or minutes depending on how the software is configured. Data sent to the other services continues uninterrupted. Once the service's server comes back online, your data will resume flowing to it.

Do all tracking services accept the same data format?

Most modern services accept Beast format or AVR format, which are the standard outputs from common receiver software. A few older or specialized services may require different formats, but the major platforms (Flightradar24, ADS-B Exchange, RadarBox, Planefinder) all work with standard formats. Check each service's documentation to confirm.

How do I know if my data is actually being used?

Log into each tracking service's website and look for your receiver on their feeder map or in their contributor list. Most services show when they last received data from your location. If you see your receiver listed and the timestamp is recent, your data is reaching that service and being used.