How is the projected score calculated?

The current run rate (runs divided by true decimal overs faced) is extended across the overs remaining and added to the current score. A wickets-in-hand tier then adjusts that rate up or down before the final extrapolation.

Why does wickets lost affect the projection?

A team with more wickets in hand can typically accelerate in the closing overs, while a team that has lost several wickets usually bats more cautiously with its tail. The calculator applies a simple multiplier tier based on wickets in hand: 7 or more in hand pushes the rate up, 4 to 6 keeps it close to flat, and 1 to 3 pulls it down.

What happens if the team is all out?

If wickets lost is 10, the innings is over and the projected score equals the current score, since no further overs can be batted.

Is this an official prediction method?

No. It is a straightforward run-rate extrapolation with a simple wickets-in-hand adjustment, not an official statistical model or a match-result prediction. Treat it as a pace estimate, not a certainty.

Can I use this for ODI matches too?

Yes. Change the total overs field to 50 (or any other value) and the same run-rate extrapolation applies, though the wickets-in-hand tiers were tuned with T20 scoring patterns in mind.

Why is the flat projection different from the adjusted one?

The flat projection extends the current run rate with no wickets adjustment at all, so it matches a plain run-rate calculator. The adjusted projection factors in wickets in hand, which is why the two numbers usually differ.

T20 Projected Score Calculator

Name: T20 Projected Score Calculator
Availability: InStock
Author: Nham Vu

Enter the current score, overs faced, and wickets lost to get a projected final T20 score based on run-rate extrapolation.

Current Innings

Current Score

Overs Faced

Wickets Lost

Total Overs

Overs faced use X.Y notation, where Y is balls (0–5). 10.4 = 10 overs and 4 balls.

Quick Examples

Enter the current score, overs, and wickets on the left to see a projected final score

How the Projection Is Adjusted

Projected Score = Runs + (Adjusted Run Rate × Overs Remaining)

The adjusted run rate multiplies the current run rate by a wickets-in-hand tier: 7–10 wickets in hand uses 1.20×, 4–6 wickets in hand uses 1.05×, and 1–3 wickets in hand uses 0.90×. This is a simplified estimate, not an official prediction method.

Copied!

Summary

Enter the current score, overs faced, and wickets lost to get a projected final T20 score based on run-rate extrapolation.

How it works

Enter the current score and overs faced, using X.Y notation where Y is balls (0–5), e.g. 15.4 for 15 overs and 4 balls.
Enter wickets lost (0–10) and the total overs for the innings (20 for standard T20).
The calculator converts overs faced to true decimal overs and finds the current run rate (CRR).
A wickets-in-hand tier adjusts the projected run rate for the overs remaining: more wickets in hand pushes the rate up, fewer pulls it down.
The projected final score extends that adjusted rate across the remaining overs and adds it to the current score.
A flat projection (no wickets adjustment) is shown alongside it for comparison.

Use cases

Estimate where a T20 innings is heading while watching a live match.
Compare a broadcast's projected score against a straightforward run-rate extrapolation.
Gauge how much wickets in hand should be expected to lift or lower the final total.
Set a target expectation before a chase begins.
Check fantasy cricket projections mid-innings.
Review how a top-order collapse changes the projected total.

Frequently Asked Questions

Last updated: 2026-07-24 · Reviewed by Nham Vu