Vision Score in League of Legends: What Good Looks Like per Role
Updated October 29, 2026 · 8 min read · by the LazyElo team
Vision score is the number on the post-game screen most players glance at and forget. That is a shame, because vision is one of the few parts of the game that clearly improves with rank, and one of the easiest to work on. This guide covers what the number measures, why your count matters less than the difference with the enemy, and what good vision looks like for each role.
What vision score measures
Vision score is Riot's measure of the vision you give your team and the vision you take away from the enemy: wards you place that stay up and see things, and enemy wards you clear. Riot doesn't publish the exact formula, so treat it as a rough total rather than a precise skill rating. Two practical points follow from how it works: a ward that survives and covers a used path counts more than one placed and instantly swept, and clearing the enemy's wards counts too.
Because the score keeps growing with game length, compare games by vision score per minute(vision score divided by the game's minutes), not by the total.
The difference is what wins, not the count
League of Graphs' warding stats make an interesting point. Raw ward counts barely line up with winning: games where a player placed 15 wards were won 38.6% of the time, and games with 60 wards 51.5%, a weak link for such a big difference in effort. The ward difference between the teams tells a much clearer story: from a 40.3% win rate at ten wards behind to 62.0% at fifteen ahead, after which it levels off.
So the goal isn't a number like “30 wards a game”. It is having more useful vision than the enemy, which means placing wards that live and clearing theirs. A support who places twenty wards that all get swept has done less than one who places twelve and clears eight.
What good looks like per role
There is no single good vision score; it depends on your role. A reasonable rule for any role: beat the vision score of your direct opponent, and beat your own average from your last 20 games in that role.
| Role | What good looks like |
|---|---|
| Support | The highest vision score on your team, game after game. Support vision clearly grows with rank: League of Graphs counts 26.3 wards per game for supports over all ranked players and 32.4 in Master and above. A control ward bought on every back, and the Oracle Lens trinket when your team needs enemy wards cleared. |
| Jungle | Usually second on the team. Your vision is about objectives and the enemy jungler: wards on their likely path before you gank, and control wards around the next dragon or baron. Jungler kill participation rises by 5 to 7 points from all ranks to Master+: higher-ranked junglers are in more of their team's fights. |
| Top and mid | A trinket ward used whenever it is ready, especially before you push past the middle of the lane, and a control ward in a river bush on most backs. Beat your lane opponent's score. |
| ADC | The lowest on the team is normal, but not zero vision. Use your trinket when your support is away, and ward your side lane before catching a wave alone later in the game. |
When to ward
Where you ward depends on the map state, but the moments are predictable. Ward:
- Before you push. The moment your wave goes past the middle of the lane is the moment a gank can reach you. A trinket ward in the river or the side bush first.
- Before objectives. Vision around the dragon or baron pit a minute or more before it spawns decides who gets to stand there. Clear their wards at the same time.
- When your jungler is coming. A ward deeper on the enemy jungler's path tells you whether the gank is safe, or whether it is about to become a 2v3.
- When you go to a side lane alone. Later in the game, a lone player catching a side wave without vision of who is missing is the easiest pick on the map. Ward before you farm.
Tools can count your wards, but not judge where they went: Riot's match timelines record that a ward was placed, not where. A request for ward positions has been open on Riot's developer tracker since 2019. Ward placement is something you check in a replay, not in a stats app.
Clearing: the other half of vision
Placing wards is only half of the score and half of the game. Every enemy ward you remove is information they no longer have, and the ward difference that tracks winning goes up just as much when theirs disappear as when yours appear. A few habits cover most of it:
- Sweep where you would ward. The bushes and river corners you like to ward are the same ones the enemy likes. Check them with a sweeper or a control ward before you place your own.
- Clear before you start an objective, not during it. A dragon taken while the enemy can see the pit is a dragon they can contest.
- Leave a control ward where it lives longest. A control ward that survives five minutes in a bush the enemy rarely checks keeps clearing and keeps scoring. One placed in the middle of a path gets killed on the next rotation.
If you play support or jungle, a simple check after each game is the number of wards you cleared. If it is close to zero, you were playing half the vision game.
The best vision stat: deaths without it
If you only track one thing, track your deaths without vision. An open-source analysis tool defines them simply: deaths with no ward of your own within 1,400 units. These are the deaths that a ward would most likely have prevented, and they are visible in every review: where did I die, and did I have a ward there?
That turns vision from a score you look at afterwards into something you do during the game. When you are about to walk into fog, ask yourself one question: do I know where their jungler is? If the answer is no, ward or wait. Waiting costs a few seconds; a death without vision costs the waves you miss, the gold you give and, often, the next objective.
In your review, go through your deaths before 14 minutes and mark each one: was there a ward of mine nearby? Most players find two or three of these per game at first. Getting that number to zero does more for your games than any vision score target.
Turn it into a goal
Vision makes a great first improvement goal because it is fully in your control, even in a game that is going badly. Write it as an if-then plan before the game, a form that has a well-documented effect on actually doing it (d = 0.65 across 94 tests):
- “If I go back, then I buy a control ward.”
- “If my trinket is ready and my wave is pushed, then I place it before I walk further.”
- “If dragon spawns within a minute, then I clear and ward its river side first.”
Track it for fifteen to twenty games, then compare your vision score per minute and your deaths without vision with where you started. The routine in how to get better at League shows how to run a goal like this.
LazyElo's review after each game shows your longest stretch without a ward and the ganks on you that came without a ward nearby, measured against your own average on that champion. On the Focus page you can make “a control ward on every back” your goal, and it checks after every game whether you did it.
Questions and answers
How is vision score calculated?
Riot doesn't publish the exact formula. Vision score adds up the vision you give your team and the vision you take away from the enemy: how long your wards stay up and see things, and the enemy wards you clear. A ward that survives on a path people use counts more than one swept right away. The total grows with game length, so compare games by vision score per minute.
What is a good vision score?
It depends on your role. A support should have the highest vision score on the team, a jungler usually the second highest, and a laner should beat their lane opponent. A simple test for any role: beat your direct opponent and your own average over your last 20 games in that role.
Sources
- League of Graphs, warding stats
- League of Graphs, warding stats for all ranked players
- League of Graphs, Lee Sin jungle stats, Master+
- hindsight-lol-analyser: deaths without vision
- Riot developer relations issue #160: ward positions in match timelines
- Gollwitzer & Sheeran (2006), implementation intentions and goal achievement