4 min read · Published · Updated
What kill participation (KP) means in League of Legends, how it's calculated, and measured median KP by role and rank from JP1 solo queue match data. 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" — a clue to the cause can show 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, the measured medians 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 heavily by role. Your natural level depends on how much your role is expected to be in fights.
The grid below is measured JP1 solo queue data: median kill participation by role and tier. Find your role's row and compare against the median at your tier.
| Role | Iron | Bronze | Silver | Gold | Platinum | Emerald | Diamond | Master+ | n |
|---|---|---|---|---|---|---|---|---|---|
| Top | 28.6% | 41.9% | 33.3% | 30.1% | 38.2% | 38.9% | 34.6% | 37.8% | 682 |
| Jungle | 47.1% | 50.0% | 49.3% | 55.7% | 54.7% | 51.6% | 52.0% | 54.5% | 681 |
| Mid | 42.9% | 43.3% | 48.0% | 46.4% | 43.1% | 43.0% | 44.3% | 47.2% | 690 |
| ADC | 45.5% | 52.6% | 50.0% | 45.6% | 51.5% | 53.3% | 48.3% | 49.4% | 679 |
| Support | 45.8% | 53.8% | 50.0% | 54.7% | 55.1% | 54.8% | 54.7% | 54.3% | 681 |
n = 640 games (3,413 player-games) · patch 16.20 · fetched Oct 20, 2026 · JP1 solo queue · games of 20+ min · medians
Across every role and tier the measured medians run from 28.6% (Top, Iron) to 55.7% (Jungle, Gold), and the lowest 25th-percentile cell is 20.7% (Top, Iron). If your KP keeps landing under the median for your role and tier in the grid, missing your team's fights is the first thing to suspect.
Measured targets for the other stats (CS/min, vision, deaths) 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.
Found this article useful? Leave a like, and share your thoughts or questions in the comments.
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. Measured in JP1 solo queue (patch 16.20, n = 640 games), median kill participation is 47.1% (Iron) to 55.7% (Gold) for jungle, 45.8% (Iron) to 55.1% (Platinum) for support, 42.9% (Iron) to 48.0% (Silver) for mid, 28.6% (Iron) to 41.9% (Bronze) for top, and 45.5% (Iron) to 53.3% (Emerald) for ADC (range of per-tier medians). Repeatedly landing under the median for your role and tier is a sign you are missing 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.
AzirKR and JP1 solo queue measured on the same patch 16.20: median deaths, KDA, kill participation, DPM, CS/min and vision score by tier and role, side by side. Below Master, KR games have more deaths and higher DPM with lower kill participation, while CS/min and vision are almost identical. Methodology and caveats included.
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.
CamilleSix 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.