← All tools/Calculators/Sports/Cricket Projected Score Calculator

Cricket Projected Score Calculator

The projected final total in a limited-overs innings, from the current score and run rate.

runs
overs
overs

Projected final score

—

Runs scoredRuns still to come

How it works

Current run rate = current score / overs bowled
Projected total = current score + run rate × overs remaining

The projection starts from the “current score”, the runs on the board when you check, and the “overs bowled”, how many overs have actually been sent down. Dividing the first by the second gives the current run rate — runs per over so far. The “overs remaining” is the total overs in the innings minus the overs bowled, and the calculator adds the current rate multiplied by those remaining overs to the current score. That is the whole method: it assumes the team keeps scoring at exactly the rate it has scored at so far. It applies to any limited-overs innings, a 50-over ODI or a 20-over T20, at any point once a few overs have been bowled. It does not apply as a prediction — it ignores wickets in hand, the pitch, dew, and the way teams usually speed up in the last ten overs — so treat it as a checkpoint, not a forecast.

Worked example: 150 runs in 25 overs is a run rate of 6.00. With 25 overs left at the same rate, 150 more runs are expected, for a projected total of 300.

Worked example 2: India are 212 for 3 after 32 overs of a 50-over ODI. The current run rate is 212 ÷ 32 = 6.63 runs per over (6.625 before rounding). There are 50 − 32 = 18 overs left, so at the same rate India would add 6.625 × 18 = 119.25 runs. The projected total is 212 + 119.25 = 331.25, or about 331. With seven wickets still in hand, the real total is likely to be higher, because the batters to come can attack in the last overs — but 331 is what the scoring rate so far points to.

What the result means

A projected total is a mirror of the scoring rate so far, and its value is in the comparison, not the number alone. If India are projected at 331 after 32 overs, that tells you the innings is travelling at a good one-day tempo — anything above 300 is a strong total on most Indian pitches. But the same projection means very different things at 212 for 3 and at 212 for 8. With seven wickets in hand, the batters can take risks in the last ten overs and the real total usually lands above the projection; with two wickets left, the tail has to survive first, and the real total often lands below it. Check it again every five overs, because the projection moves with the rate. A quiet over drops it by a few runs, a 20-run over lifts it by more than ten, and that movement is the honest picture of how the innings is going.

Frequently asked questions

Does this assume the same scoring rate all innings?

Yes. It simply extends the current run rate to the remaining overs. It does not predict acceleration in the death overs or a collapse.

Are wickets taken into account?

No. A team 150 for 8 projects the same as a team 150 for 1 here, even though the real prospects differ greatly. Treat the figure as a run-rate projection, not a prediction.

What about rain or a shortened match?

The tool uses the total overs you enter. For a rain-reduced target, official Duckworth–Lewis–Stern calculations apply instead.

When is the projected score most useful?

In the middle overs, roughly from over 15 to over 35 of a 50-over match, when enough balls have been bowled for the run rate to mean something but enough overs remain for the figure to guide decisions. Early on, two or three overs tell you almost nothing, and in the last five overs the remaining overs are too few for the projection to change much.

Why does the projection change every over?

Because the current run rate changes every over. A maiden drops the rate, a big over lifts it, and the projection is just the new rate multiplied by the overs left. That is why the same innings can project 300 after 25 overs and 330 after 30 — the rate moved, so the projection moved with it. Recheck it after each over rather than trusting one early reading.

More tools

Tell us what you think

Loving this tool, or stuck on something? Tell us — it takes a minute.

We’ll only use your name and email to reply if needed. The tool and page are filled in for you.