Broadcast graphics love a projected score: "At this rate, 174. At 10 an over, 187." This calculator recreates that graphic for any T20, ODI or custom-length innings. Enter the current score, the overs bowled and the innings length, and you will see the projected total at the current run rate, one run an over slower, and one or two runs an over faster.
How to use the projected score calculator
- Enter the batting side's current score.
- Enter the overs bowled in cricket notation. 10.3 means ten overs and three balls.
- Set the innings length: 20 for a T20, 50 for an ODI, or the reduced number of overs after rain.
- The panel shows the projections, the current run rate and the balls remaining.
The projected score formula
Current run rate = Runs ÷ (Balls bowled ÷ 6)
Projected total = Runs + Run rate × (Balls remaining ÷ 6)
The faster and slower projections simply add or subtract one or two runs per over from the current rate before applying the same formula. The answers are rounded to whole runs.
Worked example: a T20 innings at halfway
A team is 87 for 1 after 10 overs of a 20-over innings.
- Current run rate = 87 ÷ 10 = 8.70
- Balls remaining = 60, or 10 overs
- Projected at current rate = 87 + 8.70 × 10 = 174
- At 9.70 an over = 184; at 10.70 an over = 194
Most T20 sides score faster in the last 10 overs than the first, especially with wickets in hand. That is why the "+1" and "+2" projections are often closer to the final total than the straight-line figure.
Worked example: an ODI in the middle overs
A team is 168 after 30.4 overs of a 50-over innings. That is 184 balls bowled, so the run rate is 168 ÷ 30.667 = 5.48. There are 116 balls left. At the current rate the total would be about 274, at 6.48 an over about 293, and at 7.48 an over about 313.
Real match example
Royal Challengers Bengaluru v Punjab Kings
- RCB final total
- 190/9 in 20 overs
- Run rate
- 9.50 per over
- Result
- RCB won by 6 runs
RCB lost wickets regularly but kept scoring at close to 9.5 an over. Punjab Kings fell six short, needing 29 from the final over. A projection made at any stage that ignored wickets would have overstated how many RCB could add at the end.
What projections do not account for
- Wickets in hand. 87 for 1 and 87 for 6 give the same projection here, but they are very different positions. The DLS method exists precisely because overs alone do not describe a team's remaining resources.
- Phases of play. Powerplay overs, middle overs and death overs have different typical run rates.
- Conditions. Dew, a slowing pitch or a short boundary can change the scoring rate sharply.
- Who is batting. A set top-order batter and a new tail-ender do not score at the same pace.
Using projections for strategy
Captains and analysts use projections in both directions. The batting side looks at what total is realistic and plans when to accelerate. The fielding side compares projections with venue averages to decide when to attack with wicket-taking bowlers. If you are following a chase rather than setting a total, switch to the required run rate calculator, and when the first innings ends use the target score calculator to turn the total into a chase equation.
Common mistakes
- Treating 10.3 overs as 10.3 decimal. It is 10 overs and 3 balls, which is 10.5 overs in decimal. The calculator converts this for you; use the overs to balls converter if you are doing it by hand.
- Using the original innings length after rain. If overs are lost, enter the revised number.
- Treating the projection as a forecast. It is a reference point. Follow the real thing on CricketSky's live scores.
