Clash Royale Battle Types
A deck that dominates Ranked can be mediocre on Ladder and close to unplayable in 2v2. CrownStats analyses each format on its own battles rather than averaging them together, because a single blended leaderboard describes a game nobody is actually playing.
Figures cover the last 30 days.
Ranked Battle Types
Formats with enough tracked battles and enough distinct decks to publish a ranking.
Ranked
Clash Royale's competitive 1v1 ladder, played in Path of Legends.
- Battles
- 164,591
- Decks ranked
- 1,611
- Days covered
- 30
Ladder
Standard 1v1 Trophy Road battles, outside Path of Legends.
- Battles
- 49,233
- Decks ranked
- 481
- Days covered
- 30
2v2
Team battles with two players per side sharing one arena.
- Battles
- 16,390
- Decks ranked
- 140
- Days covered
- 30
Tracked, not yet ranked
CrownStats classifies these formats and keeps their history. None has a ranking page yet, and none is linked — publishing one before it can be ranked honestly would just be an empty grid.
Clan War
Collecting more dataRiver Race battles, including Boat Battles and Duels.
CrownStats is tracking this format, but not yet enough distinct decks clear the sample floor to publish a ranking that would hold up.
27,611 deck-observable tracked battles · 4 decks above the sample floor
7x Elixir
Collecting more dataA 1v1 variant in which Elixir generates at seven times the normal rate.
CrownStats is tracking this format, but not yet enough distinct decks clear the sample floor to publish a ranking that would hold up.
19 deck-observable tracked battles · 0 decks above the sample floor
Triple Elixir
Not enough evidence yetA 1v1 variant in which Elixir generates at three times the normal rate.
Too few tracked battles so far to say anything meaningful about deck performance.
5 deck-observable tracked battles · 0 decks above the sample floor
Infinite Elixir
Collecting more dataA 1v1 variant in which Elixir is unlimited for both players.
CrownStats is tracking this format, but not yet enough distinct decks clear the sample floor to publish a ranking that would hold up.
12 deck-observable tracked battles · 0 decks above the sample floor
Rage
Not enough evidence yetA 1v1 variant in which the Rage effect is permanently active for both sides.
Too few tracked battles so far to say anything meaningful about deck performance.
A note on Draft
Draft
Drafted decks are built from cards offered during a pre-match pick phase rather than brought by the player, so CrownStats does not rank them with the standard Battle Type deck model. Measuring them fairly needs a different approach, not more battles.
Why CrownStats separates Battle Types
The rules differ, so the decks differ
Ranked equalises card levels; Ladder does not, which rewards a different kind of deck. 2v2 puts four decks and double the Elixir on one arena, so cards that need space behave nothing like they do in 1v1. These are not variations in difficulty — they are different games sharing a card set.
A blended average hides all of it
Pool every format together and a deck that is excellent in one and poor in another lands mid-table, describing neither. Splitting them is what makes a win rate answer a question a player can actually act on: how does this deck do in the format I am about to queue into?
A format is a CrownStats concept
Battle Types are curated by CrownStats rather than copied from an internal game identifier. That keeps a URL and a heading stable across seasons, even when the game reorganises how a mode is delivered behind the scenes.
Publishing is a separate decision
Tracking a format does not publish a ranking for it. A format needs enough deck-observable battles AND enough distinct decks clearing the sample floor before it earns a page — which is why some formats above are tracked with real battle counts and still not ranked.
Fresh Clash Royale deck data
CrownStats collects recent battles through the official Clash Royale API and recalculates Battle Type rankings throughout the day. Every ranking here is built from real battles observed in the CrownStats dataset rather than a hand-maintained deck list, which is why a format that stops being played goes quiet instead of staying frozen at its last good numbers.
Battles are collected several times a day and these figures recalculated after each collection, so they are refreshed throughout the day rather than streamed live. Both dates are shown because they can differ: a format nobody has played this week stays honestly stale even when the calculation ran minutes ago.
Across the 3 published Battle Types, these rankings currently draw on 230,214 deck-observable tracked battles from the last 30 days.
How CrownStats calculates these rankings
A sampled dataset, not every battle
CrownStats builds its statistics from battles collected through the official Clash Royale API for the players it tracks. That is a large sample, not a census — these are tracked battles, and win rates describe the decks observed in them rather than every game played worldwide.
Deck-observable battles
Not every battle can show a deck. A River Race Duel is played across three separate decks, so it never presents one eight-card deck to attribute a result to. Rankings are built only from battles that can actually produce a deck, and that is the number quoted as the evidence behind them.
Sample floor and confidence
A deck enters a ranking only once it has been observed at least 30 times in the window. Above that it is labelled Low Sample, Moderate Sample or High Confidence at 30, 100 and 500 appearances, so a lucky run over a handful of battles is never presented as a proven result.
The Meta score
The default ordering is a confidence-adjusted score — a Wilson lower bound — rather than raw win rate. It asks how low a deck's true win rate could plausibly be given how often it has been seen, which is why a 70% deck on 40 battles does not outrank a 58% deck on 4,000.
Each format counted separately
A deck is only credited with the battles it played in this format. Nothing is carried across from another Battle Type, and no figure here is an average blended across modes — which is exactly why the rankings differ between them.
Windows and freshness
Figures cover the last 30 days in UTC, and the current day is included while it is still filling — so the newest day is a partial count that grows through the day. Aggregates are rebuilt automatically several times a day; the most recent rebuild time is shown alongside the rankings.