Aoe2 Damage Calculator

Estimate damage per hit, hits to kill, expected DPS, and time to kill in Age of Empires II. This premium calculator models the core combat rule used by AoE2 players every day: effective damage is the attacker’s attack plus bonus damage minus the defender’s relevant armor, with a minimum of 1 damage on a landed hit.

Interactive Calculator

Use presets for a fast test or enter custom numbers. For ranged units, you can lower hit chance to estimate expected DPS in practical fights.

How an AoE2 damage calculator works

An AoE2 damage calculator helps players answer one of the most practical questions in the game: how much damage does this unit really deal to that target? In Age of Empires II, raw attack alone does not tell the full story. Every combat interaction is shaped by armor classes, bonus damage, minimum damage rules, attack speed, and the target’s hit points. The result is that two units with similar listed attack can perform very differently depending on who they are fighting.

This calculator uses a clear and useful combat model for direct comparison: effective damage per landed hit = max(1, base attack + bonus damage + attack upgrades – target armor – armor upgrades). Once effective damage is known, the calculator estimates hits to kill, expected DPS, and expected time to kill. For ranged interactions or moving fights, a hit chance input is also included so you can model less than perfect engagements.

That makes this tool valuable for many use cases. If you are planning a feudal archer timing, testing whether pikes hold well enough against cavalry, or comparing power spikes after blacksmith upgrades, the calculator gives you an immediate sense of efficiency. It is also useful for content creators, strategy writers, and players who want to explain fights numerically instead of relying only on instinct.

The core damage formula

At the center of most standard AoE2 combat interactions is a very intuitive rule. Attackers bring a base attack value. Some units also receive bonus damage against certain armor classes, such as anti-cavalry damage from pikes and halberdiers or anti-archer damage from skirmishers. Defenders reduce incoming damage using melee armor or pierce armor, depending on the attack type. If the result would fall below 1, the game still deals 1 damage on a landed hit. That minimum matters more than many players expect, especially in heavily armored fights.

Practical rule of thumb: if a unit is only scratching a target for 1 damage, attack speed and numbers become the deciding factors. If bonus damage is high, armor can feel almost irrelevant because the bonus overwhelms the target’s defenses.

What each input means

• Base attack: the listed attack value of the attacking unit before target-specific bonuses.
• Bonus damage vs target: extra damage against the target’s armor class, such as a halberdier hitting cavalry.
• Target relevant armor: melee armor against melee attacks or pierce armor against arrows, javelins, and similar ranged attacks.
• Target HP: how many hit points the defender has before dying.
• Reload time: the delay between attacks. Lower reload time means better sustained DPS.
• Hit chance: a practical estimate of how many attacks actually land. This is especially useful in mobile ranged fights.
• Upgrade adjustments: extra attack or armor from blacksmith techs and other bonuses.

Why armor and bonus damage matter so much

A common mistake is to compare only attack values. In AoE2, unit matchups are not balanced around base attack alone. Instead, the game leans heavily on armor classes and bonus damage to create counters. This is why halberdiers remain dangerous to expensive cavalry, and why elite skirmishers stay relevant against archers even when their base attack looks modest. Their bonus damage changes the entire exchange.

Armor also scales in an important way. If a unit reduces incoming damage from 8 to 6, that is a 25% reduction. If it reduces damage from 3 to 1, that is a massive survival swing because the minimum damage floor now dominates the interaction. This is one reason heavily armored cavalry or unique units can feel far stronger than their visible stat line suggests.

Representative AoE2 unit statistics

The table below uses widely recognized representative unit values for common matchups. Exact patch values can change over time, but these numbers are realistic benchmarks for planning and comparison.

Unit	Attack Type	Base Attack	HP	Melee Armor	Pierce Armor	Reload Time
Crossbowman	Pierce	5	35	0	0	2.0
Arbalester	Pierce	6	40	0	0	2.0
Knight	Melee	10	100	2	2	1.8
Paladin	Melee	14	160	2	3	1.9
Pikeman	Melee	4	55	0	0	3.05
Halberdier	Melee	6	60	0	0	3.05
Elite Skirmisher	Pierce	3	35	0	4	3.0

Reading the calculator output like a high-level player

Once you press calculate, the most important result is usually effective damage per hit. That tells you whether a matchup is driven by armor, by bonuses, or by raw attack. After that, the next key number is hits to kill. AoE2 fights often flip dramatically when a unit survives one extra hit. That can alter micro outcomes, formation collapses, and the viability of a timing push.

DPS is best used as a sustained combat metric. It helps compare army value over a longer engagement, especially when units are actually getting repeated attacks off. Time to kill is more intuitive for small engagements and raid scenarios. If a cavalry unit kills villagers in just a few attack cycles, that can have a larger strategic impact than a slower unit with higher theoretical efficiency in a prolonged fight.

Example matchup comparisons

Matchup	Damage Per Hit	Estimated Hits to Kill	Why It Matters
Knight (10 attack) vs Crossbowman (0 melee armor, 35 HP)	10	4	Shows why knights punish exposed ranged units in direct contact.
Crossbowman (5 attack) vs Knight (2 pierce armor, 100 HP)	3	34	Explains why unsupported crossbows struggle against armored cavalry.
Halberdier (6 attack + 32 bonus) vs Paladin (2 melee armor, 160 HP)	36	5	Demonstrates how counter bonuses can overwhelm elite expensive units.
Elite Skirmisher (3 attack + 4 anti-archer) vs Arbalester (0 pierce armor, 40 HP)	7	6	Illustrates why cheap counter units remain cost-effective in large fights.

Best ways to use an AoE2 damage calculator in real games

1. Check upgrade breakpoints. One extra attack can reduce the number of hits needed to kill a target. That can justify fletching, bodkin, forging, or blast furnace timing windows.
2. Plan your counter units. If bonus damage pushes effective damage dramatically upward, the matchup may be better than raw stats imply.
3. Model raid efficiency. Time to kill villagers, monks, siege, or low-armor eco units often decides whether a raid succeeds.
4. Evaluate armor investments. Extra armor can create huge value when it drops enemy damage closer to the 1-damage floor.
5. Compare practical ranged performance. Use hit chance below 100% when skirmishing mobile targets or fighting around pathing issues.

Important limits to remember

No calculator can perfectly simulate every fight in AoE2. Real engagements include overkill, formations, projectile travel time, elevation, attack animation delays, hill bonuses, conversion pressure, pathing, frame timings, and civilization-specific unique techs. This calculator is therefore best seen as a clean combat estimator. It gives highly useful insight into the main damage math, but smart players still combine those results with positioning and macro considerations.

For example, a crossbow ball may have low single-unit damage versus knights, yet massing and focus fire can still become decisive when terrain, numbers, and upgrades line up. Likewise, a halberdier can show excellent damage versus cavalry, but that does not always mean it can force an engagement on open ground against a mobile army. The calculator tells you what happens if attacks connect; strategy determines how often they will.

How to think about expected damage and probability

The hit chance field introduces the idea of expected value. If a ranged unit deals 6 effective damage but only lands about 75% of its shots in the kind of fight you are modeling, then the expected damage per attack cycle is 4.5. This does not mean every volley behaves that way, but over time it is a strong planning average. Players who like to sharpen this kind of reasoning can learn more from resources like the NIST Engineering Statistics Handbook and UC Berkeley’s probability and percentages notes.

Those sources are not AoE2 strategy guides, but they are excellent for understanding the math habits behind better game analysis: expected outcomes, percentage interpretation, and comparing rates correctly. That matters when you are deciding whether an upgrade changes a fight enough to justify its cost or whether a unit switch is truly efficient instead of just feeling efficient.

Common mistakes when estimating AoE2 damage

• Ignoring bonus damage. This is the biggest error in counter-matchup analysis.
• Comparing only DPS and not hits to kill. Breakpoints often matter more than small DPS differences.
• Forgetting the 1-damage minimum. Armor is especially powerful when it pushes damage near the floor.
• Using theoretical values for practical fights. If ranged shots miss or units cannot engage cleanly, expected output falls.
• Not accounting for upgrades. A single blacksmith tech can move a matchup from awkward to efficient.

When this calculator is most useful

This tool is especially valuable in the following moments: early feudal pressure planning, castle age power spikes, imperial counter-tech switches, and cost-efficiency comparisons between gold units and trash units. It is also useful for coaching and team discussions because it turns vague claims into transparent numbers. Instead of saying “that unit should win,” you can show why it wins, how fast it wins, and which stat change would alter the outcome.

If you want the best results, combine this calculator with replay review. Look at a fight that felt surprising, then enter the unit stats and upgrades to see whether the outcome was driven by damage math, by micro, or by numbers. Over time, that process builds much better intuition. You start recognizing when a unit composition is truly underpowered and when the real issue was position, timing, or execution.

Final takeaway

An AoE2 damage calculator is not just a novelty. It is a serious planning tool for players who want cleaner decision-making. By translating attack, bonus damage, armor, HP, and reload time into concrete results, it helps you understand why counters work, when upgrades matter, and how quickly a fight can snowball. Use it to test assumptions, validate strategy ideas, and improve your combat intuition one matchup at a time.

Note: Age of Empires II receives patches and balance changes. For competitive planning, always verify current in-game values when exact breakpoints are critical.