What tier is Solar Varus Reroll on TFT Set 18?

Solar Varus Reroll is currently Tier S on TFT Set 18, with a 3.54 average placement and 71% top 4 rate over 219 real ranked games analyzed.

TFT Set 18

Solar Varus Reroll= 0.08

Level 8

Sample confidence: Low (219 games). See how this is calculated →

Placement

3.54

Top 4

71%

Contest.

Full composition

Game Plan

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

Se poser au niveau 3 pour rerolls Varus, Leona, Akali, Camille, Ornn

Niveau qui minimise l'or nécessaire pour 1-coût(s) en même temps. Compter environ 90-116 or pour une chance de 25% à 75% d'obtenir toutes les copies visées (médiane ~102 or).

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

Solar 3

Ravager 2/4

Rapidfire 2/3

Inferno 2/3

Defender 2/4

Elderwood 1/3

Adaptor 1/2

Coven 1/3

Juggernaut 1/2

Item combos — main carries (top 10)

Varus

Combo	Avg placement
	3.81
	3.67
	2.88
	3.25
	2.50
	3.00
	3.00
	3.00
	3.25
	4.25

Akali

Combo	Avg placement
	3.33
	3.08
	3.62
	2.83
	2.50
	3.25
	2.50
	5.00
	2.67
	2.67

Seen on the TOP ladders

NA J or C#NA1 CHALLENGER 964 LP 1

NA Maple#Arrow CHALLENGER 822 LP 1

BR Mecmeno#AMOR CHALLENGER 1532 LP 1

BR Lefeco#br1 CHALLENGER 741 LP 1

KR 실력과운#본캐임 CHALLENGER 1605 LP 1

NA Phoenixaa#159 CHALLENGER 819 LP 2

BR To de atestado#0101 CHALLENGER 711 LP 2

EUW TTV KatsutaxD#TFT CHALLENGER 1454 LP 3

NA Phoenixaa#159 CHALLENGER 819 LP 3

NA ZmjjKK1#4316 CHALLENGER 813 LP 3

BR Sr Kapiroto#LEITE MASTER 263 LP 3

KR 종 범#TFT CHALLENGER 1155 LP 3

KR 빈 틈#123 CHALLENGER 907 LP 3

NA Broseph#LAB CHALLENGER 974 LP 4

NA Phoenixaa#159 CHALLENGER 819 LP 4

EUW Ken Kitade#Kash CHALLENGER 960 LP 5

EUW Garkes#EUW CHALLENGER 861 LP 5

EUW Rayan Cherki#PAWS CHALLENGER 766 LP 5

NA title#1951 CHALLENGER 766 LP 5

BR JuanGhurkas#Doom CHALLENGER 1341 LP 5

Matchups vs

vs Caustic Aphelios 84 encounters 68%

vs Caustic Nidalee 47 encounters 72%

vs Riftbeast Pebbles 46 encounters 67%

vs FloraFatalis Azir 45 encounters 67%

vs Emerald Ahri 42 encounters 71%

vs Emerald Morgana 41 encounters 66%

vs Summoner Zyra 41 encounters 73%

vs Juggernaut Zyra 39 encounters 59%

vs Elderwood Ezreal 38 encounters 55%

vs Greenfather Ezreal 34 encounters 50%

vs Invoker Morgana 30 encounters 60%

vs Riftbeast Cinderling 29 encounters 55%

vs Invoker Ahri 27 encounters 74%

vs FloraFatalis Kha'Zix 25 encounters 48%

vs Defender Cassiopeia 25 encounters 68%

vs Juggernaut Sivir 22 encounters 77%

vs Greenfather Sentinel 22 encounters 55%

vs Summoner Soraka 20 encounters 70%

vs Greenfather Morgana 20 encounters 55%

vs Blossom Ahri 20 encounters 80%

Board variants

Baseline

4.75 avg placement

→

2.92 avg placement

→

3.04 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 — 7 units 4.75 avg placement · 51 games

+1 unit (8 total)

Amumu 2.92 avg placement · 24 games

Kog'Maw 3.04 avg placement · 22 games

Ivern 2.90 avg placement · 10 games

Vi 4.17 avg placement · 6 games

Nidalee 2.20 avg placement · 5 games

+2 units (9 total)

Amumu + Kog'Maw 1.50 avg placement · 4 games

Kog'Maw + Rakan 1.50 avg placement · 2 games

Ivern + Kog'Maw 2.00 avg placement · 2 games

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.