How to use the decoder
A complete guide to catching the Nasdara bunker broadcast, reading the results, and fixing the usual problems. Five minutes of reading saves a lot of standing around in the dark.
What the bunker broadcast is
At night, a radio station on 80.0 MHz in DayZ Badlands plays a loop of beeps. The beeps are Morse code, and they spell out numbers: one message for each of three radio bunkers that are active on your server. Each message gives the bunker's map grid and the PIN for that bunker. The loop repeats, so you can hear every message more than once.
You can decode it by ear with a pen and paper, but the beeps are fast and one wrong dot sends you to the wrong side of the map. This site listens with you, decodes the Morse as it plays, cross-checks every digit across repeats and puts the bunkers on a map.
What you need
- DayZ with the Badlands map, and an in-game radio that can tune to 80.0 MHz.
- Chrome or Edge on a Windows, Mac or Linux computer. The decoder hears the game through the browser's screen-sharing feature, which can include system audio. Firefox, Safari and phone browsers cannot share system audio, so they can't be used.
- Ideally, a second screen so you can watch the digits arrive while you stay in the game. One screen works too; see the tips below.
Step by step
- Wait for night in game and tune your radio to 80.0 MHz. You should hear a steady pattern of beeps with pauses between messages. Leave it playing.
- Open the decoder, ideally on your second screen.
- Press Start capture. Your browser opens a picker asking what to share. Choose Entire Screen. Any screen is fine; the page only uses the sound.
- At the bottom of the picker, turn on Share system audio, then press Share. Without that switch the page hears nothing.
- Go back to the game and keep it in focus. DayZ goes quiet when it is not the active window, so clicking away stops the beeps.
- Watch the On air strip fill in digit by digit. Each bunker card fills in once a whole message has been heard, and turns green when every digit has been heard at least twice and agrees.
You'll usually join part-way through a message. The decoder can't tell where that message began, so the page says Standing by while it plays. That's normal. As soon as it ends, the digits it caught fill in the end of that bunker's code (the start follows on the next loop), and every message after that is captured from its first digit.
Reading the results
Each bunker card shows three groups of digits:
- X (east), 3 digits: how far east the bunker is, in 100 m steps from the west edge of the map.
068means 6.8 km east. - Y (south), 3 digits: how far south, in 100 m steps from the north (top) edge.
058means 5.8 km down from the top. - PIN, 4 digits: the bunker's PIN. Sometimes the game sends only the six grid digits; the card then shows the PIN as none.
Together, X and Y point to a 100 m square. On the in-game map, the first two digits of each are the numbered 1 km grid square and the third is the tenth inside it. So 068 058 is grid square 06 across, 05 down, roughly eight-tenths of the way into it each way.
Card status
| Status | Meaning |
|---|---|
| No signal yet | No complete message for this bunker so far. |
| Incomplete | A message was heard but some digits were lost. They show as ?. |
| Heard once | Every digit is known, but only from one pass. Usually right, not yet double-checked. |
| Confirmed | Every digit has been heard at least twice and agrees. |
Location check
Nasdara has 23 known radio bunker sites, and the broadcast always points at one of them. The decoder compares the grid it heard against that list:
- A place name (for example 1.2 km NE of Dashtabad) means the grid matches a known bunker.
- Only one bunker fits means some digits are still missing, but just one known site matches the rest.
- Check the digits or No bunker at that grid means a digit was probably misheard. Let the loop play again; the next pass usually fixes it.
The map
- Hover over a bunker card to highlight its marker on the map, or over a marker to highlight its card. Click a marker to open that spot on iZurvive.
- Show on map zooms to that bunker. When you zoom in close, the marker becomes an open crosshair, so you can see the ground at the exact spot.
- Switch between the in-game paper Map and Satellite view. Satellite stays sharp right down to individual bushes.
- Red diamonds are the other radio bunker sites, which are useful for planning a route.
- iZurvive ↗ opens the full iZurvive map in a window over the page, centred on the exact spot with a marker. Its satellite view shows buildings too. Use Open in new tab (or Ctrl-click) to open it in its own tab.
- Copy for Discord copies all three bunkers as text, ready to paste to your squad.
If you only have one screen
Start capture, then go back to the game and stay there until all three messages have played at least once. A full loop takes about five minutes. Allow a little extra, since you'll usually join part-way through the first message. Then switch back to the page and read the cards. Switching away from the game mutes it, so check results only after you've finished listening.
Troubleshooting
Nothing happens, or "No beeps heard yet"
- Check that Share system audio was switched on. If not, press Stop, then Start capture again.
- Make sure DayZ is the active window and the radio is on 80.0 MHz at night.
- Watch the level bar under the buttons. It should jump with every beep. If it stays flat, the page isn't getting the game's sound.
- Turn the in-game radio volume up. Very quiet beeps can sink into background noise.
Digits keep coming out wrong
- Loud noises in game (gunfire, vehicles, rain) can hide beeps. Find a quiet spot and let the loop repeat; repeated passes outvote a bad one.
- Open Tuning & debug at the bottom of the decoder. Lowering Sensitivity makes it pick up fainter beeps; raising it ignores more noise.
- If two messages run together, raise Pause between messages a little.
"This browser cannot capture system audio"
Open the page in Chrome or Edge on a computer. Firefox, Safari and phone browsers don't offer system audio in screen sharing.
Decoding by ear
If you'd rather decode it yourself, every digit is five Morse symbols long. Write down each group of five between the short gaps:
| Digit | Morse | Digit | Morse |
|---|---|---|---|
| 1 | ·−−−− | 6 | −···· |
| 2 | ··−−− | 7 | −−··· |
| 3 | ···−− | 8 | −−−·· |
| 4 | ····− | 9 | −−−−· |
| 5 | ····· | 0 | −−−−− |
A tip: count the dots. Digits 1 to 5 start with that many dots, and 6 to 9 start with one to four dashes. A message is ten digits (X, Y, PIN), or six if no PIN is sent, followed by a longer pause.
Common questions
Does the site record me or my screen?
No. Your browser asks you to share a screen because that's the only way it can share system audio, but the page only listens to the sound. Everything happens inside your browser: nothing is uploaded, stored or sent anywhere. See the privacy policy.
Is this allowed?
The broadcast is public in-game information that any player can decode by ear; this tool just does it faster. Some community servers have their own rules about third-party tools, so check yours if you're unsure.
Can I reuse last night's codes?
Don't count on it. The active bunkers and their PINs can differ between servers and change over time, so decode again each time you play.