5 min read · Published · Updated
Real ranked match data pulled from Faker's public account and run through AI analysis. The actual CS/min, damage share, and vision numbers of a pro, what they teach beginners, and every match ID so you can verify it yourself.

CHAMPION LENS
Cassiopeia
Sylas
Ahri
Yone
Azir"How good are a pro's numbers, really?" — let's answer that with real data, not guesses.
We pulled actual ranked games from Faker's public soloqueue account (Hide on bush #KR1) via Riot's official API and ran them through the kind of AI analysis LoL2LLM is built for. Every match ID is listed so you can verify it.
Source: Riot Games official API (Match-v5), ranked solo/duo (queue 420), patch 16.12, snapshot dated 2026-06-13. Account is Faker's public main "Hide on bush #KR1." This is a quotation of public game data and is not endorsed by or affiliated with Riot Games.
Match KR_8257207023 (36 min, result: loss). On Cassiopeia, Faker statistically dominated his Sylas opponent.
| Metric | Faker (Cassiopeia) | Opponent (Sylas) | Gap |
|---|---|---|---|
| KDA | 9 / 8 / 3 | 1 / 5 / 9 | +8 kills |
| CS (CS/min) | 327 (9.0) | 213 (5.9) | +114 (+3.1/min) |
| Gold | 16,942 | 11,395 | +5,547 |
| Damage to champions | 46,022 | 16,113 | ~2.9× |
| Damage share | 33% | — | team's top damage |
The CS gap is 114 (about 3.1 CS/min) and the damage is ~2.9×. As a lane, it's a blowout.
And it's still a loss. This is exactly the thing beginners misread — "I won lane but lost, it's my team's fault" — shown directly in a pro's own game.
Three points stand out in the numbers. If you hand the data (plus the in-game timeline) to an AI with "explain, for a beginner, what decided the result," check that its answer covers them:
The lane lead is there: CS/min, gold, and damage all crush the opponent. Lane-phase mechanics are not the problem.
8 deaths point to a "converting the lead" problem: being this far ahead yet dying 8 times suggests the lead was lost in fights/catches before it was turned into sidelane pressure or objectives.
Vision 42 / 2 control wards is the upside: this far ahead, the job is to light up the map and safely impose the lead. The ahead player benefits most from vision.
The key is not stopping at "good/bad KDA" — it's forming a hypothesis from the contradiction between signals (big lead × many deaths).
A single screenshot rarely gets an AI to that reading; structured data lets you ask for it directly.
Line up his six most recent games, played back to back from the evening of June 13 into the early hours of the next day (Korea time) — all mid, excluding a remake that ended about a minute in — and something more interesting shows up.
| Champ | KDA | CS/min | Damage share | Result |
|---|---|---|---|---|
| 6/6/5 | 9.8 | 21% | Loss | |
| 5/8/3 | 8.4 | 29% | Loss | |
| 3/6/2 | 7.3 | 33% | Loss | |
| 1/6/3 | 9.4 | 23% | Loss | |
| 9/8/3 | 9.0 | 33% | Loss | |
| 0/5/2 | 9.0 | 21% | Loss |
Match IDs (top to bottom, newest first): KR_8258023509 / KR_8257808312 / KR_8257747808 / KR_8257683403 / KR_8257207023 / KR_8257140210.
Apart from one game that ended in a surrender at 15 minutes (7.3), CS/min holds at 8.4–9.8, while deaths stay high at 5–8 every game across a six-game losing streak.
Even a top-of-the-world player can keep farming (CS/min) rock-steady while results slide — individual stats like CS/min and match outcome are surprisingly decoupled in the short run.
Looking across games surfaces a reproducible pattern ("the issue today is death management, not farm") that a single game can never reveal.
Winning lane and winning the game are different things. A CS lead is a prerequisite, not the win itself.
9.0 CS/min is "standard, not a spike" even for a pro. Which means it's the most reproducibly trainable metric at any rank (see the target-numbers guide).
CS/min barely moved during this six-game streak. One day of data can't prove anything, but it doesn't look like his farming fell off. In your own losing streaks, if CS/min holds, keep your head and keep queuing; if it drops, that's your signal to stop.
Never judge off one game. The repeating weakness only appears across several.
The "gap-to-opponent table" and the "multi-game line-up" shown here need no special tooling — LoL2LLM reproduces both.
Search your Riot ID, pick games, export the data, and ask ChatGPT or Claude to "anchor on the gap to my lane opponent and name two weaknesses that repeat across games."
A pro's numbers are best used as a benchmark to locate where you are — not as something to copy outright.
The same method is applied to pros in the other roles: Oner in the jungle, Keria at support, Gumayusi at ADC and Kiin at top. Reading them side by side shows how much the "pro standard" shifts from role to role.
Found this article useful? Leave a like, and share your thoughts or questions in the comments.
QiyanaReal Challenger match data from T1 jungler Oner's public account, pulled via Riot's official API and run through AI analysis. The actual CS/min, kill participation, and damage share of a pro jungler, and why jungle farm runs lower while KP runs higher, with match IDs you can verify.
Twisted FateReal Grandmaster match data from Gen.G top laner Kiin's public account, pulled via Riot's official API and run through AI analysis. The actual CS/min, kill participation, and damage share of a pro top laner, and why KP runs so much lower in the 'island' lane, with match IDs you can verify.
RenektonThe single biggest skill gap in League of Legends laning is minion wave management. A beginner-friendly breakdown of the three actions — freeze, slow push, crash — when to use each, and how to spot your own wave mistakes from CS difference with AI.