Glossary
K/D and K/D/A
A ratio, not a threshold. Useful for form, poor as a betting line, and never a substitute for a count.
K/D is total kills divided by total deaths across the maps in the window. K/D/A adds assists to the numerator. Both describe play; neither can be bet directly, because no book prices a ratio over a window.
Why a ratio is not a line
A kill line asks about a threshold in a single map. K/D aggregates across maps and divides. A player can carry a healthy 1.3 K/D while missing a 20+ kill line in most maps, because the ratio rewards survival as much as it rewards volume.
Where it is useful
- Spotting a role change: a K/D that shifts while kill volume stays flat usually means a different position in the map.
- Sanity-checking a window: a stable K/D across 20 maps means the filter is not cherry-picking.
- Comparing teammates on the same maps rather than across careers.
Deaths and assists are shown per map alongside the ratio so you can see the components rather than trusting a single decimal.
Questions
- Does ClutchIQ price a K/D line?
- No. K/D is a descriptive ratio for the Research tables. Any stat line that gets graded is a count with a threshold and, where available, a stored or pasted price.
- Is a higher K/D always better?
- It usually correlates with better play, but it is not a verdict. A lurker who trades nothing can hold a high ratio while contributing fewer opening kills than an aggressive entry player with a lower one.
Related terms
- N+ kills
Per map, per player, one threshold. A 20+ line and a 22.5+ line are different bets about the same person.
- N+ headshots
A separate counter from kills. When the source did not store headshots, the rate is n/a rather than estimated.