How To Find ADSBexchange Feed UID Windows: Complete Guide
Finding your ADSBexchange feed UID on a Windows machine requires locating your persistent configuration files or querying your local receiver script parameters via the command line. This unique identifier ensures your feeder connects reliably to the global multi-static tracking network without needing constant IP re-authentication.
Pre-Operation & Equipment Checklist
Setting up and managing data ingestion feeds for flight tracking platforms demands a baseline familiarity with local network topologies, text editors, and command-line interfaces. Whether you are running a dedicated feeder box or sharing resources from a primary Windows workstation, organizing your toolchain beforehand prevents unnecessary downtime.
- Essential Gear and Software: A Windows 10 or Windows 11 host machine, administrative access to Command Prompt or PowerShell, an advanced text editor such as Notepad++ or Visual Studio Code, and an active software-defined radio receiver setup like Dump1090-fa or ADSBexchange feeder software.
- Prerequisite Knowledge and Standards: Basic understanding of TCP/IP networking, local loopback addresses, environment variables, and the directory structures used by Windows application data folders.
- Time and Budget Benchmarks: Estimated completion time is between 5 to 15 minutes, with zero financial cost assuming existing hardware and software components are already functional.
Step-by-Step Procedure to Locate Your ADSBexchange Feed UID
Step 1: Access the Windows Command Line Interface
Begin by opening your command-line utility to query active processes or navigate through system directories. Press the Windows key, type cmd, right-click on Command Prompt, and select Run as Administrator to ensure you possess the necessary read privileges for system-level directories. Alternatively, you can use PowerShell if you prefer advanced scripting environments, though standard command prompts are entirely sufficient for locating configuration strings.
Step 2: Search for Local Feed Configuration Files
ADSBexchange feeders running on Windows typically store their connection strings, logging parameters, and unique identifiers inside configuration text files or environment initialization scripts. Navigate to the installation directory of your feeder software, which is commonly located within the Program Files folder or your specific user profile application data directory. Use the directory change command followed by the target folder path, then list the contents using the directory listing command to find files ending in extensions like .conf, .ini, .txt, or .bat.
Pro-Tip: If you are unsure where the feeder software was installed, use the Windows search indexer or a utility like Everything by Voidtools to search your entire drive specifically for files containing terms like adsbexchange or feeder.
Step 3: Inspect Feeder Scripts and Startup Parameters
Open the primary startup batch file or configuration document using your text editor of choice. Look closely at the command arguments passed to the feeder client, such as netcat, custom python scripts, or specialized binaries like feed-adsb. The UID is frequently passed as an argument flag immediately following an identifier tag or within an exported environment variable string assigned during your initial registration on the ADSBexchange stats portal.
Warning: Never share your raw feed UID publicly on forums, social media, or pastebins. Exposing your unique identifier allows unauthorized users to spoof your station feed or manipulate ingestion metrics associated with your hardware location.
Step 4: Query Active Network Connections via Netstat
If your feeder is currently running and actively transmitting live Mode-S and ADS-B packets to the ADSBexchange ingestion servers, you can capture the active socket connection parameters. Type netstat -ano into your administrative command prompt to display all active TCP connections and their corresponding Process IDs. Cross-reference the remote foreign address pointing to the official ADSBexchange ingestion port with your active task manager processes to confirm data egress.
How to find UID?
Technical Parameters and Configuration Methods
The table below outlines the primary methods used to locate, store, or verify your ADSBexchange feed UID on a Windows operating system environment, comparing accessibility, technical depth, and primary use cases.
| Method | Accessibility Level | Technical Complexity | Primary Use Case |
|---|---|---|---|
| Configuration File Inspection | High | Beginner | Finding the permanent UID stored inside local setup files (.conf/.ini). |
| Command-Line Argument Review | Medium | Intermediate | Checking active batch scripts or startup shortcuts for runtime parameters. |
| Registry Key Analysis | Low | Advanced | Locating UIDs stored inside Windows registry hives by advanced installers. |
| Network Traffic Capture | Advanced | Expert | Sniffing outbound packets using tools like Wireshark to isolate registration headers. |
Troubleshooting Common Feed UID and Windows Connection Issues
Even with proper configuration, environment shifts or software updates on Windows can disrupt your data feed. Review these common failure scenarios to restore connectivity quickly.
- Root Cause: The configuration file containing the UID was overwritten during a software update or reinstallation of the feeder package.
- Actionable Fix: Access your account dashboard on the ADSBexchange statistics portal using your feeder's MAC address or registration email to retrieve your assigned unique identifier, then manually re-enter it into your local configuration file.
- Root Cause: Windows Defender or a third-party antivirus program is blocking outbound traffic on the specific ports required by the feeder script.
- Actionable Fix: Create an explicit inbound and outbound firewall rule allowing your feeder executable and associated ports (typically port 30004 or custom ingestion ports) to communicate freely over the public internet.
- Root Cause: Multiple instances of the feeder script are running simultaneously in the background, causing socket conflicts and authentication timeouts.
- Actionable Fix: Open Windows Task Manager, locate all running instances of python, netcat, or custom feeder executables, end those tasks entirely, and restart your primary batch script cleanly.
Frequently Asked Questions
What exactly is an ADSBexchange feed UID?
An ADSBexchange feed UID is a unique alphanumeric string assigned to your specific receiver hardware when you register to share flight data. It allows the ingestion servers to authenticate your data stream, track your feeding uptime, and credit your station on the global coverage map.
Can I use the same feed UID on multiple Windows computers?
No. Each feed UID must map to a single unique hardware receiver and antenna setup to prevent data packet collisions and inaccurate multilateration calculations on the network. If you operate multiple receivers, you must register each one individually to obtain distinct identifiers.
Where is the default installation directory for ADSBexchange feeders on Windows?
Most custom community scripts and native Windows ports install their files within the user profile directory under AppData, or inside a dedicated folder directly off the root C drive such as C:\ADSB\ or C:\Program Files\Feeder. Use your file explorer search bar to look for batch files if you cannot locate the primary directory.
What should I do if my feed UID stops working after a Windows update?
Major Windows updates frequently reset environment variables, disable background startup tasks, or alter network adapter profiles. Verify that your startup scripts still execute upon system boot and that your local firewall settings have not reverted to blocking your data ingestion client.
How do I verify that my Windows machine is successfully sending data to ADSBexchange?
You can verify your data transmission by checking your local receiver's web interface (such as the Dump1090 map running on localhost:8080) to ensure aircraft are being decoded locally. Then, search for your station's identifier or IP address on the official ADSBexchange stats website to confirm that packets are actively arriving at the ingestion servers.
Optimize your flight tracking capabilities today by securing your feeder configuration and verifying your station metrics on the global network.
