Cricket Stats Calculator — Run Rate and Strike Rate

Why overs are not decimals

An over is six balls, so cricket's .1 to .5 notation counts balls, not tenths. 28.3 overs is 28 and a half overs, or 28.5 in decimal — not 28.3.

This trips up spreadsheet calculations constantly: dividing runs by 28.3 instead of 28.5 inflates the run rate slightly. This calculator converts the notation properly before dividing, which is why its numbers match the scoreboard.

Run rate in a chase versus setting a total

Batting first, run rate is a pacing tool: you are trying to project a defendable total from where you are now. Chasing, it becomes a deadline, because the required rate is fixed by runs and overs remaining and climbs with every quiet over.

That asymmetry is why chasing sides talk about keeping the required rate within reach of the current rate. Once the gap grows beyond about two runs an over, the batting side has to take risks, and wickets usually follow.

The same words mean opposite things

Cricket uses 'strike rate' for both batters and bowlers, and the two run in opposite directions. For a batter it is runs per 100 balls, so higher is better and signals fast scoring. For a bowler it is balls per wicket, so lower is better and signals frequent breakthroughs.

A batter with a strike rate of 140 is destructive; a bowler with a strike rate of 140 is barely taking wickets. Always check which one you are reading.

What a good strike rate looks like by format

Batting strike rate is runs per 100 balls; bowling strike rate is balls per wicket, where lower is better. The same batting number can be excellent or reckless depending on format, which is why context matters more than the raw figure.