LoL2LLM
← Back to all guides
Stat Fundamentals

Five Stats That Actually Correlate With Rank in Iron–Gold

5 min read · Published · Updated

Comments

KDA and win rate rarely tell you what to fix next. Five quieter numbers do — with measured JP1 solo queue medians by tier for CS at 10 minutes and control wards bought, and where to find each number after a game.

Annie

CHAMPION LENS

Annie

Champions in this guide
Garen
Amumu
Ashe
Leona

In Iron through Gold, KDA and win rate are the numbers everyone looks at, but they rarely tell you what to fix in the next game. Five quieter numbers do: you can check them every game and move them with your own decisions. Where we have data, the difference between ranks is shown as per-tier medians from JP1 solo queue (patch 16.20, n = 640 games).

Control wards bought, damage per death, and damage to turrets can be exported in LoL2LLM's JSON and handed to an AI. CS at 10 minutes and the time of your first death are not in the JSON, so check them in the replay and add them yourself.

1. CS at 10 minutes (lane-phase control)

Total game CS is noisy because game length varies; CS at 10 minutes says far more about your laning. The measured medians in the grid below tend to rise with tier. In Gold, the median is Top 64.0, Jungle 67.0, Mid 67.5, ADC 62.5, Support 14.0 (supports are low by design because they leave minions to their laner).

RoleIronBronzeSilverGoldPlatinumEmeraldDiamondMaster+n
Top57.063.562.064.069.070.070.074.0682
Jungle64.064.564.567.067.067.468.071.2681
Mid58.068.065.567.573.076.074.076.0690
ADC52.059.060.062.564.566.065.066.6679
Support11.012.014.014.013.513.014.014.0681

n = 640 games (3,413 player-games) · patch 16.20 · fetched Oct 20, 2026 · JP1 solo queue · games of 20+ min · medians

If you keep landing well below the median for your role and tier, the likely culprit is a persistent issue with wave management or positioning. The JSON has no CS-at-10 field, so scrub the replay to 10:00 and read it off the scoreboard.

"I'll catch up later" doesn't work. Twenty CS down at 10 minutes is roughly a Long Sword's worth of stats at first item, and that gap widens to a full item by mid-game team fights. Treat early CS as a compounding asset, not a checklist item you tick off when convenient.

2. Control wards purchased per game

Outside support and jungle, almost nobody buys control wards. Median control wards bought per game in Gold: Top 0.0, Jungle 3.0, Mid 1.0, ADC 0.0, Support 8.5. As the grid shows, top, mid, and ADC barely buy more as the tier goes up.

RoleIronBronzeSilverGoldPlatinumEmeraldDiamondMaster+n
Top0.00.00.00.01.00.00.01.0682
Jungle1.02.02.03.03.02.03.02.0681
Mid0.01.01.01.01.01.01.01.0690
ADC0.00.00.00.01.00.00.00.5679
Support8.08.08.08.58.59.010.012.0681

n = 640 games (3,413 player-games) · patch 16.20 · fetched Oct 20, 2026 · JP1 solo queue · games of 20+ min · medians

Because this number barely separates ranks, a laner who simply buys and places them out-wards most players at the same tier. Supports sit at 8.0 (Iron) to 12.0 (Master+) across tiers, so compare against your own tier.

One control ward eliminates almost all ambush risk before a drake. 75 gold to delete the "invisible enemies" problem is the highest gold-efficiency item in the game — but only if you actually place it. Carrying one in your inventory is not the same as benefiting from it.

3. First-death timing

If your first death keeps coming within five minutes, review your early positioning and the information you were working with. The cause is almost always one of three: pushing without enemy jungle vision, ignoring the opponent's summoner timers, or misjudging an early-game lane bully. Death times are not in the JSON, so check them on the replay timeline.

Start with ten games where the only goal is no avoidable deaths before 8 minutes. It is easy to track, and an early death is a triple loss — gold to the enemy, a forced recall, and a lost minion wave.

4. Damage per death

Damage to champions divided by deaths. KDA hinges on kill count; this captures "how much work did you do before dying." The AI can compute it from the damage and death counts in the JSON. We don't have per-tier benchmarks for it, and damage grows with game length, so compare it with your own past games on the same role, or with your lane opponent.

Only two ways to move this number: do more damage, or die less. Asking the AI to "compute damage per death for me and my lane opponent and tell me whether damage or deaths has more room to improve" isolates your real bottleneck.

5. First-tower participation (a team metric, but yours)

First tower isn't an individual stat, but it pays tower and plate gold and opens up the map. Support, jungle, and top especially — check whether you put pressure on a tower in the windows when you could leave your lane.

When your wave is shoved, check the next wave and the enemy positions, and decide whether you can bring numbers to a tower. Which team took first tower is not in the JSON, so check the replay. Export "Damage to Turrets" from the match page's Stats tab and ask the AI "how much did I contribute to my team's tower pressure?" — it can compare your turret damage with your teammates'.

Putting it together

Chasing KDA gives you no concrete next step; tracking these five does. After every game, add your CS at 10, your first-death time, and your tier's medians from the grids above, then prompt the AI: "compare my numbers on these five metrics against my tier's medians and tell me which one has the most room to grow." That output is your practice target for the next session.

Found this article useful? Leave a like, and share your thoughts or questions in the comments.

Try it on your own games

Search your Riot ID and export your match data as AI-ready JSON.


Comments

Loading comments…

Write a comment

0 / 1000

To prevent spam, we record your IP address and browser details when you post (they are never shown). Comments appear on every language version of this article, and posts that break our Terms of Service are removed.

Read another guide

Jinx
Stat Fundamentals · 9 min

What Is a Good CS Per Minute in LoL? CS/min Chart, Measured Medians by Rank, Calculation & Tips

What's a good CS per minute in LoL? In measured JP1 solo queue games, the median is 5.37 (Iron) to 7.51 (Emerald) for mid and 6.30 (Iron) to 8.08 (Master+) for ADC. See which tier's median 5-9 CS/min reaches, a CS chart for 15-30 minute games, CS at 10 minutes, and the four reasons CS/min drops.

Read
Garen
Stat Fundamentals · 4 min

LoL Beginner Stat Targets: Measured CS/min, KP, Vision and Deaths by Rank

Which numbers should a beginner actually aim for to climb in League of Legends? Measured medians for CS/min, kill participation, vision score, deaths, and damage share by rank and role from JP1 solo queue match data — and what to fix first.

Read
Samira
Stat Fundamentals · 4 min

What Is KDA? How to Calculate It and What Counts as a Good KDA (Measured by Rank)

How KDA is calculated in League of Legends, with measured median KDA by rank and role from JP1 solo queue match data, and why chasing KDA alone will mislead your climb — plus what to look at instead.

Read