Join the receiver network
Share AIS ship signals or ADS-B aircraft signals. Valid data earns free Pro within minutes.
The network right now
103ships heard by Beacon stations today
- 162,357
- AIS messages, last 24 h
- 2
- stations online
- 235 km
- farthest reception, 30 days
Three ways to join
Each works for ships (AIS), aircraft (ADS-B) or both. You register one station either way; one computer with two radio dongles feeds both.
| Setup | Time | Cost | What you do | Guide for |
|---|---|---|---|---|
| Build itA USB radio dongle, a Raspberry Pi (or any always-on computer) and an antenna. Our installer does the software, for AIS, ADS-B or both. | TimeAbout 1 hour | CostAbout US$60–150 in parts | What you doConnect a USB radio and an antenna, run one install command | Ships · AISAircraft · ADS-BBoth |
| Plug and playDownload the Voydar SD-card image for a Raspberry Pi, or use a ready-made receiver from its maker, connected with one command. | TimeAbout 20 minutes | CostA Raspberry Pi kit, or a ready-made receiver | What you doWrite the SD card, or connect a receiver with one command | Ships · AISAircraft · ADS-B |
| Bring your ownAlready feed MarineTraffic, AISHub, FlightAware, Flightradar24 or ADS-B Exchange? Keep them, and add Voydar with one line. | TimeAbout 5 minutes | CostNothing extra | What you doPaste one line into the feeder you already run | Ships · AISAircraft · ADS-B |
On a boat? Share what your AIS hears, even offshore: Beacon at Sea.
Build it
Everything below is sold by the maker or an official reseller. Links are plain: no affiliate codes, no tracking. Voydar sells no hardware.
Prices vary · links last checked Sep 24, 2026
1. USB radio (SDR dongle)
- RTL-SDR Blog V4Our pick
The standard AIS dongle. Their buy page lists the official stores (Amazon, AliExpress and others). Genuine units only: clones decode AIS poorly.
about US$30–40 - Nooelec NESDR SMArt v5
A good alternative if the RTL-SDR Blog V4 is out of stock.
about US$30–45
2. Always-on computer
Already have a Raspberry Pi or a spare Linux, Windows or Mac computer that stays on? Use it: skip step 2.
- Raspberry Pi 5 (2–4 GB)Our pick
Plenty for AIS. Official Raspberry Pi resellers.
about US$50–85 - Raspberry Pi 4 (2 GB)
Also fine, and uses less power.
about US$45–55 - Official 27 W USB-C power supply (Pi 5)
Use the official supply: a weak one causes USB dropouts.
about US$12–15 - Official 15 W USB-C power supply (Pi 4)about US$8–10
- microSD card, 32 GB
Any good A1/A2 card works.
about US$10–15
3. Antenna
- RTL-SDR Blog dipole antenna kit
Budget starter. Set each arm to about 46 cm for 162 MHz and put it outside, vertical.
often bundled with the V4 - Marine VHF/AIS antenna (162 MHz)Our pick
The biggest upgrade. Any well-known marine AIS or VHF antenna, mounted as high as you can.
about US$50–150
4. Cable and adapters
- SMA male to SO-239 adapter
Connects a marine antenna's PL-259 coax to the dongle. Use low-loss coax and keep the run short.
about US$10
5. Filter or preamp (optional)
- Uputronics filtered preamp (AIS 162 MHz version)
Filters out strong nearby signals and boosts weak ones. Needs bias-tee power (
-gr biastee on) or its own supply.about US$50–70 - Nooelec SAWbird filter and LNA modules
Choose a module whose passband covers 162 MHz.
varies
6. Aircraft (ADS-B, optional)
For aircraft add a second dongle made for 1090 MHz and a 1090 MHz antenna: one Raspberry Pi runs both. Aircraft only? Skip the AIS antenna and dongle and use these instead.
- FlightAware Pro Stick PlusOur pick
RTL-SDR dongle made for 1090 MHz, with a filter and amplifier built in. The installer recognises it.
about US$46 - FlightAware 1090 MHz antenna
Outdoor antenna tuned for ADS-B. Mount it high with a clear view of the sky.
about US$50 - FlightAware 1090 MHz band-pass filter
Only needed with a dongle that has no filter (the Pro Stick Plus already has one), near strong transmitters.
about US$29
Put it together
- 1
Register a station on Voydar. You get a station key and a one-line install command with the key already in it.
- 2
Put the antennas up high, with a clear view of the water (AIS) or the sky (ADS-B). Height matters more than anything else: a roof or a mast beats a window.
- 3
Connect each antenna to its USB radio with coax (and the adapter it needs). Add a filter or preamp between them if you bought one.
- 4
Set up the Raspberry Pi with Raspberry Pi OS Lite (64-bit) using Raspberry Pi Imager, turn on SSH, and plug the USB radios in.
- 5
Paste the one-line command from your station page into the Pi. With one dongle it sets up AIS; add
--adsbfor aircraft only, or plug in two dongles for both. - 6
Watch your station page. It turns green when the first ship is heard, and shows ADS-B live when the first aircraft is heard.
What we use
PlaceholderVoydar's own reference station in Tampa Bay was built from a kit, an antenna and AIS-catcher. We will publish its exact parts list and settings here once they are written up. Until then, the parts above are the ones we recommend.
Software: the easy way
On a Raspberry Pi, Debian or Ubuntu, one command does everything. It downloads our installer, checks it against the fingerprint below, and runs the decoders in Docker so they restart on their own after a power cut. The decoder images are pinned to exact versions.
YOUR_STATION_KEY is filled in for you on your station page after you register. The key is shown once, so the page is the place to copy it from.
curl -fsSL https://www.voydar.com/api/beacon/install-v7.sh -o voydar-install-v7.sh && \
echo "a90ae7a33268473f1ca5b93a6a5754412f14c605debb1f5859baa6145c294fbc voydar-install-v7.sh" | sha256sum -c - && \
sudo sh voydar-install-v7.sh YOUR_STATION_KEYcurl -fsSL https://www.voydar.com/api/beacon/install-v7.sh -o voydar-install-v7.sh && \
echo "a90ae7a33268473f1ca5b93a6a5754412f14c605debb1f5859baa6145c294fbc voydar-install-v7.sh" | sha256sum -c - && \
sudo sh voydar-install-v7.sh --adsb YOUR_STATION_KEYcurl -fsSL https://www.voydar.com/api/beacon/install-v7.sh -o voydar-install-v7.sh && \
echo "a90ae7a33268473f1ca5b93a6a5754412f14c605debb1f5859baa6145c294fbc voydar-install-v7.sh" | sha256sum -c - && \
sudo sh voydar-install-v7.sh --both YOUR_STATION_KEYRead the installer before you run itInstaller fingerprint (sha256): a90ae7a33268473f1ca5b93a6a5754412f14c605debb1f5859baa6145c294fbc
With two dongles the installer uses the one whose serial number contains 1090 (or a FlightAware Pro Stick) for aircraft. If it cannot tell, it lists them and asks you to rerun with --adsb-serial <serial>. To label a dongle for good, plug in only that one and run rtl_eeprom -s 1090 (from the rtl-sdr package), then replug it. Optional: --lat and --lon give readsb your antenna position for its range checks; it stays on your computer.
Other options: --ais or --adsb to choose, --ais-serial to name the AIS dongle, --private for a private AIS feed (ADS-B is public only), and an AIS gain such as 33.8 after the key.
docker run -d --name voydar-beacon --restart unless-stopped \
--device /dev/bus/usb ghcr.io/jvde-github/ais-catcher:v0.70 \
-H https://receiver.voydar.com/v1/beacon/ingest USERPWD voydar:YOUR_STATION_KEY INTERVAL 10 GZIP onAIS-catcher -H https://receiver.voydar.com/v1/beacon/ingest USERPWD voydar:YOUR_STATION_KEY INTERVAL 10 GZIP onPrefer to do it by hand?
- Install AIS-catcher by following its installation guide (Raspberry Pi steps).
- On Linux, stop the TV-tuner driver from grabbing the dongle: put
blacklist dvb_usb_rtl28xxuin/etc/modprobe.d/rtl-sdr.confand reboot. - Check it hears ships: run
AIS-catcheron its own. It prints each message as it arrives (-v 10adds statistics every 10 seconds). - Add the Voydar output from your station page to the command, and run it as a service so it starts on boot.
Free, open-source software does the decoding: AIS-catcher by jvde-github (GPL-3.0), and for ADS-B the sdr-enthusiasts ultrafeeder container (GPL-3.0) with wiedehopf's readsb (GPL-3.0-or-later). Many PiAware users run FlightAware's dump1090-fa (GPL-2.0-or-later), which works too. Voydar only adds an output.
Plug and play
No building: write our SD-card image for a Raspberry Pi, or use ready-made hardware and one command to connect it. Voydar sells no hardware and earns nothing from these links.
Plug and play: download the SD image
Version 1.2.0A ready Raspberry Pi image with the Beacon installer built in. Write it to a microSD card, plug in the USB radio and power, and a setup page on your own network asks for your station key. It feeds ships (AIS), aircraft (ADS-B) with a second radio, and can keep feeding other AIS networks at the same time.
0bcfd47597bb6c2a3fd8ca73b8b788bc8ed27cfc0b5abc77f8437183e2e8198fCheck the download before you flash it. This page is the reference for the hash: the file must match the one printed here, not only the .sha256 file next to the image. The same line is at /beacon/download/sha256.
echo "0bcfd47597bb6c2a3fd8ca73b8b788bc8ed27cfc0b5abc77f8437183e2e8198f voydar-beacon-1.2.0.img.xz" | shasum -a 256 -c -echo "0bcfd47597bb6c2a3fd8ca73b8b788bc8ed27cfc0b5abc77f8437183e2e8198f voydar-beacon-1.2.0.img.xz" | sha256sum -c -From card to station
- Flash the
.img.xzwith Raspberry Pi Imager ("Use custom"). Skip Imager's OS customisation: the image has its own setup page. - Before first boot, open
voydar-wifi.txton the card and type your Wi-Fi name, password and country. The Beacon then joins your Wi-Fi by itself and you open http://voydar-beacon.local/. Without it, the Beacon starts aVoydar-Beacon-XXXXhotspot whose password is on the HDMI screen or invoydar-hotspot.txton the card. - Plug in the radio and power. The first boot takes a few minutes (longer on a Pi Zero 2 W).
- Paste your station key from your stations into the setup page and pick ships, aircraft or both. Your station page turns green when the first messages arrive.
Supported boards
- Raspberry Pi Zero 2 W
- Raspberry Pi 3B / 3B+
- Raspberry Pi 4
- Raspberry Pi 400
- Raspberry Pi 5
64-bit, based on Raspberry Pi OS Lite (Debian trixie), with a USB RTL-SDR radio from the parts list under Build it. Tested on a Pi Zero 2 W with a Nooelec NESDR SMArt v5.
Built in the open: the build scripts, release notes, build inputs and full package list are on GitHub (release 1.2.0). The image contains GPL software (AIS-catcher, readsb in ultrafeeder, the Linux kernel and Debian packages): the matching source archives are attached to the release, and the release notes carry a written offer for the complete corresponding source. Based on Raspberry Pi OS; not Raspberry Pi OS and not endorsed by Raspberry Pi Ltd.
Ready-made receivers
These receivers decode by themselves. Each links to its maker's own product page; how it connects to Voydar is next to it.
Ships (AIS)
- dAISy HAT
Dual-channel AIS receiver that sits on a Raspberry Pi.
USB or serial: AIS-catcher reads it and forwards to Voydar
about US$70–90Wegmatt - dAISy-catcher
High-performance receiver, designed with the AIS-catcher author.
USB or serial: AIS-catcher reads it and forwards to Voydar
about US$100–150Wegmatt - dAISy 2+
USB receiver with NMEA 0183 output.
USB or serial: AIS-catcher reads it and forwards to Voydar
about US$80–110Wegmatt - Digital Yacht AIS100PRO
Dual-channel AIS receiver with USB and NMEA 0183 outputs.
USB or serial: AIS-catcher reads it and forwards to Voydar
about £250Digital Yacht - Comar R250
Dual-channel AIS receiver with USB, NMEA 0183 and Wi-Fi.
USB or serial: AIS-catcher reads it and forwards to Voydar
see the makerComar Systems - Comar R550Ni
Network AIS receiver for shore stations, with Ethernet and Wi-Fi.
Network NMEA output: a local AIS-catcher relay forwards it
see the makerComar Systems - Quark-elec A024
Network AIS receiver with WiFi: AIS-catcher reads it over TCP.
Network NMEA output: a local AIS-catcher relay forwards it
about US$150–250Quark-elec
Aircraft (ADS-B)
- FlightAware FlightFeeder Pro
A ready-to-run PiAware (Raspberry Pi, Pro Stick Plus, indoor antenna and touchscreen) from FlightAware's own store.
SkyAware aircraft.json: Voydar's feeder posts it
about US$200FlightAware
The commands
AIS-catcher -e 38400 /dev/ttyACM0 -H https://receiver.voydar.com/v1/beacon/ingest USERPWD voydar:YOUR_STATION_KEY INTERVAL 10 GZIP ondocker run -d --name voydar-relay --restart unless-stopped \
ghcr.io/jvde-github/ais-catcher:v0.70 -t txt RECEIVER_IP 10110 \
-H https://receiver.voydar.com/v1/beacon/ingest USERPWD voydar:YOUR_STATION_KEY INTERVAL 10 GZIP onIf your receiver sends UDP instead, use the UDP option under Bring your own.
curl -fsSL https://www.voydar.com/api/beacon/adsb-feed-v3.sh -o voydar-adsb-feed-v3.sh && \
echo "6a6d210080805150dcdac9eb46df949cb81b55870f5dc0d1e4a27b84eb87308b voydar-adsb-feed-v3.sh" | sha256sum -c - && \
sudo sh voydar-adsb-feed-v3.sh --install http://PIAWARE_IP/skyaware/data/aircraft.json YOUR_STATION_KEYBring your own
Keep everything you run today. Voydar is one more destination, and our contributor terms allow multi-feeding: feed Voydar alongside MarineTraffic, AISHub, FlightAware, Flightradar24, ADS-B Exchange and others, as long as it is data your own antenna receives.
Bring your own: AIS
Already run a receiver? Add Voydar next to your other feeds. Register a station to get these with your own key filled in (shown right after registering or rotating the key); here they show YOUR_STATION_KEY.
Copy for my setup
Already feeding MarineTraffic, AISHub, VesselFinder or another network? Pick what you run and add Voydar as one more destination.
AIS-catcher command line or config.cmdAIS-catcher started from a command, a script or /etc/AIS-catcher/config.cmd
-H https://receiver.voydar.com/v1/beacon/ingest USERPWD voydar:YOUR_STATION_KEY INTERVAL 10 GZIP on- Paste this at the end of your AIS-catcher command. With AIS-catcher's own installer, put it on a new line in
/etc/AIS-catcher/config.cmd(sudo nano /etc/AIS-catcher/config.cmd). - Restart:
sudo systemctl restart ais-catcher, or rerun your command.
Keeps your other feeds: AIS-catcher repeats outputs, so every -H sends to its own destination.
Check: after a minute, journalctl -u ais-catcher -n 30 shows HTTP Client [https://receiver.voydar.com/…]: return code 200. 401 means the key is wrong.
AIS-catcher config.jsonAIS-catcher's own installer and most Raspberry Pi setups (/etc/AIS-catcher/config.json)
{
"url": "https://receiver.voydar.com/v1/beacon/ingest",
"userpwd": "voydar:YOUR_STATION_KEY",
"interval": 10,
"gzip": true
}- Open the file:
sudo nano /etc/AIS-catcher/config.json. - If it has an
"http": [ ... ]list, paste this inside the brackets, with a comma after the entry before it. If not, add"http": [ ... ],with this inside, on a new line after"version": 1,. - Save, then restart:
sudo systemctl restart ais-catcher.
Keeps your other feeds: the sharing, UDP and HTTP outputs already in the file stay as they are.
Check: journalctl -u ais-catcher -n 30 shows HTTP Client [https://receiver.voydar.com/…]: return code 200. If AIS-catcher stops with a config error, a comma is missing or extra.
AIS-catcher web controlAIS-catcher's settings page in the browser (managed mode)
https://receiver.voydar.com/v1/beacon/ingest?key=YOUR_STATION_KEY- In the web control, open Output and add an HTTP output.
- Paste this as its URL and set the interval to 10 seconds. Leave any user and password fields empty: the key is in the URL.
- Press Save, then restart the receiver.
Keeps your other feeds: it is one more output next to the ones you have.
Check: AIS-catcher's log shows return code 200 for this output. The log line includes the URL and so the key: rotate the key if you share a log.
Docker or docker-shipfeedersdr-enthusiasts docker-shipfeeder, or the AIS-catcher Docker image
AISCATCHER_EXTRA_OPTIONS=-H https://receiver.voydar.com/v1/beacon/ingest USERPWD voydar:YOUR_STATION_KEY INTERVAL 10 GZIP on- In
docker-compose.yml, add this under the shipfeeder service'senvironment:. IfAISCATCHER_EXTRA_OPTIONSis already set, add everything after the=to the end of its value, with a space. - Apply:
docker compose up -d. - Running the
ghcr.io/jvde-github/ais-catcherimage directly? Add everything after the=to the end of yourdocker runcommand and recreate the container.
Keeps your other feeds: AIS-catcher repeats outputs, so your other networks keep receiving.
Check: docker logs --tail 30 shipfeeder (use your container's name) shows return code 200 for receiver.voydar.com.
AIS Dispatcher, rtl-ais, OpenCPN or a network AIS box (UDP)Anything that sends NMEA sentences over UDP
To send UDP straight to Voydar: assign a UDP port on your station page. Until then, this local relay does the job.
docker run -d --name voydar-relay --restart unless-stopped -p 127.0.0.1:10110:10110/udp \
ghcr.io/jvde-github/ais-catcher:v0.70 -x 0.0.0.0 10110 \
-H https://receiver.voydar.com/v1/beacon/ingest USERPWD voydar:YOUR_STATION_KEY INTERVAL 10 GZIP on- Run this on the computer next to your decoder or AIS box.
- In your program, add one more UDP output to
127.0.0.1port10110.
Keeps your other feeds: add an output and leave the UDP destinations you already have.
Check: docker logs --tail 30 voydar-relay shows return code 200.
Raw TCP (advanced): send KEY <your key> as the first line, then NMEA lines, to receiver.voydar.com port 5631.
Bring your own: ADS-B
Voydar's ADS-B feeder is a short script (sh, curl and gzip) that reads your decoder's aircraft.json or SBS output and posts it to Voydar every 5 seconds. --install sets it up as a service that starts on boot. It opens no ports.
curl -fsSL https://www.voydar.com/api/beacon/adsb-feed-v3.sh -o voydar-adsb-feed-v3.sh && \
echo "6a6d210080805150dcdac9eb46df949cb81b55870f5dc0d1e4a27b84eb87308b voydar-adsb-feed-v3.sh" | sha256sum -c - && \
sudo sh voydar-adsb-feed-v3.sh --install YOUR_STATION_KEYcurl -fsSL https://www.voydar.com/api/beacon/adsb-feed-v3.sh -o voydar-adsb-feed-v3.sh && \
echo "6a6d210080805150dcdac9eb46df949cb81b55870f5dc0d1e4a27b84eb87308b voydar-adsb-feed-v3.sh" | sha256sum -c - && \
sudo sh voydar-adsb-feed-v3.sh --install http://PIAWARE_IP/skyaware/data/aircraft.json YOUR_STATION_KEYcurl -fsSL https://www.voydar.com/api/beacon/adsb-feed-v3.sh -o voydar-adsb-feed-v3.sh && \
echo "6a6d210080805150dcdac9eb46df949cb81b55870f5dc0d1e4a27b84eb87308b voydar-adsb-feed-v3.sh" | sha256sum -c - && \
sudo sh voydar-adsb-feed-v3.sh --install http://127.0.0.1:8080/data/aircraft.json YOUR_STATION_KEYcurl -fsSL https://www.voydar.com/api/beacon/adsb-feed-v3.sh -o voydar-adsb-feed-v3.sh && \
echo "6a6d210080805150dcdac9eb46df949cb81b55870f5dc0d1e4a27b84eb87308b voydar-adsb-feed-v3.sh" | sha256sum -c - && \
sudo sh voydar-adsb-feed-v3.sh --install sbs:127.0.0.1:30003 YOUR_STATION_KEYcurl -fsSL https://www.voydar.com/api/beacon/adsb-feed-v3.sh -o voydar-adsb-feed-v3.sh && \
echo "6a6d210080805150dcdac9eb46df949cb81b55870f5dc0d1e4a27b84eb87308b voydar-adsb-feed-v3.sh" | sha256sum -c - && \
sudo sh voydar-adsb-feed-v3.sh --install http://127.0.0.1:8080/data/aircraft.json YOUR_STATION_KEYdocker run -d --name voydar-adsb --restart unless-stopped \
-e ULTRAFEEDER_CONFIG=adsb,BEAST_HOST,30005,beast_in -e TZ=UTC \
-v /run/voydar-adsb:/run/readsb \
ghcr.io/sdr-enthusiasts/docker-adsb-ultrafeeder:latest-build-965@sha256:39d0eb3b2307caaa3653367327aecb4b1ad87f485d6d7713686f12adc75bea7d && \
curl -fsSL https://www.voydar.com/api/beacon/adsb-feed-v3.sh -o voydar-adsb-feed-v3.sh && \
echo "6a6d210080805150dcdac9eb46df949cb81b55870f5dc0d1e4a27b84eb87308b voydar-adsb-feed-v3.sh" | sha256sum -c - && \
sudo sh voydar-adsb-feed-v3.sh --install /run/voydar-adsb/aircraft.json YOUR_STATION_KEYRead Voydar's ADS-B feeder before you run itFeeder fingerprint (sha256): 6a6d210080805150dcdac9eb46df949cb81b55870f5dc0d1e4a27b84eb87308b
Only what your antenna hears counts. Voydar drops MLAT results (positions other networks calculate for you) and anonymous (~) tracks, so running MLAT for FlightAware or ADSBx is fine: it simply is not sent on.
ADS-B works on public stations. Private feeds are AIS only for now.
Beacon at Sea: share your boat's AIS
Your boat already hears ships that no shore station can: offshore, in remote anchorages, along coasts nobody covers. Beacon at Sea forwards what your AIS receiver or transponder hears to Voydar, keeps it on board while you are out of reach, and uploads it when you are back online. Receive-only: Voydar never transmits and never writes to your instruments.
What you need
An AIS receiver or transponder on board, plus one way to reach its data:
- a NMEA 0183 Wi-Fi gateway or multiplexer (many transponders have one built in), read by the Voydar app or a small computer on board;
- or a Signal K server (often on a Raspberry Pi or a Victron Cerbo GX), with the Voydar plugin;
- or a USB AIS device plugged into a laptop running Chrome or Edge, while the page is open.
Gateways and software that work
A few common ones, linked to the maker's own page. Any device that outputs standard NMEA 0183 AIS sentences (!AIVDM) over Wi-Fi (TCP or UDP), USB or Signal K works; this is not an endorsement and we earn nothing from these links.
- NMEA 2000 Wi-Fi Gateway (YDWG-02)GatewayYacht Devices
Turns an NMEA 2000 network into NMEA 0183 over Wi-Fi, AIS included.
- NMEA 2000 Wi-Fi Router (YDNR-02)GatewayYacht Devices
A router and gateway in one, for boats that want their own Wi-Fi network.
- NMEA 0183 Wi-Fi Gateway (YDWN-02)GatewayYacht Devices
For an AIS receiver or transponder with an NMEA 0183 output.
- Smart WLN10GatewayDigital Yacht
NMEA 0183 to Wi-Fi, a small box next to your AIS.
- Smart WLN30GatewayDigital Yacht
NMEA multiplexer with Wi-Fi.
- iAISTX transponderAIS transponderDigital Yacht
Class B transponder with Wi-Fi built in.
- A026 AIS receiverAIS receiverQuark-elec
AIS receiver with GPS, multiplexer and Wi-Fi.
- A032 gatewayGatewayQuark-elec
NMEA 2000 and 0183 gateway with USB and Wi-Fi.
- W2K-1 gatewayGatewayActisense
NMEA 2000 to Wi-Fi gateway.
- em-trak AISAIS transponderem-trak
Transponders and receivers, several with Wi-Fi.
- Signal KSoftwareSignal K
Open marine data server. Install the Voydar plugin on it.
- Signal K serverSoftwareSignal K
The server software, for a Raspberry Pi or any Linux computer.
- OpenCPNSoftwareOpenCPN
Free chart plotter; can pass its NMEA data on to a gateway port.
How to connect
First add your boat on your stations page to get its station key. Then pick one:
The Voydar app
On a phone or tablet on board: Account, then "Share my boat's AIS". The app reads your Wi-Fi gateway (TCP or UDP) and keeps a buffer while you are offline. Simplest if you already carry a device on board.
Signal K plugin
If your boat runs a Signal K server, install the Voydar plugin on that computer. It forwards the AIS targets Signal K already sees and keeps its buffer on disk, so it runs whenever the boat's electronics are on.
Raspberry Pi or Linux computer
For an always-on boat: one command installs a small forwarder as a service. It reads your gateway over the network (or a USB receiver), buffers on disk and uploads whenever there is a connection. Read the script first; its SHA-256 is below. Already set up? Run the new command again: it upgrades in place and keeps your key and anything buffered.
This browser
Chrome or Edge on a laptop with a USB AIS device, or any browser with a Signal K server reachable over https. It only runs while the page is open. Browsers cannot reach http:// or ws:// addresses on your boat's network from an https page; use the Signal K plugin for those.
curl -fsSL https://www.voydar.com/api/beacon/install-boat-v4.sh -o voydar-boat.sh && \
echo "33bc92bd576c00a47cc998aa1e3ca0bc4a19c0b1c8206d5d7969a3f59bf82a8f voydar-boat.sh" | sha256sum -c - && \
sudo sh voydar-boat.sh --tcp 192.168.4.1:10110 YOUR_STATION_KEYcurl -fsSL https://www.voydar.com/api/beacon/install-boat-v4.sh -o voydar-boat.sh && \
echo "33bc92bd576c00a47cc998aa1e3ca0bc4a19c0b1c8206d5d7969a3f59bf82a8f voydar-boat.sh" | sha256sum -c - && \
sudo sh voydar-boat.sh --signalk YOUR_STATION_KEYRead the boat installerSHA-256: 33bc92bd576c00a47cc998aa1e3ca0bc4a19c0b1c8206d5d7969a3f59bf82a8f
Offshore without internet: store and forward
- Everything your AIS hears is kept on board with the time it was received, corrected by your GPS clock when one is available.
- When Starlink, Wi-Fi or 4G comes back, the buffer uploads automatically, newest data first while it is still live, then the rest.
- Late data goes into vessel history with its original times. It never shows as a live position.
- The buffer is capped and nothing older than 14 days is kept, so it never fills your device.
Your privacy on board
- Receive-only: nothing is ever sent to your AIS or gateway.
- Your own boat is never sent unless you turn on "share my own boat's position" (off by default). Its reports are dropped on board and again on our side.
- Your boat's location is used only coarsely (about 11 km) for quality checks and a track that only you see.
- Boats are never listed publicly and never appear on the public coverage map.
Rewards
The same as a shore station: your first valid data earns free Pro within minutes. For a boat, any hour the app or plugin is connected at sea counts as checking in, so a quiet crossing is fine; Pro pauses only after 45 days without connecting at all. Station level compares unique vessels per day at sea (at least 72 hours in 30 days), and unique vessels you hear more than 40 nm from land, checked against their own track, count double toward it.
Add your boatTroubleshooting
The dongle is not found
Run lsusb and look for RTL2838 or 0bda:2838. If it is missing, try another USB port or cable, and use the proper power supply (a weak one starves USB). If it is listed but AIS-catcher says it is busy, the TV driver has it: blacklist dvb_usb_rtl28xxu (the installer does this) and reboot.
Few messages, or lots of garbage
The gain may be wrong. Try a fixed value: -gr tuner 33.8 (the installer takes it as a second argument: sudo sh voydar-install-v7.sh <key> 33.8). Near strong transmitters (pagers, broadcast masts) lower it, or add a 162 MHz filter. rtlagc off sometimes helps too.
It runs, but no ships
Almost always the antenna. Mount it higher, outdoors, with line of sight to the water, and use an antenna made for 162 MHz. Check there are ships nearby: AIS-catcher's own map (-N 8100, then open http://<your computer>:8100) shows what it hears.
Behind a firewall or proxy
The installation script configures the Voydar receiver address. Your station only needs outbound HTTPS (port 443); nothing comes in, so there is no port to open or forward.
An old setup sends to port 10110
Earlier instructions sent raw NMEA with -P, -u or -t to port 10110. That port is now private and resets connections, so those stations deliver nothing. Replace that output with the HTTPS output from your station page (it starts with -H and ends USERPWD voydar:YOUR_STATION_KEY INTERVAL 10 GZIP on), then restart AIS-catcher.
The log says 429
Your station is sending faster than its limit. Use INTERVAL 10 (or more) and don't run two copies with the same key.
ADS-B runs, but no aircraft
Check that the decoder hears anything with sudo docker ps -a, then read its log with sudo docker logs --tail 30 <container-name>. Check the feeder unit shown by systemctl list-unit-files | grep -i adsb with sudo journalctl -u <service-name> -n 30. Use a 1090 MHz antenna mounted high with a view of the sky, and a dongle with a 1090 MHz filter near strong transmitters. The aircraft.json file should update every second.
Two dongles: the installer asks which one is for ADS-B
Rerun it with --adsb-serial <serial> (it lists the serials). If both dongles report the same serial, label one: plug in only that dongle, run rtl_eeprom -s 1090 (package rtl-sdr), replug, and run the installer again.
The ADS-B feeder says 403 or 409
403 with a licence message: stations registered before ADS-B was added accept the updated contributor licence once, on your station page; then restart the feeder unit shown by systemctl list-unit-files | grep -i adsb. 409: the station is private, and ADS-B needs a public station.
Do MLAT aircraft count?
No. MLAT positions are calculated by other networks, not received by your antenna, so Voydar drops them, together with anonymous (~) tracks. Everything your antenna decodes directly counts.
What happens to your data
- You keep the right to share what your station hears with anyone else. You give Voydar a non-exclusive licence to use it, ships and aircraft alike, as set out in our terms.
- Your station's precise location and your identity are never shown publicly. If you choose to list your station, only its name and a location rounded to about 1 km appear.
- Aircraft your station hears appear only inside the Voydar Terminal, never on public pages. We honour FAA LADD/PIA blocks where the lists are available and owners' opt-out requests, and we never name individual aircraft owners.
- Receive-only: we never transmit. If you feed from a boat, your own vessel's reports (
!AIVDO, or your MMSI) are dropped on board and again on our side, unless you choose to share your own position (off by default). - Every message is checked (impossible positions, impossible ranges, clock errors). Anything suspicious is set aside, not published.
Free Pro for contributors
Send valid data from your station and Pro is included on your account within minutes of the first message that passes our checks. There is no waiting period and no minimum number of ships or aircraft.
Pro stays on while your station keeps reporting in. A quiet antenna, a slow week or a short outage changes nothing: Pro pauses only after 14 days in a row with neither valid data nor a check-in from a fixed station (45 days for a boat), and comes back the moment it reports again.
Station and Anchor recognise the best-placed stations: Station needs at least 85% uptime and 25 ships or 50 aircraft a day that no other Beacon station hears, and Anchor stations are picked by us in a gap that matters. Both include Pro, the same as every contributor, and nothing more for now.
Uptime counts every hour your station sends ships or aircraft, so one computer with two dongles is one station. Valid means the key is yours, the contributor terms are accepted, the data passes our quality checks and the station is real: a second registration of someone else's station, or an invented location, does not count. Free Pro adds to anything you pay for and never cancels it; if you subscribe through the App Store or Google Play, cancel there if you no longer want to pay.
Chokepoints need you
A station near one of these passages would see some of the world's busiest and most watched traffic.
- Suez CanalNo Beacon station yetTransit monitor
- Panama CanalNo Beacon station yetTransit monitor
- BosphorusNo Beacon station yetTransit monitor
- Strait of HormuzNo Beacon station yet
- Bab-el-MandebNo Beacon station yet
Ready?
Register a station to get your key and a ready-to-paste install command. It takes a minute.
Register a station