LoL2LLM
← Back to all guides
Real Pro Data
Real data

What Are a Pro ADC's CS/min, KP, and Vision Numbers? Gumayusi's Real Data, AI-Analyzed

3 min read · Published · Updated

Comments

Real Challenger match data from Worlds-winning ADC Gumayusi's public account, run through AI analysis. The actual CS/min, kill participation, damage share, and control-ward counts of a pro ADC, with match IDs you can verify.

Jhin

CHAMPION LENS

Jhin

Champions in this guide
Mel
Miss Fortune
Caitlyn
Jinx

"As an ADC, what numbers should I actually be hitting?" Let's check with the real Challenger games of Gumayusi, a Worlds-winning top-tier ADC.

We pulled real data from his public account (HLE Gumayusi #0298, Challenger) via Riot's official API and ran it through the kind of AI analysis LoL2LLM is built for. Every match ID is verifiable.

Source: Riot Games official API (Match-v5), ranked solo/duo (queue 420), patch 16.12, snapshot dated June 10–14, 2026. Account is the Challenger-tier public account "HLE Gumayusi #0298." This is a quotation of public game data and is not endorsed by or affiliated with Riot Games.

The headline: a pro ADC's CS/min is around 10

Take three of his bot-lane games from this period and CS/min sits at 9.4–10.4.

Using ~8 as a rough Platinum ADC benchmark for comparison, that works out to 1.4–2.4 CS/min ahead.

ChampKDACS/minKPDamage shareResult
MissFortuneMiss Fortune7/2/610.481%28%Win
JhinJhin7/4/1310.074%29%Loss
MelMel (bot)4/8/29.432%24%Loss

Match IDs (top to bottom): KR_8253869107 / KR_8259131396 / KR_8255010684.

Case study: perfect farm and KP on Jhin — and a loss

Match KR_8259131396 (30 min, loss). Here's the comparison to the enemy ADC (Mel).

JhinGumayusi · JhinVSMelvs · Mel
MetricGumayusi (Jhin)Enemy ADC (Mel)
CS (CS/min)302 (10.0)248 (8.2)
Kill participation74%—
Damage share29%—
Control wards6—

+54 CS, 74% KP, 29% damage share — a flawless ADC line. And still a loss.

Just like the Faker games (separate guide), individual excellence and the result are decoupled in the short run, even in a pro's own data.

What the data shows that's ADC-specific

Three things an ADC can copy today

To see how far your ADC numbers are from a pro's, export a game with LoL2LLM and ask the AI to "compare my CS/min, KP, damage share, and control wards to a pro ADC benchmark (10 CS/min, 70% KP, 28% share, 6 wards)."

For concrete targets, see beginner stat targets by rank; for the positioning side of the role, see ADC positioning: what KDA hides; and for the support half of the lane, see Keria's real support data.

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

Camille
Real Pro Data · 6 minReal data

Keria's Real Data: A Pro Support's Vision Score and Kill Participation vs KR Master+

Six support games from T1 Keria's public account (Keria #4111 when fetched, now Keria #zxcv), pulled via Riot's official API. His median vision score per minute (3.98) and damage share (17.8%) compared with measured KR Master+ supports, plus what to track when CS/min doesn't apply, with match IDs you can verify.

Read
Jinx
By Role · 4 min

ADC Positioning: What KDA Hides and Damage Share Reveals

An ADC's real job is sustained damage in fights, not staying alive. Four metrics that catch the “safe but useless” pattern KDA can't see — with measured JP1 solo queue damage-share medians by tier.

Read
Jinx
Stat Fundamentals · 6 min

LoL Damage Explained: Damage Types, DPM vs DPS, and Damage Share by Role

How damage works in League of Legends: physical, magic and true damage and how armor/MR reduce them, total damage vs damage to champions, DPM vs DPS, measured medians by role and rank from JP1 solo queue, and how to calculate damage share from your match JSON.

Read