Skip to content
CricketTaken

Projected Score Calculator

A projected score takes the rate an innings is scoring at and carries it forward to the end. A side on 142 after 30 of 50 overs is scoring at 4.73, so twenty more overs at that pace adds about 95 and projects 237.

Projected score237At the current run rate, with no acceleration
Current run rate
4.73
Balls remaining
120
At 8 an over from here
302
At 12 an over from here
382

Projected score = current runs + (current run rate × overs remaining)

The calculator also shows where the innings lands at eight and twelve an over from here, because almost no side finishes at the rate it was scoring at halfway. The projection is a baseline, not a forecast.

Why a flat projection always understates a limited-overs innings

Scoring is not evenly distributed. A fifty-over innings typically starts briskly in the powerplay, slows through the middle while a partnership is built, and accelerates sharply in the last ten overs. A projection made at the thirty-over mark extrapolates the slow phase and misses the fast one.

That is why the figure at the current rate is usually the floor rather than the expectation, and why the higher rates on this page are the more useful numbers in the last fifteen overs.

Wickets are the missing variable

The projection has no idea how many wickets are left. A side on 142 for 1 and a side on 142 for 7 project identically and will not finish anywhere near each other, because one can attack for twenty overs and the other is protecting a tail.

Read the projection alongside wickets in hand, and treat it as the answer to "where does this go if nothing changes" rather than "where does this end".

Projection and par score are not the same

A projected score extrapolates this innings. A par score describes what a good total looks like at this ground in these conditions, drawn from history rather than from the current match.

Both are useful and they answer different questions. In a rain-affected match, "par" means something more specific again: the Duckworth-Lewis-Stern score that would leave the chasing side exactly level.

Questions

Projected score, answered

How do you calculate a projected score in cricket?

Work out the current run rate by dividing runs by overs faced, then multiply that rate by the overs remaining and add it to the current score. A side on 142 after 30 of 50 overs is scoring at 4.73 and projects to roughly 237.

Why is the projected score usually too low?

Because limited-overs innings accelerate. A flat projection carries the current rate forward and so extrapolates the slower middle phase while ignoring the final ten overs, where most sides score fastest. It is better read as a floor than as a forecast.

Does the projected score account for wickets lost?

No. The calculation uses only runs and overs, so a side on 142 for 1 and a side on 142 for 7 project to the same total. Wickets in hand are the single biggest factor the projection cannot see.

What is the difference between projected score and par score?

A projected score extrapolates the innings in progress. A par score is what a competitive total looks like at that ground in those conditions, based on past matches. In a rain-affected game, par has a third meaning: the Duckworth-Lewis-Stern score that leaves the chasing side level.

How accurate is a projected score?

As a floor it is reasonable; as a prediction it is not. It assumes the scoring rate holds, which it rarely does in either direction, and it is blind to wickets, to who is batting and to how many overs the best bowlers have left.

How accurate is a projected score in T20?

Less accurate than in a fifty-over game, because a T20 innings accelerates harder over a shorter span. A projection made at ten overs typically understates the final total by a wide margin, since the last five overs often produce more than the first ten. Treat it as a floor.

What is a par score in cricket?

A total that would make the match roughly even at that ground in those conditions, drawn from what past matches there have produced. It is different from a projected score, which extrapolates the innings in progress, and different again from a Duckworth-Lewis par score, which is the figure leaving a chasing side exactly level.

Why do broadcasters show different projected scores?

Because they project at different assumed rates. Most show a row of totals — at the current rate, at eight an over, at twelve — rather than one number, precisely because a single projection would be wrong almost immediately. The spread is more honest than any one figure in it.

Can a projected score account for wickets in hand?

Not in its basic form, which uses only runs and overs. More sophisticated forecasting models do weight wickets, which is the same insight behind the Duckworth-Lewis resource table. A simple projection treats a side one down and a side seven down as identical, and they are not.