CS/min: The Most Honest Metric in Competitive League of Legends

Stats can lie. A player with a 70% win rate might be getting carried. A player with a high KDA might be playing safe and avoiding fights. But CS/min? CS/min is hard to fake.

Every minion you last-hit is a data point. Miss it and the number drops. Hit it and it counts. There's no teammate to inflate the stat, no lucky Baron steal to pad it. CS/min is pure mechanical execution — and that's why it deserves its own deep dive.

What CS/min actually measures

On the surface, CS/min (creep score per minute) counts how many minions and monsters a player kills per minute of game time. Simple enough.

But what it really measures is a combination of things that are hard to see in a VOD review:

• Laning fundamentals — can the player secure last hits under pressure, under tower, and while trading?
• Wave management awareness — are they catching side waves, or letting gold crash into towers uncontested?
• Game state decision-making — after laning phase, do they keep farming between objectives, or do they ARAM mid and bleed gold?
• Consistency under pressure — does their CS/min hold steady in losing games, or does it collapse when they fall behind?

A player who maintains 8+ CS/min even in losses is telling you they don't mentally check out. That's valuable information.

Benchmarks by role

Not every role farms the same, and comparing a support's CS/min to an ADC's is meaningless. Here's what competitive and high-elo benchmarks look like as a reference point:

ADC

ADCs have the most consistent access to minion waves. If your AD carry is below 8.0 in SoloQ, that's a laning issue worth investigating — not a team problem.

Mid lane

Mid laners often sacrifice CS for roams. A mid with 7.2 CS/min who's creating advantages elsewhere is fine. A mid with 7.2 CS/min who's just losing the lane is not. Context matters — that's why you cross-reference with damage/min and kill participation.

Top lane

Top lane CS/min varies wildly depending on champion pick. A Sion or Gangplank should be pushing high numbers. A Renekton who's roaming and diving will naturally sit lower. Compare within champion archetypes, not across them.

Jungle

Jungle CS includes camps and any lane minions picked up. A jungler with high CS/min is pathing efficiently and not wasting time. A jungler with low CS/min is either ganking constantly (check their kill participation) or simply falling behind in tempo.

Support

Support CS/min is generally irrelevant — most supports shouldn't be taking farm. If your support's CS/min is notably high, that might actually be a problem worth a conversation about wave management habits.

Why the trend matters more than the number

A single CS/min value tells you very little. A player averaging 8.0 CS/min could be:

• Consistently hitting 8.0 every game (great)
• Alternating between 9.5 and 6.5 (inconsistent — why?)
• Slowly declining from 8.5 three weeks ago to 7.5 now (red flag)

This is where time-window filtering becomes essential. Compare the last 7 days against the last 30 days:

• 7-day CS/min higher than 30-day average — the player is trending up. They might be in good form, or they've switched to a more farm-heavy champion pool.
• 7-day CS/min lower than 30-day average — something changed. Fatigue? Tilt? New champion picks they haven't mastered yet? Start asking questions.
• Both numbers stable and close together — consistency. This is what you want from a roster player.

SoloQ vs. Scrim CS/min — the gap that reveals everything

One of the most telling comparisons you can make is between a player's SoloQ CS/min and their scrim CS/min.

SoloQ CS/min significantly higher than scrim CS/min? The player might be struggling with the coordinated pressure of scrims — lane swaps, jungle attention, and draft matchups they don't face in SoloQ. Or they might be too focused on team plays and neglecting their own farming patterns.

Scrim CS/min higher than SoloQ? Less common, but it happens when a player is more disciplined in a structured environment. It can also mean they're autopiloting in SoloQ and not treating it seriously.

Both roughly equal? The player is consistent regardless of context. That's your most reliable roster member.

How to act on CS/min data as a coach

Raw numbers need to become coaching actions. Here's a practical framework:

Sudden drop (> 0.5 CS/min decline over 7 days)

Don't bench — investigate. Pull up their last 10 games and check:

1. Did they switch champions? New picks often come with a temporary CS dip.
2. Are they facing harder matchups? Check opponent rank distribution.
3. Is the game duration shorter? Shorter games naturally compress CS/min as early game chaos takes over.
4. Is there a pattern in specific matchups? Some lanes are just hard to farm in.

Chronic low CS/min (consistently below role benchmark)

This is a fundamentals issue. Consider:

• 1v0 practice — 10 minutes of farming in practice tool before every session. Set a target (e.g., 90 CS at 10 minutes with no items).
• VOD review focused on CS — watch their laning phase at 2x speed with the CS counter visible. Where are they missing? Under tower? During trades? After recalls?
• Wave management theory — some players have the mechanics to last-hit but don't understand when to freeze, slow push, or shove. This is coachable.

High CS/min but low impact

Sometimes a player has great CS/min but low damage/min and low kill participation. They're farming well but not converting gold into impact. This is a different problem entirely — it's not about the CS, it's about what they do with the gold.

The 10-minute benchmark

A useful shortcut for quick assessment: check CS at 10 minutes. At the 10-minute mark, 114 minions have spawned in a solo lane (107 in bot lane per player). Here's the quick math:

• 80+ CS at 10 — strong laning, missing very few
• 70–80 CS at 10 — average, room to improve
• 60–70 CS at 10 — weak, losing meaningful gold
• Below 60 CS at 10 — something is very wrong in this lane

This won't show up in post-game CS/min, which includes mid and late game farming. But it isolates laning phase — where mechanical CS ability is most clearly visible.

Start tracking CS/min across your roster

Checking CS/min once tells you where a player is. Tracking it over time tells you where they're going.

With VictoryView, you can filter by player, by queue type, and by time window to see exactly how CS/min is trending. Import your team's recent matches, and you'll see at a glance who's sharpening their fundamentals and who needs a focused practice block.

No spreadsheets. No manual op.gg checks. Just the numbers your coaching staff needs to make better calls.