Counter-battery missions are the point where IRON NEST stops being an arithmetic exercise and becomes a time trial. Enemy fire direction centres begin ranging on your position as soon as you fire, and every second spent at the map table after that is a second under someone else's fire plan.
The one rule
Finish every calculation before the first shell leaves the tube.
These missions are not a test of thinking on your feet. They are a test of how much work you did before the clock started. Operators who plot target two after firing at target one are already losing, and no amount of speed at the map table recovers that.
This inverts the instinct most players bring from earlier operations, where working target by target is perfectly viable. Here the map work and the shooting have to be separated in time, because only one of them can happen safely.
Execution sequence
- Plot every target in the fire plan. All of them, on the card, before anything is loaded.
- Fire target one and immediately begin traversing to target two. Do not wait to observe the impact — traverse is the longest single action you own, and it can overlap with everything else.
- Load the second gun while the turret is still moving. Shell and charge for target two, so the gun is ready as the bearing settles.
- Take corrections on the move. Apply them to the recorded solution rather than re-deriving from scratch.
Traverse is the real clock
Turret rotation dominates your cycle time, and it is the one cost you cannot budget your way out of. Everything else — loading, computing, correcting — can be overlapped with something. Rotation cannot be overlapped with more rotation.
This produces one concrete planning rule: group targets that sit on similar bearings and fire them as a block. The shells you deliver per minute rise sharply when the turret stops swinging across the whole arc between every round, and the gain compounds across a long fire plan.
Sorting a fire plan by bearing rather than by priority feels wrong the first time. It is usually correct anyway, because a target you reach thirty seconds sooner is a target engaged before the counter-battery has finished ranging on you.
Use FDC kills as pauses, not as objectives
Destroying an enemy fire direction centre temporarily suspends counter-battery fire against you. That pause is worth more as working time than as a scoreline.
- Do not rush to eliminate every FDC on sight.
- When one goes down, spend the quiet restocking and computing additional solutions rather than firing immediately.
- Every measurement taken while counter-battery is suspended is a measurement you are not taking under fire later.
Treating the pause as a chance to shoot more is the intuitive move and the wrong one. The pause is the only period in the mission when the map table is safe, which makes it the most valuable resource the mission hands you.
What the mission is grading
Medal conditions in IRON NEST are assembled from a recurring set of measures, and counter-battery response time is one of them. So are accuracy and requisition limits, which pull in different directions during these missions.
Requisition is the tension worth planning around. Ranging rounds cost budget, and so do repairs — both draw from the same pool. Taking damage early because you stayed at the map table too long can quietly put a requisition-limited medal out of reach before you have fired anything meaningful.
Where the exact thresholds sit for any individual mission is unconfirmed on this site. The categories are confirmed; the numbers are not.
Damage control
Repair priorities under sustained fire depend on which subsystem the enemy has actually hit, and a general ordering that holds across every situation does not exist. Hydraulic damage that stops traverse is categorically worse than damage that slows loading, because traverse is the bottleneck the whole plan is built around.
Beyond that principle, the specific repair order and the time each repair takes are unconfirmed here. This is one of the areas where community testing on the Steam boards is ahead of any published guide, including this one.
Practising without the pressure
The free demo runs the same fire-control loop with procedurally generated objectives, plus two challenge modes with leaderboards. That makes it a legitimate rehearsal environment for the habits this page describes — pre-computing a full plan, overlapping traverse with loading, and batching by bearing.
Drill the sequence until the order is automatic, because under a live counter-battery clock you will execute the order you practised rather than the order you intended. Timing yourself from teleprinter to first round is a better measure of readiness than accuracy on a single shot.
The underlying mindset
Every other operation in the game rewards care. This one rewards care performed in advance. The map table is where the mission is won, and it is also the one place you cannot afford to be once the shooting starts, which is a genuinely elegant piece of design rather than an artificial difficulty spike.
If a counter-battery mission is going badly, the diagnosis is almost never that you shot too slowly. It is that you arrived at the first shot without the rest of the plan already on the card.
Where this gets worked out
The Steam discussion boards carry a dedicated Counter-Battery Challenge thread where players compare approaches, and it is the fastest place to check whether a patch has changed the timings. Community walkthroughs cover mission-by-mission specifics that this page deliberately does not, since those depend on a verified playthrough.
The official Discord is where developer clarifications on the underlying mechanics appear first, which matters here because counter-battery timings are among the most balance-sensitive values in the game.