Skip to main content
⌖ OF Intel

GUIDES

How Much Damage Does a Shell Do in OpenFront: Warship and Defense Numbers

Learn the real Shell damage roll, how warship veterancy multiplies it, the warship and defense-post firing cadence and range, and how to read that against troops, SAMs and nukes.

Mechanics Difficulty · Intermediate Published Nov 20, 2026 Updated Nov 20, 2026 Reviewed by OpenFront Intel editors #shell#warship#defense-post#damage#combat#naval#mechanics

What a Shell is and the number you should remember

A Shell is the solid projectile that every Warship and every Defense Post fires at enemy ground units. It is the cheapest repeatable source of ground damage in the game because it costs no gold and does not consume troops, so the single most useful number to memorize is its per-impact damage. The Shell is the connective tissue between two guides you will want to keep open alongside this one: warship fleet decisions explains when to commit the ships that fire it, and defense posts covers the land emitter that shares this exact damage roll. Each Shell does not deal one fixed amount: the engine rolls a value and that value is what lands. The roll produces a result between 200 and 325 damage, and the average across many shots is 262.5. When you are estimating how fast a warship will chew through a column of troops, use the average 262.5 per Shell as your baseline, and remember that any single shot can come in as low as 200 or as high as 325.

That range matters for two practical reasons. First, it explains why the same warship can look slow in one engagement and devastating in the next: the damage roll varies by up to sixty points shot to shot, and a lucky early streak of high rolls can delete a squad before its defender has time to react. Second, it is the baseline that every other damage mechanic on this page builds on. Warship veterancy multiplies exactly this rolled number, the defense post uses the same roll but a slower cadence, and the nuke comparison below is expressed against the same per-impact unit. Hold 262.5 in your head as the cost of one shell impact and the rest of the guide becomes a set of multipliers and rates applied to that number.

Keep the question narrow before you move on: this page answers how much a single Shell deals, who fires it on what cadence and range, and what that implies for defending against or projecting warships. It does not re-teach fleet building or the full nuke formula; those are covered on their own pages and are linked where they matter. The decision this number unlocks is simple. Before you commit troops near water or rely on a wall of defense posts, you should be able to say roughly how many Shell impacts your units can absorb and how many impacts your own warships can deliver in the same window. That single estimate is the difference between a shore defense that holds for the duration and one that is gone in the first volley, and it is the arithmetic every other section on this page makes concrete.

Where Shells come from and who fires them

Two building types emit Shells, and the difference between them drives most of the decisions on this page. The first is the Warship. A Warship is a naval unit that moves along the sea and automatically fires Shells at enemy ground units that enter its targetting range; it does not need a separate order and does not spend anything to do so. The second is the Defense Post, a fixed land structure that likewise auto-fires Shells at enemy ground units within its shorter range. In both cases the Shell is generated for free and the firing is automatic, so neither source competes with your gold economy or your troop pool for the act of dealing damage.

The cleanest way to think about the two sources is by what you are paying. A Warship costs troops and gold to build and can move, so you choose where its damage is applied and can pull it away from a bad fight. A Defense Post is a building on a tile you own; it is cheaper to stand up quickly and it never has to retreat, but it only ever damages whatever happens to walk into its radius. That asymmetry is the heart of the guide: warship shells are mobile, concentrated, and scalable with your fleet, while defense-post shells are static, local, and bounded by a single structure’s range. When you ask “will this line of troops survive the water” you are really asking how many moving warships the opponent can bring to that beach, and when you ask “will my border hold” you are really asking whether the defense posts covering that border can out-pace the troops that cross it.

A third, easily confused, source is the nuke, which is a separate, one-shot, very high damage option that is not a Shell and is not fired on a cadence. If you mix nukes and shells in the same estimate you will badly misjudge the timing of a defense. Treat the nuke as its own layer on top of the Shell baseline and read the dedicated nuke calculator page for it. The point of this section is only to keep the two Shell emitters distinct: one floats on the sea and moves, one stands on land and stays. That distinction is also why warship veterancy matters here: only the moving emitter can accumulate the combat experience that multiplies the shell damage, while the static post fires its fixed base roll for the entire match. Everything about cadence, range and counterplay below splits along that same line, so keeping the two emitters separate in your head is the first step to reading the damage numbers correctly.

The per-shell damage roll, explained with the actual numbers

The Shell damage is not a single constant; it is a roll with a known distribution, and the shape of that roll is what you should model. The engine picks an integer roll from one to six, and the damage is computed from that roll so that the lowest possible impact is 200 and the highest is 325, stepping up by 25 with each higher roll. That gives six equiprobable values: 200, 225, 250, 275, 300 and 325. Because each of the six outcomes is equally likely, the long-run average is the midpoint, 262.5. So a single warship shell will almost always land somewhere in that band, and over a volley of many shells the total will cluster tightly around 262.5 times the number of shells.

The reason the minimum and maximum are worth writing down is that a single impact can decide a narrow engagement. Suppose a defending unit with about 250 hit points is standing in a gap. A 325-point shell deletes it in one impact while a 200-point shell leaves it wounded; over a short burst the difference between the high and the low of the band is the difference between a clean kill and a survivor that retreats and heals. For larger columns the variance averages out and 262.5 per impact is a reliable planning figure, but for one-on-one or two-on-one fights against light units the full 200 to 325 band is the honest estimate. Use the average for anything you intend to defend over several seconds, and use the full band when you are judging whether one or two shells can finish an isolated target.

The same roll is shared by both emitters. A defense post does not roll a different number from a warship; the 200 to 325 range and the 262.5 average apply identically to a shell fired from land. The only things that differ between the two are the cadence, the range and the veterancy multiplier, all of which are covered in the sections that follow. That shared roll is also what makes the comparison against other damage types clean: a nuke, a SAM or a troop exchange can all be expressed in terms of “how many 262.5-average shell impacts is this worth,” which is the unit the rest of the guide uses to make the numbers concrete.

OutcomeDamage per impactCumulative share of the band
Lowest shell (roll 1)2007.7 percent below average
4th of 6 (roll 4)2754.8 percent above average
Average (midpoint)262.5baseline for planning
Highest shell (roll 6)32523.8 percent above average

Warship firing cadence and range versus the defense post

Now put a rate on the rolls. A Warship fires one Shell every 20 game ticks, and the game runs 10 ticks per second, so that is one Shell every 2 seconds, sustained for as long as there is an enemy ground unit inside its targetting range of 130 tiles. A Defense Post fires one Shell every 100 ticks, which is one Shell every 10 seconds, within a range of 75 tiles. Those two cadence-and-range pairs are the core of the comparison, and they say something important: a single warship is not just mobile, it is roughly four times as rapid a Shell source as a single defense post, and it reaches nearly twice as far.

Work out the average damage per second each emitter produces from a single unit. A warship dealing the 262.5 average every 2 seconds produces about 131 damage per second from one ship. A defense post dealing the same 262.5 average every 10 seconds produces about 26 damage per second. The ratio is exactly the cadence ratio, five shells to one over a common window, so one warship’s sustained shell output is about five times a defense post’s. If you are defending a beach and the opponent has even one warship committed to your troops, the warship alone is out-damaging several of your defense posts in the same time. That is the quantitative reason a static defense can be overwhelmed by a small committed fleet: the fleet converts its gold and troop investment into a far higher shell rate than the equivalent number of posts.

The range difference changes the geometry of the fight. At 130 tiles a warship can begin damaging your units long before those units can reach it, and it can keep doing so while retreating, because the range is measured from the moving ship. At 75 tiles a defense post only matters when troops are inside a fairly tight ring around it, and the moment troops are outside that ring the post contributes nothing. Two practical consequences follow. First, to defend against warships you need to bring damage that can reach a moving ship or accept a fight at your own range, which is where nukes and naval counters enter. Second, to defend a land border, a single defense post covers a small ring, so the number of posts you need scales with the length of the border you are protecting, while a warship’s longer reach means fewer ships can threaten a wider front. Hold the 130 versus 75 and the 2-second versus 10-second numbers; they are the basis for every defense calculation that follows.

How warship veterancy multiplies Shell damage

Warship veterancy is the multiplier that turns a fleet’s raw shell rate into a real threat, and it is the single biggest source of underestimating naval damage. When a warship fires a Shell, the damage is not just the base roll; it is the rolled damage increased by 20 percent for each level of veterancy the firing warship has, up to a maximum of three levels. The increase is applied to the rolled value, not a fixed number, so it scales with the band you already saw. A level-one warship fires shells at 120 percent of the roll, a level-two at 140 percent, and a level-three at 160 percent of the rolled damage. Because the roll averages 262.5, the effective average per shell climbs from 262.5 at no veterancy to about 315 at level one, about 367 at level two, and about 420 at level three.

Warship veterancyShell multiplierAverage damage per shell
Level 0 (fresh)1.00262.5
Level 11.20315
Level 21.40367.5
Level 3 (cap)1.60420

Read that table as a decision tool, not trivia. A level-three warship firing at 420 average damage every 2 seconds is delivering about 210 damage per second, roughly 1.6 times the roughly 131 per second of a fresh warship, and far more than any single defense post. That is why a fleet that has been sitting in a match, accumulating kills, suddenly becomes lethal: the same number of ships now deals up to 60 percent more per impact, and that stacks on top of the already-high shell cadence. When you are estimating whether your troops can survive a naval attack, you must first estimate the veteran levels of the attacking warships, because a fresh fleet and a veteran fleet of identical size are not the same threat.

How do warships earn that veterancy? Each level is gained through accumulated combat: a warship levels up after sinking enough enemy transports and capturing enough trade, and it caps at three levels. The practical implication is that a warship that has been winning a long sea lane is a different weapon than one that has just been built. In the mid-to-late game, where most naval fights happen, the warships you face are usually at least partially veteranced, so planning against the level-zero 262.5 baseline will systematically understate the damage you are about to take. Always add the veteran multiplier before you commit ground units to a fight you cannot easily retreat from, and remember that the same logic applies to your own fleet: the warships you have built early and kept alive are worth protecting because their shells are already worth up to 60 percent more than a replacement’s.

Why a Shell is not the same as a nuke or a SAM

The shell is a continuous, low-per-impact, free damage source, and the most common planning error is to compare it directly against the nuke, which is a one-shot, enormous, expensive, timed damage source. A nuke does not fire on a 2-second cadence and does not cost zero gold; it has its own price, its own flight time and its own area, and it is managed on the dedicated nuke pages. The reason to keep the two separate here is that a defense plan that assumes “my nukes will match the enemy shells” is a plan built on the wrong time scale: shells arrive every 2 seconds and will have killed your troops long before a nuke can be aimed and landed, while the nuke is the tool for deleting a whole column or a structure in one burst. Think of shells as the pressure you must survive second to second and the nuke as the burst you spend to break the pressure.

The same separation applies to the SAM, which is the counter to aerial and incoming damage and is not a Shell. A SAM does not deal 200 to 325 of ground damage on a 2-second cadence; it is a defensive intercept layer with its own cost and its own targeting, and mixing its numbers into a shell estimate corrupts the comparison. If your question is “can I stop an enemy warship’s shells” the answer is not “buy a SAM”; a SAM does not intercept the ground-targeting shells the way it intercepts other threats, and the correct counters to warship shells are your own damage that reaches the ship (naval, nuke, or troops with anti-naval capability) or removing the troops it is targeting. The shell’s nature as a cheap, automatic, continuous source is exactly what makes it dangerous to a static defense and exactly what makes it weak against a defense that can simply deny the beach it is supposed to hit.

The clean mental model is three layers. Layer one is the shell: free, fast, low per impact, continuous, and the damage you must absorb every 2 seconds while it lasts. Layer two is the nuke: paid, slow to land, enormous per burst, and the tool for winning a specific moment. Layer three is the counter to the emitter itself: damage that reaches the warship or the removal of the target, which stops the shell stream rather than trading with it. Most failed naval defenses conflate these layers, defending the shell stream with a tool meant for one of the other two. Before you commit, name which layer each of your tools is, and make sure the layer that stops the shell stream is the one you actually have.

Reading Shell damage against a troop column

To make the shell number concrete, translate it into “how many troops does it kill” and “how long does the column last.” A Shell impacts a single enemy ground unit for its full rolled damage; it does not split across a column, so the question is always which unit absorbs the hit and whether that unit dies. The planning shortcut is to compare the per-impact band (200 to 325, average 262.5) against the hit points of the unit type standing in the line. A light unit with a few hundred hit points may die to one or two shells, a mid unit may need several, and a heavy unit may survive a full volley and still be fighting. Because the shell does not pierce or splash by default, a tight column does not absorb the shells more efficiently than a spread one; each shell still targets one unit and deals one roll’s worth of damage to it.

Now put the cadence on that column. A single warship hitting the same target every 2 seconds at 262.5 average is about 131 damage per second; a veteran warship at level three is about 210 per second. If a troop of a given total hit points is standing still and absorbing all of that, you can estimate its survival time by dividing its total hit points by the damage per second and you get seconds, not turns. This is the arithmetic that decides whether a landing is a landing or a massacre: if your beach column has, say, a few thousand hit points of total defense and the opponent brings two veteran warships, the combined roughly 420 damage per second means the column is gone in under ten seconds, which is far shorter than the time it takes to react or to bring a nuke. The number of warships the opponent commits, their veteran levels, and your own total hit points are the three inputs to that division, and the rest is arithmetic.

The defensive reading flips the same numbers. If you are the one placing troops to face a shore or a border that defense posts and warships are shelling, your decision is whether your total hit points and your ability to retreat exceed the incoming damage per second over the time you expect the fight to last. A column that cannot retreat and that is out-hit for its lifetime is a guaranteed loss no matter how brave the placement; the fix is to bring more hit points, to keep the units moving so the target is not sustained, or to remove the emitter. A column that can retreat, that has enough hit points for the expected window, or that forces the enemy to spread across a wider front can survive the same shell rate. The 262.5 average, the 2-second cadence, and the veteran multiplier are the three constants you plug in; the troop composition and the retreat option are the variables you control.

When to defend with posts versus with nukes versus with your own damage

The previous sections give you the rates; this section turns them into a decision rule for choosing your defense. The first input is the scale of the shell source. If the threat is a few warships shelling a wide, slow-moving front, a wall of defense posts can match the local damage per second because the posts’ lower cadence is offset by having many of them and by their being free to fire the moment a unit enters range. If the threat is a small, concentrated, veteran fleet committing to one beach, posts will lose the race, because the committed warships produce far more damage per second than the handful of posts covering that point, and that is the case where you need a tool with a different time scale: your own damage that reaches the ships, or a nuke to break the concentration at the moment it forms.

The second input is your economy and your timing. A nuke is the highest-leverage single tool against a committed fleet, but it costs gold and it needs the time to aim and land; spending it too early wastes it on a threat that has not yet concentrated, and spending it too late means the column is already gone. The shell rate tells you how much time you actually have, because the shell rate is the clock: at the combined damage per second of the attacking warships, you have only as many seconds as your hit points allow before the beach falls, and the nuke must land inside that window. A defense post, by contrast, has no such timing problem because it is already firing continuously; it is the cheap, always-on layer that you keep on the border even when no fleet is present, and it is the first thing you build when a coast is at risk.

The third input is retreat and denial. The strongest answer to a shell stream is often not to match it at all but to deny its target: if you pull the troops off the beach the warships have no ground unit to shell and the entire shell rate goes to zero, which is a free defense no nuke or post can match. This is why the decision is really about three tools answering three different questions. Defense posts answer “how do I absorb a continuous, wide shell pressure cheaply and always on.” Nukes answer “how do I break a concentrated burst of naval damage at a specific moment.” Your own damage and your retreat answer “how do I stop the shells by removing the emitter or the target.” A competent naval defense has all three and knows which one the current shell rate is asking for; the failure mode is reaching for the tool that is wrong for the time scale, usually a nuke for a pressure that posts should absorb, or posts for a burst that only a nuke or a counter-attack can break.

Failure modes and the counter to each

The most common failure is underestimating the veteran multiplier and committing troops against a fleet that looks small. A player counts three warships, divides the 262.5 average, and concludes the damage is manageable, then loses because those three ships are level three and each is dealing 420 average instead of 262.5, so the actual damage per second is 60 percent higher than the estimate. The counter is the discipline of estimating the attacking warships’ veteran level before the fight, not after; if the opponent has had a long, unopposed sea lane, assume the upper end of the table and plan the troop hit points and the retreat accordingly, because the cost of assuming fresh when the fleet is veteran is a column you do not get back.

The second failure is a static column that cannot retreat and is out-hit for its lifetime. This is a pure arithmetic loss: the column’s total hit points divided by the incoming damage per second is shorter than the time the fight will last, and no amount of bravery changes that. The counter is to make the number work by either bringing more total hit points so the division yields a longer survival window, by keeping the units moving so the shell stream cannot sustain a single target, or by denying the beach entirely so the shells have nothing to hit. Of these, movement and denial are the cheaper fixes, because they do not require spending gold that could go to other decisions, and they turn a guaranteed loss into a fight the enemy cannot easily win.

The third failure is layer confusion, where a player defends a continuous shell pressure with a nuke or defends a concentrated burst with a wall of posts. Against a slow wide front, the nuke is wasted because the threat never concentrates into a single burst worth a big spent tool, and the gold goes to a nuke that does not improve the second-to-second survival the posts should be providing. Against a fast committed burst, the posts are too slow to matter because their low cadence means they cannot match the damage per second of the committed warships in the short window before the column is gone. The counter to layer confusion is to name the time scale of the shell source before choosing the tool: continuous and wide means keep the always-on posts and do not waste a nuke, fast and concentrated means spend the nuke or bring your own damage to the ships, and the retreat option is the universal fix that works at every time scale because it removes the target and zeros the shell rate for free.

How Shell damage changes the decision across modes and maps

The same shell numbers play out differently on different maps and in different modes, and the decision changes accordingly. On a map with a long, narrow coast and a few crossing points, the shell rate at those points is the bottleneck of the whole match: the defender knows exactly which beaches matter, can stack defense posts on them, and can assume any committed fleet will concentrate on the one or two crossings that are defensible, so the defender’s shell-pressure problem is local and the attacker’s is forced into a burst. On a map with a long, open shoreline, the attacker can spread across many points and the defender cannot put posts everywhere, so the shell pressure is distributed and the defender’s posts are out-stretched, which shifts the decision toward the attacker favoring a broad, low-concentration approach that keeps the defender’s always-on layer thin.

In a ranked one-versus-one, both players can usually read the opponent’s fleet and veteran levels, so the shell numbers are a shared arithmetic and the edge comes from timing: the defender who reads the veteran table and holds the nuke for the moment of commitment wins the race the attacker cannot see. In free-for-all, the shell math is against multiple fleets at once and the retreat option becomes more valuable, because you cannot always tell which of several nearby warships is the one that will commit, so keeping your columns mobile and denying the beach is the safer default. In team modes, the shell rate is multiplied by how many allied warships can be brought to a shared front, and the decision is no longer one player’s arithmetic but a coordination problem: the team that concentrates several warships on a single crossing produces a damage per second no single player’s posts can match, and the team that defends must either match that concentration or deny the crossing.

The map-size and compact-mode settings change the geometry rather than the numbers: the 130-tile warship range and the 75-tile defense-post range are fixed, but on a smaller or more compact map those ranges cover a larger share of the available space, so a single warship can threaten more of the front and a single defense post covers a larger fraction of its local border. That means on compact maps the shell decision is more decisive per unit, because each emitter matters more, and the arithmetic of damage per second against total hit points carries more weight in deciding a fight. On large maps the same emitters are less decisive individually and the fight is more about how many of them you can bring to a point, which pushes the decision toward fleet size and concentration rather than per-unit damage. In every case the constants are the same 262.5 average, the 2-second and 10-second cadences, the 130 and 75 tile ranges, and the up-to-60-percent veteran multiplier; what changes is how much of the map a single emitter controls and how many of them each side can commit to the front that actually matters.

SituationShell pressureCorrect defense
Narrow coast, few crossingslocal, high per pointposts plus held nuke at the crossing
Open shoreline, many pointsdistributed, thinmobile columns, deny the beach
Ranked 1v1readable, timedread veteran level, spend nuke on commit
Free-for-allseveral fleets at oncekeep columns moving, deny the beach
Team modemultiplied by alliesmatch concentration or deny the crossing

Related content

Continue reading
OpenFront AFK Teammate Takeover: Absorb a Disconnected Ally for Zero Troop Loss

A Team-mode decision guide for what a teammate's disconnect does to your win/loss position, when absorbing their land is free, when it is a trap, and what the 30-second mark and the ranked 2v2 rules actually change.