7 min read
What kill participation (KP) means in League of Legends, how it's calculated, and typical averages and targets by role. Why farming alone loses, what to fix when your KP is low, and how to analyze your own games with AI.

CHAMPION LENS
Nautilus
Lee Sin
Ashe
Tryndamere
Fiora"I farm fine but still lose" — the cause often shows up in one stat: kill participation (KP).
KP is a single number for how often you were part of the plays where your team was fighting.
This guide covers how KP is calculated, typical averages by role, and the traps that make KP misleading if you read it alone.
KP is (your kills + your assists) ÷ total team kills × 100.
So in a game where your team got 20 kills and you had 4 kills and 8 assists, that's (4 + 8) ÷ 20 = 60%.
A kill and an assist both count as one "participation," so you don't need the finishing blow — being in the fight is enough.
Conversely, when teammates take a kill while you're farming elsewhere, you weren't part of it, and your KP drops.
KP is driven more by role than by rank. Your natural level depends on how much your role is expected to be in fights.
The table below is a loose solo-queue reference — a feel, not a precise statistic.
| Role | Target KP | Note |
|---|---|---|
| Jungle / Support | 60%+ | Roaming roles; low KP means low impact |
| Mid | 55%+ | Are your roams affecting side lanes? |
| ADC / Top | 50%+ | Are you dealing damage in teamfights? |
As a rough rule, dropping below 50% means you missed half of your team's fights — the first number worth questioning.
Finer targets by rank and role are in stat targets by rank.
KP also swings with a champion's job. It runs high on champions that start fights or apply pressure across the map.
By contrast, split-pushers who pressure a side lane alone deliberately leave the group, so their KP runs low. That isn't "bad" — it's the strategy working.
So comparing a split-pusher's 45% to an engage support's 65% tells you nothing. The useful read is whether you're above or below normal for that champion and role.
KP has a few traps where a high number means less than it looks.
It depends on total team kills: 5 participations in an 8-kill game (62%) and 12 in a 20-kill game (60%) are very different workloads at the same "rate."
It can't measure quality: the play that decided a teamfight and a single spell tagged from range both count as the same "1."
Forcing it backfires: throwing yourself into bad fights to pad KP racks up deaths and kills your win condition. The number and the win rate don't always agree.
So read KP alongside death timing, CS difference, and damage dealt rather than on its own.
For how the stats relate, see metrics that correlate with rank; for how KP differs from KDA, see what is KDA.
Once you know KP is low, translate it into why you couldn't join.
The usual causes are three: roaming and grouping for objectives too late, poor wave management that pins you to lane, and no vision so you commit to fights too slowly.
Export a game as JSON with LoL2LLM and you get both total team kills (teamMacro) and your own line (combat). Ask an AI to open up the number:
From this match data, compute my kill participation and tell me whether a low or high KP came from roam timing, grouping for objectives, or wave management.
KP is (your kills + your assists) divided by total team kills, times 100. For example, in a game where your team got 20 kills and you had 4 kills and 8 assists, that's (4 + 8) / 20 = 60%. A kill and an assist each count as one participation.
It depends on role. Rough targets are 60%+ for jungle and support, 55%+ for mid, and 50%+ for ADC and top. Dropping below about 50% is a sign you missed half of your team's fights.
Yes. Engage supports and mobile junglers join fights easily and run high, while split-pushers who pressure a side lane alone deliberately leave the group and run low. A low KP on a split-pusher is the strategy working, not a mistake.
Not necessarily. KP depends on total team kills and can't distinguish a fight-deciding play from a spell tagged at range. Forcing participation into bad fights racks up deaths and hurts your win condition. Read KP alongside death timing, CS difference, and damage dealt.
GarenWhich numbers should a beginner actually aim for to climb in League of Legends? Realistic targets for CS/min, kill participation, vision score, deaths, and damage share by rank and role — and what to fix first.
AhriRead the post-game scoreboard the way a coach would. Role-aware benchmarks, what each number actually measures, and how to combine them before handing the JSON to an AI.
SamiraHow KDA is calculated in League of Legends, what a good KDA looks like by rank and role, and why chasing KDA alone will mislead your climb — plus what to look at instead.