Cricket Scoring

Cricket Projected Score Calculator (Run Rate)

Carry the current run rate — or an assumed run rate — forward across the remaining overs to project an innings total. Enter overs as overs.balls (e.g. 20.3) and this tool converts them to decimal overs the ICC way. This is arithmetic on a rate, not a forecast of the final score.

Run-rate conventions: ICC playing conditions • Checked 24 Aug 2026

Innings Position

Sample Scenarios:

1. Current Score & Overs Bowled

2. Assumed Run Rate for the Rest of the Innings

Overs notation: the digit after the dot is balls (0–5). So 20.3 means 20 overs and 3 balls = 20.5 decimal overs. Entries like 20.6 are not valid and are rejected.
Projected Innings Total If the rate continues
Projected Total (at current rate)
360
If scoring continues at 6.00 rpo over the remaining 20.0 overs
Current Run Rate
6.00 rpo
Overs Remaining
20.0
Projected (current rate)
360
Projected (assumed rate)
360
Not a prediction of the final score. It projects the current or an assumed run rate forward — actual scoring speeds up and slows down with wickets, powerplays and the batting order.
✓ Copied to clipboard!

How the projected score is calculated

A projected score is simple arithmetic: work out a run rate, then multiply it by the overs still to be bowled and add it to the runs already on the board. The only care needed is converting cricket overs.balls notation into true decimal overs before dividing.

Overs to decimal: overs_decimal = completed_overs + (balls / 6) e.g. 20.3 overs = 20 + (3 / 6) = 20.5 decimal overs Current run rate: RR = current_runs / overs_decimal Overs remaining: overs_remaining = total_overs − overs_bowled (in decimal overs) Projected (current rate): current_runs + RR × overs_remaining Projected (assumed rate): current_runs + assumed_RR × overs_remaining

Why this is not a forecast

Arithmetic on an assumed rate

“This is not a prediction of the final score. It projects the current or an assumed run rate forward — actual scoring speeds up and slows down with wickets, powerplays and the batting order.”

Every output is phrased as “if scoring continues at this rate”. A team on 80/2 after 10 overs is not going to score at exactly the same pace for the next 10 — but the projection tells you what the total would be if it did, which is a useful reference point.

Accuracy notes and limits

No DLS / rain-adjusted targets
  • Wickets are display-only: this tool does not adjust the rate for how many wickets are in hand. A projection at 8/2 and at 8/8 are identical arithmetically; interpret them differently.
  • Duckworth–Lewis–Stern (DLS): this tool does not compute DLS or any rain-adjusted par score or revised target. Those calculations are proprietary and are not implemented here — a straight run-rate projection is a different thing entirely.

Worked example: 80/2 after 10 overs of a T20

  1. Current runs: 80 • Overs bowled: 10.0 = 10.0 decimal overs
  2. Total overs: 20 • Overs remaining: 20 − 10.0 = 10.0
  3. Current run rate: 80 / 10.0 = 8.00 rpo
  4. Projected at current rate: 80 + 8.00 × 10.0 = 160
  5. Projected at an assumed 10.0 rpo: 80 + 10.0 × 10.0 = 180

Projected T20 total from 80/2 after 10 overs

Ten overs still to bowl. The table below shows the projected 20-over total at several assumed run rates for the remaining overs — each is simply 80 + rate × 10.

Assumed rate (remaining 10 overs) Runs added Projected total
7 runs/over 70 150
8 runs/over (current rate) 80 160
9 runs/over 90 170
10 runs/over 100 180
12 runs/over 120 200

Related sports calculators

Cricket

Net Run Rate Calculator

Tournament NRR, run rate and required run rate under ICC playing conditions.

Running

Running Pace Calculator

Calculate paces and finish times across metric and imperial distances.

Frequently asked questions

Why does 20.3 overs become 20.5 in the maths?

Cricket overs have 6 balls, so the digit after the dot is a count of balls, not tenths. 3 balls is 3/6 = 0.5 of an over, so 20.3 overs is 20.5 decimal overs. Entries like 20.6 or higher are invalid because an over has only 6 balls (0–5 as the ball digit).

Does the projection account for wickets in hand?

No. Wickets are shown for context only. The projection is pure run-rate arithmetic, so a side eight wickets down projects the same total as one two wickets down at the same rate. In reality, wickets in hand are one of the biggest factors in whether a rate can be sustained.

Can this give me a rain-adjusted or DLS target?

No. This tool only projects a run rate forward. It does not compute Duckworth–Lewis–Stern par scores or revised targets, which use a proprietary resource model that is not implemented here.