Cricket Run Rate Calculator
Compute the current and required run rates from runs, overs faced, the target and the innings length.
Overs are written x.y where y counts balls from 0 to 5, so 12.3 means twelve overs and three balls. The current rate is runs divided by overs, and the required rate uses the runs still needed plus one, divided by the overs left.
A ball count above 5, an innings already complete, or a target of 0 is refused with the reason stated; nothing is rounded into a plausible answer. The page does not apply Duckworth-Lewis or any rain rule, and it does not know the fall of wickets.
The four fields are the whole input, so the same scoreline prints the same two rates after a reload.
Run rate is runs scored divided by overs faced, and the page works in balls underneath: balls faced = whole overs × 6 + the ball digit, current rate = runs ÷ (balls ÷ 6), and the required rate = (target − runs + 1) ÷ (balls left ÷ 6). The plus one is the winning margin, not a rounding artefact.
Overs must be written the way cricket writes them, x.y with y from 0 to 5, so 12.3 is twelve overs and three balls. Anything else, and an innings already finished, is refused.
How to use it
Enter runs scored, overs faced as x.y, the target and the overs allotted to the innings, then press Run. You get the current rate, the required rate and the ball counts behind both.
The arithmetic
Balls faced drives both divisions, so 12.3 is 75 balls and not 12.3 overs. If no balls are left the required rate has no denominator, and the page says the innings is over rather than printing an infinity.
What to Expect
Best for
- Working out a chase's required rate from the score, the overs faced and the innings length.
What this tool keeps
- Both rates, the balls faced and the balls left, so a scoreboard disagreement can be traced.
Sample input
87 runs, 12.3 overs, target 160, 20 overs allotted.
Sample output
Current run rate = 6.96 per over Required run rate = 9.87 per over to reach 160 in 20 overs Balls faced 75, balls left 45
Frequently asked questions
Why is 12.3 not 12.3 overs?
Cricket writes overs as whole overs and balls, so the digit after the point counts balls from 0 to 5. The page converts to 75 balls, and a figure like 12.6 is refused as not an over.
Why does the required rate add one run?
A side needs to pass the target, not equal it, so the runs still needed are target minus runs plus one. Without that run the required rate would describe a tie.
Can I use it mid-over?
Yes, as long as the ball count is written as x.y. The rate is then over the balls actually faced, which is why the ball count is printed beneath it.
Is the match state saved?
No. The four figures live only in the fields of the open tab and nothing is stored between visits.
Build custom tools for your store
Join the SDK program to create useful ecommerce utilities for your store.