TV broadcasts often show “projected scores” at different run rates during the first innings. These projections help fans and captains understand where a match is heading. This guide explains how to predict a cricket score simply and how to adjust for wickets and the final overs, with our free Cricket Score Predictor.
The simple projection
Projected total = Current score + (Run rate × Overs remaining)
Example: 85 runs after 10 overs in a T20 (run rate 8.5). Remaining overs: 10.
| Assumed run rate for remaining overs | Projected total |
|---|---|
| Current (8.5) | 170 |
| 9.0 | 175 |
| 10.0 | 185 |
| 12.0 | 205 |
Check the current run rate with the Run Rate Calculator.
Adjust for wickets
A team at 85/1 can accelerate more than a team at 85/6. A simple rule of thumb: with many wickets in hand, use a higher rate for the last overs; with few, use a lower rate.
The death overs effect
Teams usually score faster at the end. In T20s, the last five overs often go at 10 or more per over when wickets are in hand. In ODIs, the last 10 overs often produce 80 to 100 runs or more.
A better T20 estimate
- Project the middle overs at the current rate.
- Add a higher rate for the last 5 overs.
Example: 85/2 after 10 overs. Overs 11–15 at 8.5 = 42.5; overs 16–20 at 11 = 55. Projected total ≈ 85 + 42.5 + 55 = 182.
Venue and conditions
Average first-innings scores at a ground give context. Dew, pitch wear and boundary size also matter.
Limits
Projections are estimates, not predictions of the future. A couple of quick wickets or a big over can change everything.
From projection to target
The opposition’s target will be the final total plus one; see the Cricket Target Calculator. For defending totals, read par scores in T20 cricket.
Frequently asked questions
How do I project a cricket score?
Current score plus run rate times overs remaining.
Why adjust for wickets?
Teams with more wickets can score faster at the end.
Are projected scores accurate?
They are estimates; wickets and big overs can change the outcome.