What is CS/min in League of Legends, and Why Coaches Track It
In SoloQ, players look at KDA.
In scrims, coaches look at CS/min.
Not because farming is "basic", but because it's one of the cleanest performance signals you can track across games. This article breaks down what CS/min actually measures, why it matters more than KDA in most reviews, and how coaches use it to diagnose macro issues.
What CS/min actually measures
CS/min is a measure of gold generation consistency over time.
The formula is simple: Total CS divided by game time. A player sitting at 180 CS at 18 minutes has a 10 CS/min. This accounts for lane minions and jungle camps when relevant to the role.
It's not a mechanic stat. It's a resource efficiency metric.
Why CS/min matters more than KDA in reviews
KDA is volatile. It depends on draft, on jungle pathing, on fights you don't fully control.
CS/min is stable. Every wave is predictable. Every missed CS is accountable. Every drop is explainable.
In practice
Take two mid laners. Player A goes 4/1/2 with 6.2 CS/min. Player B goes 1/0/1 with 9.1 CS/min. In most comps, Player B hits item spikes earlier and controls mid-game tempo.
Coaches don't ask "Who got kills?" They ask "Who generated gold reliably?"
What good CS/min looks like (context matters)
Raw numbers without context are useless.
Baseline targets sit around 8 to 10 for solo lanes in a stable matchup, 9 to 11 for ADC in a low pressure lane, and vary for junglers depending on pathing.
But real evaluation depends on matchup pressure, jungle proximity, lane assignments like swaps, freezes or weakside duty, and game state. A 7.5 CS/min in a losing matchup can be cleaner than a 9.5 in a free lane.
Why coaches track CS/min
Not for the number itself. For what it reveals.
Wave management
Low CS/min often points to bad crash timings, missed bounce setups, or poor side lane collection. When a player consistently loses minions, it's rarely about last-hitting. It's about how they handle the wave before and after trades.
Recall discipline
Every bad reset costs one to two waves. Coaches look for patterns: recalling on a slow push and losing the stacked wave, or recalling too late and being forced into a TP that bleeds tempo.
Map movement
CS drops usually correlate with unnecessary roams, late rotations, or grouping without wave setup. If your CS/min dips after 12 to 15 minutes, it's often a macro issue, not mechanics.
Role understanding
ADCs dropping CS in mid-game signals bad lane assignment. Mid laners missing side waves reveals poor tempo sync. Top laners over-grouping means lost sidelane value. CS/min exposes role misuse instantly.
What low CS/min actually signals
Players say "I miss CS sometimes." In review, it's usually something deeper: incorrect wave priority, bad lane resets, tempo desync with the team, overcommit to low-value fights, or no side lane discipline.
CS/min is not the problem. It's the symptom of macro leaks.
How coaches use CS/min in practice
CS/min is never used alone. It's tracked alongside CS at 10 and 15 minutes, gold diff at 15, wave states before recalls, and lane assignment timelines.
The typical workflow goes like this. First, identify the CS drop timing. Then check the wave state right before the drop. Review the decision that caused it, whether it was a recall, a roam, or a fight. Finally, link it back to the macro error.
The stat gives the timestamp. The VOD gives the reason.
How to improve CS/min (without grinding last-hit drills)
For competitive players, improvement is macro-driven.
Fix your recalls. Don't reset when there's a slow push moving away from you, or when a stacked wave is about to crash into your tower.
Respect side lanes. Mid-game rule: if a wave is dying on a side lane, someone is inting tempo.
Stop coinflip roams. Before moving, ask yourself what wave you're giving up and what you gain from the play.
Track your drop points. Don't just track average CS/min. Track when it drops and why it drops. That's where the real insight lives.
Why this matters for performance tracking
CS/min scales across SoloQ, scrims, and stage games. It's reproducible, comparable, and actionable. That's why it's the go-to metric in coaching environments.
Final take
KDA tells you what happened. CS/min helps you understand why your game state looks the way it does.
If your CS/min is unstable, your macro is unstable.
From stat to insight
Tracking CS/min manually gives you numbers. It doesn't give you wave context, decision quality, or macro patterns.
That's where tools like VictoryView come in. Instead of just seeing "7.2 CS/min", you see where you dropped waves, which decisions caused it, and how it impacts your tempo.
That's the difference between tracking stats and actually improving.