Batting Strike Rate Calculator
Calculate scoring velocity — runs scored per 100 legal balls faced. Isolates scoring tempo from batting average with exact ball-counting rules for extras.
Open CalculatorChoose a calculator below to get instant results. Each tool has its own dedicated page with detailed explanations, formulas, and FAQs.
Calculate scoring velocity — runs scored per 100 legal balls faced. Isolates scoring tempo from batting average with exact ball-counting rules for extras.
Open CalculatorFind the average runs conceded per 6-ball over. Correctly converts cricket dot notation into decimal overs before division to ensure mathematical precision.
Open CalculatorCalculate a team's Current Run Rate (CRR) or the Required Run Rate (RRR) needed to chase a target, with ball-by-ball required scoring tempo.
Open CalculatorCalculate the total runs of a partnership while separating off-the-bat contributions from bowling extras to see each batter's true scoring share.
Open CalculatorEstimate Duckworth-Lewis-Stern revised targets and par scores for rain-interrupted limited-overs matches based on overs remaining and wickets in hand.
Open CalculatorConvert cricket overs notation (e.g. 16.4) into total legal deliveries (100 balls), decimal overs (16.667), and remaining balls in the over.
Open CalculatorStandard math tools cannot process cricket's base-6 over notation or specific rules for extras, dismissals, and match targets.
Handles cricket dot notation accurately (8.3 means 8 overs and 3 balls — 8.5 decimal overs, not 8.3) preventing division errors.
Correctly separates legal deliveries from re-bowled extras like wides and no-balls when computing balls faced and strike rates.
Assigns bowler extras (wides, no-balls) to economy rates while separating fielding extras (byes, leg-byes) that belong only to the team total.
Computes required run rates dynamically, showing how dot balls escalate required scoring rates and how boundaries bring targets within reach.
Evaluates weather-shortened matches using overs remaining and wickets in hand rather than flawed linear run-rate scaling.
Every calculation runs entirely in your browser using client-side JavaScript. No account is required and no match data is stored or transmitted.
Benchmark strike rates, economy rates, and run rates across T20, ODI, and Test cricket — so you know what results mean.
IPL · Big Bash · The Hundred · PSL
World Cup · Champions Trophy · Bilateral Series
The Ashes · World Test Championship
Net Run Rate is the tiebreaker used in tournament group stages when teams finish level on points, such as in the ICC World Cup or IPL. In plain terms, it measures how fast your team scored runs across the tournament compared to how fast you gave them away.
Net Run Rate = (Total Runs Scored ÷ Total Overs Faced) − (Total Runs Conceded ÷ Total Overs Bowled)
One rule that often surprises people is what happens when a team gets bowled out. If a team loses all 10 wickets in, say, 41 overs of a 50-over match, their run rate is still calculated using the full 50 overs, not the 41 overs they actually lasted. This ensures a team is not rewarded with a higher run rate for getting bowled out quickly. However, when chasing, if a team reaches the target in 35 overs, only the 35 overs actually batted are counted.
Here is how you calculate NRR across two 50-over matches:
Match 1: Your team bats first and scores 265/7 in 50 overs. You then restrict the opponent to 235/9 in 50 overs.
Match 2: Your team gets bowled out for 175 in 41.2 overs. Because you were all out, the full 50 overs count. The opponent chases it down, scoring 176/4 in 35.4 overs (35 overs and 4 balls = 35.67 decimal overs).
1. Batting Rate (runs scored):
Total runs = 265 + 175 = 440 runs
Total overs = 50 + 50 = 100 overs
Batting run rate = 440 ÷ 100 = 4.400 runs per over
2. Bowling Rate (runs conceded):
Total runs = 235 + 176 = 411 runs
Total overs = 50 + 35.67 = 85.67 overs
Bowling economy = 411 ÷ 85.67 = 4.798 runs per over
3. Net Run Rate:
4.400 − 4.798 = −0.398
Because the team conceded runs faster than they scored them across both matches, their tournament Net Run Rate is −0.398.
Cricket's specialized scoring rules frequently cause calculation errors when treated as standard arithmetic.
In a chase, subtracting 32.2 overs from 50.0 overs on a calculator gives 17.8. In cricket, 50 overs minus 32 overs and 2 balls leaves 17 overs and 4 balls (17.4 overs, or 104 balls remaining).
Byes and leg-byes result from fielding or keeping misses, not bowling error. Charging them against a bowler's runs conceded falsely inflates their economy rate.
Wides must be re-bowled and are credited to team extras. Including them in a batter's personal balls-faced count deflates their strike rate.
When a team is dismissed in fewer overs, dividing by the overs actually survived instead of the scheduled full allocation (50 or 20) yields an incorrect Net Run Rate.
Quick answers about our free online cricket calculator tools.
The dot in cricket scorebooks is a delimiter separating two distinct units: completed 6-ball overs on the left, and remaining legal deliveries on the right. Because an over contains 6 balls, the number following the dot can only be 0, 1, 2, 3, 4, or 5. It functions like hours and minutes rather than a base-10 decimal.
Wides and no-balls are illegal deliveries and must be re-bowled. They add penalty runs to the batting team's extras and to the bowler's runs conceded, but they do not count toward the 6 legal deliveries required to complete an over. A batter facing a wide or no-ball does not advance their personal balls-faced tally, but any runs struck off the bat from a no-ball are credited to the batter's score.
Both metrics use the exact same mathematical formula (Runs ÷ Decimal Overs), but they analyze the match from opposite perspectives. Run Rate measures batting scoring speed (runs scored per over by a team). Economy Rate measures bowling containment (runs conceded per over by an individual bowler or bowling unit).
A single-match Run Rate describes scoring speed during one innings (Runs ÷ Overs). Net Run Rate is a cumulative tournament tiebreaker that subtracts a team's overall conceding rate from its overall scoring rate across all completed group-stage matches.
When rain reduces the available overs during a chase, the target is adjusted using the Duckworth-Lewis-Stern (DLS) method. The required run rate must then be recalculated using the revised DLS target minus current runs scored, divided by the remaining overs allocated under the revised playing conditions.
No. Runs scored, runs conceded, wickets taken, and overs bowled in a Super Over or tiebreaker are recorded separately. ICC playing conditions state that Super Over figures never count toward a player's official career statistics or a team's tournament Net Run Rate.