Batting
Read a strike rate alongside the innings
Strike rate is runs per 100 balls, which makes it a measure of pace and nothing else. Here is how to calculate it, combine it and read it against the match situation.
Start with the scorebook question
Most calculation mistakes begin before the division: using team runs for bowling economy, reading overs as a decimal, or adding a batter’s earlier runs to a new partnership. These guides work through those decisions step by step, and every guide ends with practice questions and answers.
All match examples are fictional. The ten calculators work from the figures you enter; they do not fetch live scores or certify match results. If you spot an error, tell us and we will check it.
By CricketCals · Updated
All guides
Rain interruptions
A rain target is about resources, not an overs ratio
When rain cuts a match, overs and wickets both change what a team can score. This guide explains the resource idea behind DLS and works through the arithmetic with simplified numbers.
Bowling
Check the runs column before judging a bowling spell
A bowler’s economy rate uses the runs charged to them, not the runs the team added. Here is how to read the analysis column, convert overs correctly and combine spells.
Chasing
A quiet over changes the asking rate: work it through
The asking rate in a chase moves with every ball. This guide works through a 20-over chase step by step so you can recalculate it yourself from the score and balls left.
Tournament figures
Why averaging match run rates can mislead
Net run rate compares how fast a team scores with how fast it concedes across a whole competition stage. Here is how to calculate it, including the all-out and chase adjustments.
Batting together
Separate the stand from each batter’s full score
A partnership is the runs added while two batters were together. It is not the sum of their innings totals. Here is the arithmetic, the fall-of-wickets shortcut and how extras fit in.
Scorebook notation
Add spells in balls, then write the overs again
The dot in an overs figure separates complete overs from balls. This guide shows how to convert, add and subtract overs correctly so rates and totals come out right.
Batting
Batting average explained: why not-outs change the number
A batting average divides runs by the number of times a batter was dismissed. This guide shows why not-outs matter, how to read average with strike rate and which common mistakes to avoid.
Bowling
Bowling average, strike rate and economy: three numbers, one relationship
Bowlers are judged on average, strike rate and economy. They look like three separate statistics, but they are linked by one equation. This guide shows how to calculate each and how to use them together.
T20 cricket
Powerplay, middle overs and death overs: how to read T20 phase run rates
A single run rate hides the shape of a T20 innings. This guide splits a fictional innings into its three phases, shows how to calculate each rate and explains why the phases differ.
Scorecards
How to read a cricket scorecard line by line
A scorecard packs a whole innings into a few lines of shorthand. This guide decodes each column and shows how to check that the batting, extras and bowling figures all agree.
Rules and scoring
Wides, no-balls, byes and leg-byes: who is charged for what
Extras add runs to the team total, but they are not all charged the same way. This guide shows how each type affects the batter, the bowler and the number of legal balls in an over.
Chasing and projecting
Projected score: how to estimate an innings total and why it needs a range
Scoreboards often show a projected total. It is a useful reference point but not a forecast. This guide shows how to calculate it, how to build a realistic range and what the figure leaves out.
Checklists
Ten common cricket calculation mistakes and how to avoid them
Most cricket calculation errors come from the inputs, not the formulas. These ten mistakes account for most wrong answers, and each one has a simple fix.
Rules and scoring
T20, ODI and Test: what changes when you calculate cricket numbers
The formulas are the same in every format, but the context changes what the numbers mean. This guide compares T20, one-day and Test cricket and shows which calculations matter most in each.
Batting and bowling
Dot balls and boundaries: the two numbers a strike rate hides
A strike rate says how fast a batter scored, not how. Dot-ball percentage, boundary share and balls per boundary show the shape of an innings. Here are the formulas, worked examples and a calculator to check your own figures.
Results and margins
Margin of victory: runs, wickets and balls to spare
A result such as "won by 6 wickets" hides two numbers: the wickets in hand and the balls to spare. Here are the formulas behind every margin, how they feed net run rate, and a calculator to check your own match.
Guide index
- Read a strike rate alongside the innings
- A rain target is about resources, not an overs ratio
- Check the runs column before judging a bowling spell
- A quiet over changes the asking rate: work it through
- Why averaging match run rates can mislead
- Separate the stand from each batter’s full score
- Add spells in balls, then write the overs again
- Batting average explained: why not-outs change the number
- Bowling average, strike rate and economy: three numbers, one relationship
- Powerplay, middle overs and death overs: how to read T20 phase run rates
- How to read a cricket scorecard line by line
- Wides, no-balls, byes and leg-byes: who is charged for what
- Projected score: how to estimate an innings total and why it needs a range
- Ten common cricket calculation mistakes and how to avoid them
- T20, ODI and Test: what changes when you calculate cricket numbers
- Dot balls and boundaries: the two numbers a strike rate hides
- Margin of victory: runs, wickets and balls to spare
Ready to calculate?
Every guide links to a matching calculator. You can also browse all ten tools in one place.
Browse calculators