BrokenMeta.gg
WoW: ForeverWoW: Forever Teamfight TacticsTFT League of LegendsLoL
FR EN
HM
TFT Set 18

Executioner Ahri▲ 0.45

Level 9
Placement
4.15
Top 4
62%
Contest.
83

This comp was Tier A in a previous refresh (last seen Sep 22), but doesn't get enough recent games to stay actively ranked this cycle. Kept here for reference.

Full composition

Ornn
Yunara
StrikersFlailKrakensFuryThiefsGloves
Alistar
Fiddlesticks
IonicSparkBrambleVestThiefsGloves
Ahri
SpearOfShojinEmblemExecutionerJeweledGauntlet
Soraka
Sett
Ezreal
Kennen

Game Plan

Each step's detail is currently only generated in French.

Niveau 9, quelques rerolls suffisent

Aucun carry à 2-3★ dans cette compo : médiane ~70 or pour compléter le board.

These numbers assume a solo player with no contest from other players in the lobby. Real contest on these champions can make these estimates optimistic.

Traits

Executioner Executioner 4
Elderwood Elderwood 3/5
Blossom Blossom 3/5
Brawler Brawler 2/4
Defender Defender 2/4
Spellweaver Spellweaver 2/4
Flora Fatalis Flora Fatalis 2
Inferno Inferno 1/2

Item combos — main carries (top 10)

Ahri
Ahri
ComboAvg placement
EmblemExecutionerRabadonsDeathcapSpearOfShojin
5.39
EmblemExecutionerJeweledGauntletSpearOfShojin
2.67
EmblemExecutionerSpearOfShojinVoidStaff
3.50
JeweledGauntletSpearOfShojinStrikersFlail
4.80
EmblemExecutionerGiantSlayerSpearOfShojin
5.20
ArchangelsStaffEmblemExecutionerSpearOfShojin
2.75
JeweledGauntletSpearOfShojinVoidStaff
5.67
JeweledGauntletRabadonsDeathcapSpearOfShojin
4.00
AdaptiveHelmEmblemExecutionerJeweledGauntlet
2.67
EmblemExecutionerHextechGunbladeSpearOfShojin
5.50

Seen on the TOP ladders

KR baobao fan#xuxu CHALLENGER 1038 LP 2
NA GambaGoblin#1649 CHALLENGER 616 LP 3
BR HIGH Hatsu#3030 CHALLENGER 508 LP 3
NA inflames#TFT CHALLENGER 722 LP 4
BR FOUR Bala#FOUR GRANDMASTER 500 LP 4
KR 뽀뇨뽀뇨#1218 CHALLENGER 847 LP 5
EUW SLY Voltariux#EUW CHALLENGER 1266 LP 6
NA Nik#0283 CHALLENGER 1232 LP 6
BR Alberoni#TFT GRANDMASTER 441 LP 6
KR 너무멋있어영#KR1 CHALLENGER 968 LP 7
BR FOUR vakio#br1 CHALLENGER 514 LP 8
BR Teteuso10#BR1 GRANDMASTER 480 LP 8
KR Nodme#111 CHALLENGER 824 LP 8

Matchups vs

vs Caustic Aphelios 29 encounters 76%
vs FloraFatalis Azir 25 encounters 52%
vs Juggernaut Zyra 25 encounters 52%
vs Caustic Nidalee 20 encounters 45%
vs Summoner Zyra 17 encounters 71%
vs Emerald Morgana 17 encounters 35%
vs Defender Cassiopeia 17 encounters 47%
vs Elderwood Ezreal 16 encounters 50%
vs Riftbeast Pebbles 14 encounters 43%
vs Invoker Morgana 14 encounters 64%
vs Emerald Ahri 13 encounters 15%
vs Greenfather Ezreal 13 encounters 31%
vs Greenfather Amumu 12 encounters 50%
vs Riftbeast Cinderling 11 encounters 9%
vs Juggernaut Sivir 11 encounters 36%
vs Greenfather Aphelios 9 encounters 44%
vs Greenfather Morgana 9 encounters 44%
vs Executioner Ezreal 9 encounters 56%
vs Summoner Soraka 9 encounters 56%
vs Rapidfire Aphelios 9 encounters 67%

Board variants

AhriEzrealFiddlesticksGnarKennenOrnnSettSorakaYunara
Baseline
7% of games 2.12 avg placement
AhriAlistarEzrealFiddlesticksKennenOrnnSettSorakaYunara
Gnar
→
Alistar
5% of games 4.83 avg placement
AhriAlistarEzrealFiddlesticksOrnnSettSorakaYunara
GnarKennen
→
Alistar
4% of games 5.00 avg placement
Real versions of this comp's final board: which exact group of champions shows up together, how often, and the average placement of those games. Not a game-by-game history (Riot only exposes the end-of-game board, never how it got there): a comparison of builds, not a timeline.

Board add-ons (9th/10th unit)

Base board — 9 units 4.83 avg placement · 6 games
Not enough games with an extra unit for a reliable signal.
The main board above stops at 9 units: reaching a 10th slot needs level 10, which on its own already correlates strongly with a good placement. Below, the average placement of games with this base board plus one or two extra units, shown as a correlation to interpret, not a causal recommendation.

Augment path

Data unavailable. Riot's API doesn't populate the augments field for this set — verified directly on the collected sample (the "augments" field doesn't even appear in the response, across 23,000+ real participants checked). The field does exist in the official schema and worked on older sets, so this probably isn't permanent — this section will activate automatically as soon as it fills in again.