Batting Strike Rate Calculator
Enter a batter's runs and recorded balls faced. For example, 42 from 28 balls gives a strike rate of 150.00: the same pace as 150 runs per 100 balls.
Open Calculator
10 Free Cricket Calculators
Which cricket number do you need?
Choose a tool for batting, bowling or the team score. Each page includes the input fields, the formula and an explanation of the result.
If two figures on your scorecard seem to disagree, start with the one-over scorebook check. It shows why runs added to the team total are not always runs charged to the bowler.
Bowling Economy Rate Calculator
Enter the runs charged to the bowler and their overs bowled. A spell of 27 runs from 3.4 overs has an economy of 7.36, because 3.4 means 22 balls.
Open CalculatorRun Rate Calculator
Check a team's scoring pace from runs and overs. For a chase, use runs still needed and overs remaining in the same fields to work out the required rate.
Open CalculatorPartnership Calculator
Add each batter's runs made during the stand, plus its extras. Use contributions since the partnership began, rather than each batter's full innings score.
Open CalculatorDLS Target Estimator
Explore a simplified rain-target estimate using a resource table. This is a learning tool; use the match officials' target for an actual rain-affected game.
Open CalculatorOvers to Balls Converter
Convert between overs and balls before doing the sums. An entry of 16.4 means 100 legal deliveries, not 16.4 decimal overs. These tools use six-ball overs.
Open CalculatorBatting Average Calculator
Divide total runs by dismissals, not innings. 162 runs in 6 innings with 2 not-outs is an average of 40.50.
Open CalculatorBowling Average & Strike Rate Calculator
Get runs per wicket, balls per wicket and economy together. A spell of 4-0-28-2 has an average of 14.00 and a strike rate of 12.0.
Open CalculatorRequired Run Rate Calculator
Enter the target, score and overs bowled. Needing 72 from 42 balls is a required rate of 10.29, with a next-over what-if table.
Open CalculatorNet Run Rate Calculator
Add matches, tick all-out innings for the full-quota rule and get the aggregate NRR across a stage of a tournament.
Open CalculatorBefore you press calculate
Most cricket calculation mistakes start with the input. A team total, a batter's score and a bowler's runs conceded describe different things. Take a moment to choose the right scorecard entry.
Read the dot as “overs and balls”
At 8.3 overs, 51 legal balls have been bowled: eight lots of six, then three more. That is 8.5 decimal overs. Typing 8.3 into an ordinary division gives a different answer. In these tools, enter the scorecard notation directly.
Use the recorded balls faced
For strike rate, copy the batter's balls-faced figure. Do not work it out from the team's overs: the other batter has faced some of those deliveries. The calculator uses the total you enter; it does not reconstruct the ball-by-ball scoring.
Keep team runs and bowler runs separate
Run rate uses the team total, including extras. Economy uses the runs charged to that bowler. Wides and no-ball penalties count against the bowler; byes and leg-byes do not. Copying the bowling analysis is the simplest way to avoid mixing them up.
Check the target to win
If the opposition finishes on 168 in an uninterrupted match, the winning target is 169. Subtract your current score from 169. After rain, use the revised target and allocation announced by the officials.
| Scorecard entry | Legal balls | Decimal overs for division |
|---|---|---|
| 3.4 | 22 | 3 + 4 ÷ 6 = 3.666… |
| 8.3 | 51 | 8 + 3 ÷ 6 = 8.5 |
| 16.4 | 100 | 16 + 4 ÷ 6 = 16.666… |
The digit after the dot runs from 0 to 5. After 8.5 comes 9.0, so enter 9.0 rather than 8.6. Keep the full ball count during a calculation and round the final rate. See the overs-to-balls converter for other values.
One over, three different totals: check the scorebook
The scoreboard says 13 came from the over, but the bowler's figures went up by only 11. Before changing either number, check the extras. Both entries can be right.
In this fictional innings, the team starts at 84/2 after 10 overs. The next over includes a wide, two leg-byes and a no-ball hit for two. No wicket falls. Read each row as a separate delivery; only six of the eight deliveries advance the over.
| Delivery | What happened | Batter runs | Extras | Bowler charged | Score after delivery |
|---|---|---|---|---|---|
| 1 | Single | 1 | 0 | 1 | 85/2 (10.1) |
| 2 | Wide; no running | 0 | 1 wide | 1 | 86/2 (10.1) |
| 3 | Dot ball | 0 | 0 | 0 | 86/2 (10.2) |
| 4 | Four off the bat | 4 | 0 | 4 | 90/2 (10.3) |
| 5 | Two leg-byes | 0 | 2 leg-byes | 0 | 92/2 (10.4) |
| 6 | No-ball, two off the bat | 2 | 1 no-ball | 3 | 95/2 (10.4) |
| 7 | Single | 1 | 0 | 1 | 96/2 (10.5) |
| 8 | Single | 1 | 0 | 1 | 97/2 (11.0) |
| Over totals | 9 | 4 | 11 | 13 team runs added | |
Check the team total
Nine runs off the bat plus four extras equals 13. Add that to 84 and the team reaches 97. Its innings run rate is now 97 ÷ 11 = 8.82. The 13 scored in this over is a separate figure from the average across the innings.
Check the bowling analysis
The bowler concedes nine off the bat, one wide and one no-ball penalty: 11. If their previous figures were 0/20 from two overs, they are now 0/31 from three, an economy of 10.33. The two leg-byes stay outside those figures.
To check this example, enter 97 and 11.0 in the run-rate tool, or 31 and 3.0 in the economy tool. “Batter runs” in the table combines both players' contributions; it is not an individual balls-faced record. The scoring rules behind the example are covered by MCC Laws 17, 21, 22 and 23.
Work through a scorecard with us
These are made-up match situations, so you can check every step without needing a live score. Try the same inputs in the linked tools.
A quick 42: what does the strike rate mean?
A batter makes 42 from 28 balls. Divide 42 by 28 and multiply by 100: 150.00. They scored at 1.5 runs per ball over that innings.
Another batter makes 12 from eight balls and has the same rate. The pace matches, but the first innings supplied 30 more runs. Read strike rate alongside runs scored and the match situation, especially when comparing a short cameo with a longer innings.
Try 42 runs from 28 ballsAn unfinished spell: 27 runs in 3.4 overs
The bowler has delivered 22 legal balls. Economy is 27 × 6 ÷ 22 = 7.36 runs per over, rounded to two decimal places. Dividing by 3.4 would give 7.94, which overstates the rate.
Suppose the team also picked up four leg-byes during that spell. Those runs affect the team total, but the bowler's conceded-runs entry remains 27. The tool relies on you entering that bowling figure.
Check the economy for 27 in 3.4The chase: 112/4 after 14.2 overs
In a 20-over game with a target of 169, the batting side needs 57 from 34 balls. It has used 86 of its 120 balls. Its current rate is 112 × 6 ÷ 86 = 7.81; its required rate is 57 × 6 ÷ 34 = 10.06.
To check the required rate in the run-rate tool, enter 57 under “Total Runs” and 5.4 under “Overs Faced”. Here those fields represent runs needed and overs left. After a dot ball, the requirement rises to 57 from 33, or 10.36 per over.
Work out the rate for this chaseA stand that begins at 48/2
The next wicket falls at 109/3, so the partnership added 61 runs. During the stand, one batter scored 34, the other scored 22, and there were five extras: 34 + 22 + 5 = 61.
If the first batter already had 18 when the stand began, their score is now 52. Enter 34 for this partnership, not 52. The tool's batter shares use the 56 runs off the bat: 60.7% and 39.3%. Extras make up a separate 8.2% of the full stand.
Check a 34 + 22 + 5 partnershipWhat would a six-, ten- or fourteen-run over change?
Return to the chase above: 57 needed from 34 balls. Compare three possible outcomes over the next six legal deliveries, assuming the target stays the same. Each leaves 28 balls, written as 4.4 overs.
| Runs added | Runs still needed | New required rate |
|---|---|---|
| 6 | 51 from 28 balls | 51 × 6 ÷ 28 = 10.93 |
| 10 | 47 from 28 balls | 47 × 6 ÷ 28 = 10.07 |
| 14 | 43 from 28 balls | 43 × 6 ÷ 28 = 9.21 |
Ten runs sounds like a productive over, but here it barely keeps pace. Fourteen brings the requirement below ten. None of these rates tells you how likely the chase is to succeed: losing two wickets while scoring fourteen could still leave the batting side in a worse position.
Try another outcome: subtract the runs scored from 57, then multiply by 6 and divide by 28. This is a planning exercise, not a win-probability model.
Net run rate: add the totals before dividing
You can run the numbers yourself in the net run rate calculator, or read the full net run rate guide.
Current run rate describes an innings. Net run rate compares a team's scoring and conceding rates over the matches counted in a competition stage. It is not the average of the individual match NRR figures. CricketCals explains the calculation here; it does not have a separate tournament NRR calculator.
NRR = (total runs scored × 6 ÷ balls faced for NRR) − (total runs conceded × 6 ÷ balls bowled for NRR)
A two-match example
In two uninterrupted 20-over matches, your side scores 160/6 from 20 overs, then 121/4 from 15 overs. The opponents score 140/8 and 120/9, each from 20 overs. Neither side is all out.
- Scoring rate: (160 + 121) ÷ (20 + 15) = 281 ÷ 35 = 8.028571…
- Conceding rate: (140 + 120) ÷ (20 + 20) = 260 ÷ 40 = 6.5.
- Subtract, then round: 8.028571… − 6.5 = +1.529.
Averaging the two match differences would give (1.00 + 2.066666…) ÷ 2 = 1.533333…, a different answer. The innings used unequal numbers of balls, so the combined totals are needed.
When the scorecard needs an adjustment
For NRR, an all-out innings uses the full allocated overs. For example, 120 all out in 17 overs of a 20-over innings counts as 120 from 20. An ordinary innings run-rate calculation still uses the 17 overs actually faced. A successful chase uses the balls taken to finish it.
No-results, rain-adjusted results and stage boundaries need the competition's rules. The ICC Men's T20 World Cup 2026 conditions, clause 16.10.7, exclude Super Overs and specify adjustments for DLS results. Check your own league's conditions before trying to reproduce its table.
Rain targets need more than a run-rate calculation
Cutting an innings from 20 overs to 15 does not simply mean taking three quarters of the original target. Overs and wickets together affect a side's scoring opportunity. That is the idea behind resource-based rain adjustments.
The DLS target estimator on this site uses a simplified resource-table calculation. It does not reproduce the official DLS software or account for every interruption scenario. Treat its output as an illustration, not a match decision.
Once officials announce a revised target, you can still calculate the required rate normally. For instance, a revised target of 131 with 96 already scored and 24 balls left means 35 more runs at 8.75 per over. The ICC's DLS resources explain the official method.
When your result does not match the scorecard
Keep the original scorecard beside you and change one input at a time. These checks help distinguish an entry mistake from a difference in what the figures measure.
You entered 16.67 and got an error
The overs field expects cricket notation. A hundred balls is 16.4 overs; 16.67 is a rounded decimal conversion. Enter 16.4. If you only know the ball count, divide by six: the whole-number quotient is the overs and the remainder is the digit after the dot.
The partnership seems too large
Check whether you used an innings total instead of runs made during the stand. Also check the time window for extras: innings extras include runs from earlier partnerships. For a stand with no retirement or other unusual interruption, compare your sum with the change in the team score between its start and end.
The displayed rate has different decimal places
Check rounding before assuming the formula is wrong. For 60 runs from seven overs, the full rate is 8.571428… . Rounding to two decimal places gives 8.57, while rounding to one gives 8.6. Keep the original runs and balls when combining figures; do not calculate from an already rounded rate.
The projected total looks like a prediction
A team on 80 after ten overs would reach 160 in twenty if it kept scoring at exactly the same pace. That calculation makes no allowance for wickets, a new bowler or changing conditions. Use a projection as a reference point, and recalculate it as the innings changes.
These over-based tools assume six-ball overs. Do not enter a historical eight-ball over or a five-ball set as though it were a six-ball over. Check the competition's counting convention first. If a result still looks wrong, send the exact inputs and expected answer.
Questions that come up at the scorebook
A few checks to make when a result looks unexpected.
Why does 4.5 overs mean 29 balls, not 27?
The dot separates complete overs from extra balls. Four complete overs contain 24 balls; add five to get 29. For division, that is 29 ÷ 6 overs. The next legal delivery completes the fifth over, written as 5.0.
Do wides and no-balls count towards an over?
Neither counts as one of the six legal deliveries. They can add runs without advancing the over count. For a batter’s strike rate, use the recorded balls-faced figure from the scorecard rather than trying to derive it from the team’s overs.
Can I calculate a rate before a ball has been faced?
A rate needs a non-zero denominator. Zero runs from five balls gives a strike rate of zero, but zero balls faced leaves strike rate undefined. The same issue applies to economy or current run rate before any legal ball has been bowled.
How do I combine several innings or bowling spells?
Add the runs and the relevant balls first, then calculate the rate. For example, 10 from 10 balls and 30 from 15 balls combine to 40 from 25, a strike rate of 160. Averaging the separate rates of 100 and 200 would incorrectly give 150.
Why can the team run rate differ from a bowler’s economy?
The team total includes all extras, while a bowler’s conceded runs exclude byes and leg-byes. For example, a single completed over containing six runs charged to the bowler and four leg-byes adds ten to the team score: team run rate 10.00, bowler economy 6.00.
Can these tools decide an official rain target or league position?
No. Use the target issued by the match officials and the standings published by the competition. The rain-target tool is a simplified estimate, and the NRR guide cannot account for every competition-specific adjustment. The other tools help you check arithmetic from the figures you enter.
About this guide and its sources
Published by CricketCals for readers checking their own scorecards. The examples use fictional scores, not reports of actual matches. You can reproduce the results from the figures shown without supplying personal information.
The method in this guide is to count balls first, separate team and player runs, then divide and round the final result. Ordinary rates here use two decimal places; the tournament NRR example uses three. Links below distinguish scoring laws from competition rules, while the rain-target section explains where this site's estimate stops being suitable.
- MCC's Laws of Cricket: consult Laws 17, 21, 22 and 23 for overs, no-balls, wides, byes and leg-byes.
- ICC playing conditions: match and competition rules can add to or modify the Laws. Use the document for your event.
Found a mismatch? Send a correction with the tool name, the values you entered and the result you expected. For a scoring-rule question, include the competition and the relevant rule so the example can be checked.
No account is needed to use the tools. This site includes third-party advertising services; see the privacy policy for information about data and cookies.