Analytics Glossary

Every metric RunChase shows, in plain terms โ€” what it measures, and how to read it without over-reading it. Small samples say less than big ones; where that matters, it's flagged.

Batting
Strike Rate (SR) Batting
Runs scored per 100 balls faced โ€” runs รท balls ร— 100. The core measure of scoring speed in T20.
How to read it: elite T20 batters cluster tightly around 140โ€“155, so gaps that look big in the raw number are often smaller than they seem once you account for role and phase.
Batting Average Batting
Runs scored per dismissal โ€” runs รท times out. A measure of how long a batter tends to survive, independent of speed.
How to read it: high average + high strike rate is the rare combination. Average alone rewards not getting out, which isn't always the T20 job โ€” pair it with SR and role.
First 10 Balls SR (f10) Batting
Strike rate over just the first 10 balls a batter faces in an innings โ€” how fast they get going before they're set. Computed directly from each innings' real ball-by-ball start, not estimated from innings totals.
How to read it: separates fast starters from players who need time. A low f10 with a high overall SR means a batter who accelerates once in; the reverse can flag someone who front-loads risk.
Boundary % & Dot Ball % Batting
Share of balls faced that went for four or six (boundary %) versus the share that brought no run (dot %). Two sides of the same tempo coin.
How to read it: a high boundary rate carried by a high dot rate is a high-risk profile โ€” big shots between pressure balls. A low-dot, lower-boundary profile is a rotator who keeps the score ticking.
Context & Pressure
Phase Splits โ€” Powerplay / Mid Overs / Death Both
Performance broken out by the three T20 phases: the fielding-restricted Powerplay (overs 1โ€“6), the Mid Overs (7โ€“15), and the Death (16โ€“20). Each phase asks a different question of a player.
How to read it: a single overall number hides where a player actually does their work. A death-overs strike rate matters far more for a finisher than a Powerplay one.
Pressure Bands โ€” High / Medium / Low Batting
Splits a batter's record by how much pressure the match situation applied at the time โ€” chase demands, wickets in hand and overs remaining โ€” bucketed into high, medium and low. Answers "how do they bat when it's hard?" rather than "how do they bat on average?"
How to read it: a strike rate that holds up in the high band is the signal to look for. A record built mostly in low-pressure situations is a genuinely easier record, even at the same headline number.
Bowling
Economy Rate Bowling
Runs conceded per over โ€” runs รท overs. The primary containment measure for a bowler.
How to read it: always read it against phase. A death bowler's economy will look worse than a Powerplay specialist's because the job is harder, not because the bowler is.
Bowling Strike Rate & Balls per Wicket Bowling
How often a bowler takes a wicket โ€” balls bowled per dismissal. Lower is better: a wicket-taker rather than a container.
How to read it: pairs with economy to place a bowler on the attack-vs-control spectrum. Some bowlers buy wickets with runs; others strangle without striking.
Benchmarks
Percentile Rank Both
Where a player sits against every other qualifying player on a given metric. A 90th-percentile strike rate means faster than 90% of the field; the benchmarks are regenerated on the full, cleaned dataset.
How to read it: percentiles turn a raw number into "is that actually good?". Because elite fields bunch up, moving from the 70th to the 95th percentile can be a much smaller raw gap than it feels.
Comparison & Significance
League-Strength Normalisation Batting
Adjusts for the fact that runs in a weaker competition are easier to score than runs against international attacks. Built with within-player fixed effects โ€” comparing the same players across the competitions they've all played โ€” so it isn't fooled by who happens to play where.
How to read it: this is why internationals correctly come out as the hard end of the scale, not the easy one. A raw number flattered by a weak league gets pulled back toward its true worth.
Significance Testing (Bootstrap) Batting
Resamples the innings thousands of times to ask whether a gap between two players is real or just noise from a limited number of innings. Produces a spread of likely outcomes rather than a single false-precise verdict.
How to read it: if the resampling split lands near 50/50, the two players are effectively the same on that metric โ€” the difference you see is within the margin of error, not a ranking.
Single-Innings Spread (Box Plots) Batting
Shows the full distribution of a player's innings โ€” median, the middle 50%, and the tails โ€” not just their average. Two players with identical averages can have completely different spreads.
How to read it: a wide spread is a boom-or-bust player; a tight one is a metronome. On any given night, the spread tells you more about what you'll actually get than the average does.
Type & Matchups
Pace vs Spin Split Batting
A batter's strike rate and dismissal rate separated by bowler type. Shown only when enough of the deliveries faced are classified โ€” below that coverage the split is hidden rather than guessed at.
How to read it: a clear gap (roughly 15+ SR) between pace and spin is a real vulnerability worth planning around. When coverage is low, treat a split with caution โ€” or its absence as honesty rather than a gap in the data.
Matchups & Nemesis Batting
A batter's best and worst records against individual bowlers they've faced enough times (โ‰ฅ25 balls). A "nemesis" is a bowler who has dismissed them 3+ times. Head-to-head records are career-wide across all competitions.
How to read it: ball count is everything here. A brutal strike rate over 26 balls is a small-sample curiosity; the same over 120 balls is a genuine pattern. The number of balls is always shown so you can weight it yourself.