35 current-season troops, ranked by a transparent, reproducible methodology built entirely from this site's own data — peak efficiency, effective output, trait synergy, star scaling, and ability — with the reasoning behind every placement published below, not hidden. This ranking is never changed by votes. Community opinion appears beside a troop once it passes 25 votes, shown as its own signal — 0 votes cast so far from 0 voters.
This ranks full-merge (4★) potential, not typical in-game performance at whatever star level a given match actually reaches — a stated scope choice, not an oversight.
This board is mid-transition for Season 11
The scored troop pool itself is changing, not just individual troops' values. Dark Prince, Hog Rider, Ram Rider and the reworked Prince are September's Supers: Supercell publishes no stats for them and no stacking thresholds for their Rider trait, so they carry no methodology score. Ten more troops were reworked in Season 11 and are scored on their pre-rework kits until Supercell publishes the new numbers. 10 troops are also leaving the pool this season — Supercell hasn't named them, so every troop's normalized score could shift again once they're confirmed and removed. This board isn't being silently recomputed around these gaps; the placements below still reflect the pool as it stood before Season 11's roster changes.
Every troop below is placed by our published methodology — votes never move it. Cast your own verdict to add your voice to a troop's community signal, shown once it passes 25 votes.
First pick, every game, no questions asked.
Strong enough to build a comp around.
Solid. Fills a slot without carrying the run.
Situational — needs the right board to matter.
You've got 4 Elixir. Spend it on literally anything else.
Tier placement is always our published methodology score — votes are never folded into it. A troop's community vote count appears here once it passes 25 votes.
Each troop's editorial score is a weighted composite of five dimensions, computed entirely from data already published on this site:
15%
Peak Efficiency
15%
Effective Output
20%
Trait Synergy
20%
Star Scaling
30%
Ability
Peak efficiency uses the better of offense or defense, not their average
The first draft averaged offense-per-elixir and defense-per-elixir into one efficiency score. That penalizes specialists for not doing a job they were never built for — Giant, a pure tank with almost no offense, scored worse than its actual tanking value warranted purely because the average was dragged down by a stat it was never meant to have. Fixed by taking the stronger of the two instead of the mean.
Effective output — a troop can't be credited for damage it doesn't survive to deal
Switching to max() removed the only thing suppressing lopsided stat lines, and several cheap, fragile troops (Spear Goblins, Goblins, Dart Goblin) briefly rose on offense-per-elixir alone with nothing accounting for how quickly they die. Added a second, genuinely different dimension — offense × defense, both already-normalized — that collapses toward zero if either side is weak. A glass cannon with top offense and bottom defense no longer outranks a durable mid-statline troop; a pure tank still scores separately (and well) on peak efficiency for doing its one job, but doesn't get credited on this dimension for output it doesn't realistically land.
Trait value includes Ruler enablement, not just combat thresholds
Goblin trait has no combat thresholds at all — its six current troops were scoring zero trait value, even though Goblin Queen (one of 10 Rulers) explicitly ties into the trait in her own kit. Trait score is now combat-threshold magnitude plus Ruler enablement (checked against all 10 Rulers' real ability text — only Goblin Queen/Goblin and Tomb Queen/Undead have an explicit tie-in, so this is a small, real, data-derived credit, not an invented bonus).
This list ranks full-merge potential, not typical-star performance
The star-scaling dimension rewards a troop's ceiling at 4★, which is a different question from "how good is this troop in a typical match." That's a stated scope choice, not an error — it's a genuinely useful question nobody else in this space answers directly, and changing it wasn't justified on its own terms the way the two fixes above were.
Troops below have crossed 25 community votes with a clear majority leaning away from our published tier — real disagreement, not a handful of outlier votes. This is opinion data shown for its own sake; it does not change the tier above.
No troop has crossed 25 votes with a clear majority leaning away from our tier yet — check back as voting picks up.
The published tier for every troop is always our own methodology score — peak efficiency, effective output, trait synergy, star scaling and ability, with the reasoning shown for every placement — and votes never change it. Community votes appear beside a troop once it passes 25, shown as their own labelled signal (how many voters ranked it higher, the same, or lower than our tier), never as something that overrides the ranking.
Because a reproducible, transparent methodology is this list's actual value — nobody else in this space publishes their reasoning. Swapping a troop's placement for a raw vote count the moment enough people vote would trade that away for something weaker and less defensible: community sentiment can be brigaded and isn't reproducible. Votes are shown instead as a separate opinion signal, and where that signal diverges sharply from our tier, it's surfaced explicitly as its own section rather than silently overriding anything.
Full-merge potential. The star-scaling dimension specifically rewards how much a troop's stats grow from 1★ to 4★, so this ranks ceiling performance, not typical in-game power at whatever star level a given match actually reaches.
Because it answers a specific question: how much stat and ability potential a troop has from its own published numbers, weighted by the methodology above, at full 4★ merge. It does not use match results, pick rates or win rates — Supercell doesn't expose that data and this site doesn't estimate it — so a list built on a different question can reasonably place the same troop elsewhere.
Log in and link a player tag, then vote S through D on any troop. One vote per account per troop — re-voting changes your existing vote rather than adding a second one. Your vote adds to that troop's community signal; it never changes its published tier.
