Work out a cricket batter's strike rate — how quickly they score — with the formula strike rate = (runs scored ÷ balls faced) × 100. Enter any two of runs scored, balls faced, and strike rate, leave the third blank, and the calculator solves for it.
The batting strike rate calculator tells you how quickly a cricket batter scores runs relative to the number of deliveries they face. It uses the standard formula strike rate = (runs scored ÷ balls faced) × 100, and because it works in every direction, you can just as easily find the runs or the balls when you know the strike rate. Enter any two values, leave the third blank, and get an instant, accurate answer. Whether you are analyzing a professional innings, tracking your own performance, or settling a debate about who is the more aggressive batter, this tool does the arithmetic for you.
Strike rate is one of the most important statistics in modern cricket, especially in the shorter formats where scoring quickly can matter as much as scoring heavily. This page explains what strike rate is, the formula behind the calculator, worked examples you can reproduce, how it differs from batting average, what counts as a "good" strike rate in each format, and answers to the questions fans and players ask most.
In cricket, a batter's strike rate measures the average number of runs they score per 100 balls faced. It is a measure of scoring speed or aggression, not of total output. A batter with a strike rate of 100 scores, on average, one run for every ball they face; a strike rate of 150 means 150 runs per 100 balls, or 1.5 runs per delivery; a strike rate of 50 means the batter scores at half a run per ball. The higher the strike rate, the faster the batter is scoring.
Strike rate matters because cricket is played with a limited number of deliveries, particularly in limited-overs formats. A batter who scores 50 runs from 30 balls has contributed far more to the team's scoring rate than one who scores the same 50 from 90 balls, even though both reached the same total. Strike rate captures that difference, which is why it sits alongside the batting average as one of the two headline numbers used to judge a batter.
The formula for batting strike rate is simple:
strike rate = (runs scored ÷ balls faced) × 100
You divide the number of runs a batter has scored by the number of balls they have faced, then multiply by 100 to express it per hundred deliveries. Multiplying by 100 is just a convention that turns the runs-per-ball figure into a more readable number — instead of saying a batter scores 0.85 runs per ball, we say their strike rate is 85.
Because the relationship is a simple ratio, it can be rearranged to find any of the three quantities:
The calculator handles all three, so you can leave whichever value you do not know blank.
Consider one of the most famous Test innings ever played: Len Hutton's 364 for England against Australia in 1938. He scored 364 runs from 847 balls. His strike rate was:
strike rate = (364 ÷ 847) × 100 = 42.975
So Hutton scored at a strike rate of about 42.98 — sedate by modern standards, but entirely typical for a marathon Test innings built for endurance rather than speed. These are the calculator's default values, so you can press Calculate to see the result and then enter your own numbers.
Strike rate and batting average are the two pillars of batting statistics, and they answer completely different questions. The batting average measures how many runs a batter typically scores before getting out — it is runs divided by the number of times dismissed. Strike rate measures how quickly a batter scores — runs per 100 balls. A batter can have a high average but a low strike rate (a patient accumulator who bats for a long time), or a lower average but a very high strike rate (an aggressive hitter who scores fast but gets out often).
Neither number alone tells the whole story. In Test cricket, a high average is prized because occupying the crease and building large totals is paramount. In Twenty20 cricket, strike rate is often more valuable because the team has only 120 balls and needs runs quickly. The best modern batters combine both — a strong average with a healthy strike rate — which is why analysts always look at the two figures together.
A "good" strike rate depends heavily on the format of the game, because each format rewards a different balance of speed and safety:
Context matters too: a strike rate of 70 might be excellent for an opener rebuilding after early wickets, but poor for a finisher at the death. Always read strike rate against the match situation and the batter's role.
The rise of Twenty20 cricket has pushed strike rate to the front of the sport's analytics. In a format where a team faces only 120 deliveries, every ball is precious, and a batter who scores slowly can cost the team more than one who gets out quickly but scores fast. Franchise leagues, selectors, and commentators now scrutinize strike rates closely, and players are increasingly judged not just on how many runs they make but on how fast they make them. Even in the longer formats, scoring rates have crept up as batters bring T20 skills to Test and ODI cricket. Understanding strike rate — and being able to calculate it instantly — is therefore essential for anyone who wants to follow, analyze, or play the modern game.
It is worth noting that cricket also has a bowling strike rate, and it means something entirely different. A bowler's strike rate is the average number of balls they bowl per wicket taken (balls bowled ÷ wickets), so for bowlers a lower number is better. This calculator is for batting strike rate, where a higher number is better. Do not confuse the two: batting strike rate is about scoring runs quickly, while bowling strike rate is about taking wickets frequently. They share a name but are computed and interpreted in opposite directions.
You do not need to be a professional to benefit from tracking strike rate. Club and amateur cricketers can use it to understand their own game: are you an anchor who holds an innings together, or an aggressor who accelerates the scoring? Recording your runs and balls faced across innings and calculating your strike rate reveals patterns you might not notice otherwise — for example, that you score freely against spin but slow down against pace, or that your strike rate dips when you first come in and rises as you settle. Coaches use strike rate to assign batting roles and to set targets, and players use it to work on specific parts of their game, such as rotating the strike or finding boundaries more often.
Seeing the formula applied to different innings makes it easy to interpret:
These illustrate how the same statistic describes wildly different styles of batting, from block-and-defend to all-out attack.
Strike rate is powerful but not perfect. On its own it ignores how many runs a batter scored and how often they got out, so a player who blazes 15 off 5 balls has a huge strike rate but a small contribution. It also does not account for match conditions — a slow pitch, a strong bowling attack, or a difficult chase can all suppress strike rates without reflecting poorly on the batter. And it treats all runs equally, whether scored when the team was cruising or when quick runs were desperately needed. For a full picture, strike rate should always be read alongside the batting average, the number of runs, the situation, and the format. Used that way, it is one of the most revealing numbers in cricket.
Behind a single strike-rate figure lies every delivery a batter faced. Each dot ball — a delivery from which no run is scored — drags the strike rate down, while every boundary lifts it sharply. A single four adds four runs for one ball faced, which on its own is a strike rate of 400 for that delivery; a six is worth 600. This is why boundary-hitting is the fastest route to a high strike rate, and why finishers who clear the ropes regularly post the biggest numbers. Rotating the strike with quick singles keeps the strike rate ticking over between boundaries, whereas a run of dot balls can quietly sink it. When you calculate strike rate over a full innings, you are really averaging out all of these individual outcomes: the boundaries, the singles, and the dot balls combine into one number that summarizes the whole knock. Understanding this makes the figure far more meaningful than treating it as an abstract statistic — it is the fingerprint of how an innings was actually constructed, ball by ball.
The calculator works equally well for a single innings and for an entire career. For one innings, you simply divide the runs by the balls faced in that knock. For a career strike rate, you add up all the runs a batter has scored across every innings and divide by the total balls they have faced, then multiply by 100. A career figure smooths out the peaks and troughs — the blazing cameos and the slow grinds — into a single representative number, which is why it is the figure most often quoted in player profiles and record books. A single-innings strike rate, by contrast, captures the character of one specific performance. Both are calculated with exactly the same formula; only the scope of the numbers you enter changes. When comparing players, always make sure you are comparing like with like: a career T20 strike rate against a career T20 strike rate, not a single explosive innings against another batter's lifetime average, which would be misleading.
Strike rate = (runs scored ÷ balls faced) × 100. It gives the average number of runs a batter scores per 100 deliveries faced.
A strike rate of 100 means the batter scores, on average, exactly one run for every ball they face — 100 runs per 100 balls.
Yes, for batting. A higher strike rate means faster scoring. But it should be balanced against the batting average and the match situation, as scoring too quickly can lead to getting out.
In T20, a strike rate of 130–150 is considered good, and the most explosive batters exceed 180 or 200. Because a T20 innings has only 120 balls, scoring speed is crucial.
Batting strike rate is runs per 100 balls (higher is better). Bowling strike rate is balls per wicket (lower is better). They share a name but measure opposite things.
Yes. The calculator is bidirectional. Enter the strike rate and either the runs or the balls, leave the unknown blank, and it will solve for it using runs = (SR/100) × balls or balls = runs / (SR/100).
This Batting Strike Rate Calculator is provided for general informational and educational purposes. It computes the standard cricket batting strike rate from runs scored and balls faced. Statistics should be interpreted alongside other measures such as batting average, match format, and conditions for a complete picture of performance.