CricPulse
Batting Milestone Calculator
Enter a batter's current score and balls faced to see exactly how many balls they need for a fifty, century, or custom target — and the strike rate required if the innings is running out.
Leave blank if you just want the balls needed at the current rate, with no innings deadline.
Scoring a Match? Let the App Keep Count
CricPulse scores ball by ball and keeps run rates and player stats up to date as you go. Free on iOS and Android.
What the Batting Milestone Calculator Does
Commentators and scorers say it constantly — “he needs 23 off the last 12 balls for a hundred” — but working it out mid-match means two quick calculations: how many balls the milestone takes at the batter’s current rate, and, if the innings is running out, the strike rate needed instead. This tool does both instantly for a fifty, a century, 150, 200, or any custom target you set.
The Two Numbers That Matter
Balls needed = (Runs needed ÷ Current strike rate) × 100
Required strike rate = (Runs needed ÷ Balls remaining) × 100
The first tells you where the milestone lands if nothing changes. The second only matters once the innings has a hard stop — it tells you how much the batter needs to accelerate (or whether they can afford to slow down) to get there before the last ball is bowled.
Worked Example
A batter is 45 off 30 balls — a strike rate of exactly 150 — chasing a fifty with 4 balls left in
the innings. They need 5 more runs. At their current rate, that takes
(5 ÷ 150) × 100 = 3.33, rounded up to 4 balls — exactly the balls
remaining, so the fifty is reachable without changing gear. The required strike rate from here is
(5 ÷ 4) × 100 = 125, comfortably below the 150 already being scored at.
Why It Matters Beyond the Number Itself
The gap between “balls needed at the current rate” and “balls remaining” is a genuine tactical signal, not trivia. When the two are close, a batter can play a normal ball and still get there — no need to take extra risk for one boundary. When the required rate jumps well past what they’ve shown all innings, that’s the moment a captain or the batter themselves has to decide whether the milestone is worth a real risk, or whether the team situation matters more than the personal landmark. For the format-specific side of that trade-off, see our T20 strategy guide and the Strike Rate Calculator for career and format benchmarks to judge whether a given rate is actually fast for the level being played.
Track Every Milestone Automatically with CricPulse
CricPulse already tracks every batter’s runs and balls faced ball by ball as part of live scoring — this calculator uses exactly that pair of numbers. Score your matches in the app to keep a permanent, accurate record of every fifty and century chase, without reaching for a calculator mid-over. Free on iOS and Android.
Frequently Asked Questions
How do you calculate the balls needed to reach a batting milestone? +
Divide the runs still needed by the current strike rate, then multiply by 100 — balls needed = (runs needed ÷ strike rate) × 100, rounded up. A batter on 45 off 30 balls (a strike rate of 150) needing 5 more for a fifty needs a further 4 balls at that same rate.
What strike rate do you need to reach a milestone before the innings ends? +
Divide the runs still needed by the balls remaining, then multiply by 100. Needing 20 off the last 10 balls of the innings requires a strike rate of 200 from that point on, regardless of the rate scored so far.
Why does the calculator say a milestone is "highly unlikely"? +
This tool flags a required strike rate above 300 as highly unlikely, since even the most explosive T20 batters rarely sustain that for more than a handful of balls. It is a guide, not a hard cutoff — a set batter against a weak death-overs attack can still occasionally clear it.
Does the current strike rate include dot balls? +
Yes. Strike rate is always runs scored per 100 balls faced, and every ball faced counts toward the balls figure whether it produced a run or not — that is exactly why a string of dot balls drags the projected balls-needed figure up even if the next ball is a boundary.
What if no balls have been faced yet? +
With zero balls faced there is no strike rate to project from, so the calculator shows the runs needed and the reference pace table (balls needed at 100, 125, 150 strike rate, and so on) instead of a single current-rate projection.
Can I use this for a bowler's over-limit or a team target instead of a batter's milestone? +
No — this tool is for an individual batter's own runs and balls faced. For a bowler's maximum overs, use the Bowler Over Limit Calculator; for a team chasing a target, use the Required Run Rate Calculator.
Score Your Next Match with the App
Ball-by-ball scoring, live stats, offline support, and instant sharing. Free to download on iOS and Android.