T20 Score at 10 Overs: What the Halfway Total Becomes by Over 20
Runs and wickets at the halfway mark of a T20 first innings say a lot about the final total. Here is how often each branch follows.
If the side batting first in a T20 has a given score and wickets down after 10 overs, what final total does it go on to make?
- A89.9 runsAverage runs added in overs 11-20
- B100.9 runsRuns added when 0 down at 10 overs
- C63.5 runsRuns added when 5+ down at 10 overs
- D91.7%180+ from 100+ for 0-1 down at halfway
The halfway total is the in-play number I watch most closely in a T20 first innings. When I build the totals view on my today's cricket predictions page, I want to know two things at the end of the 10th over: the score, and how many wickets it cost. This study takes 6,169 full-length first innings and asks what each of those halfway states went on to become.
The headline answer is that wickets matter as much as runs. On average the side batting first added 89.9 runs in overs 11-20, but that figure stretches from 100.9 runs with nobody out to 63.5 runs at 5 or more down. A strong platform with wickets in hand converts very reliably: from 100+ with 0-1 down, 91.7% of innings finished on 180 or more.
Branch AWickets in hand decide how much the back half adds
This chart sorts innings by wickets down after 10 overs and shows the average added from there. It slopes down steadily: 100.9 runs at 0 down, 98.7 at 1 down, 81.3 at 4 down. Then it falls off a cliff to 63.5 runs at 5 or more down.
That last step is bigger than any of the steps before it. It is the point where a side stops swinging freely and starts protecting a lower order that cannot be trusted to finish the job.
Match counts in brackets.
View the data: runs added in overs 11-20 by wickets down at 10
| Batting first: average runs scored after the halfway mark | |
|---|---|
| 0 down (337) | 100.9 runs |
| 1 down (1,166) | 98.7 runs |
| 2 down (1,777) | 94.1 runs |
| 3 down (1,592) | 88.3 runs |
| 4 down (864) | 81.3 runs |
| 5+ down (433) | 63.5 runs |
I don't treat wickets as a small adjustment to the run rate. Five down at halfway is a different innings altogether, not a slower version of the same one.
Branch BDoubling the halfway score holds best at 2-4 down
The old rule of thumb says you double the 10-over score to get the final total. The table shows the final total at least doubled in 74.1% of innings at 2 down, 75.2% at 3 down and 74.0% at 4 down. It works less well at the edges: 68.2% at 0 down and 55.7% at 5 or more down.
The 0-down figure looks odd until you remember that those sides usually have higher halfway scores, so doubling asks more of them. At 5 or more down, the rule simply runs out of batters.
| Wickets at 10 | Innings | Avg added | Median added | Doubled or more |
|---|---|---|---|---|
| 0 down | 337 | 100.9 | 102.0 | 68.2% |
| 1 down | 1,166 | 98.7 | 98.0 | 69.7% |
| 2 down | 1,777 | 94.1 | 93.0 | 74.1% |
| 3 down | 1,592 | 88.3 | 88.0 | 75.2% |
| 4 down | 864 | 81.3 | 81.0 | 74.0% |
| 5+ down | 433 | 63.5 | 65.0 | 55.7% |
The medians sit very close to the averages. At 3 down the average addition was 88.3 runs and the median 88.0, so a few huge innings are not inflating these figures.
Branch CReaching 180 depends on score and wickets together
The heatmap gives the chance of finishing on 180 or more from each halfway state. From 100+ with 0-1 down it is 91.7% (314 innings). From 80-89 it swings from 55.9% at 0-1 down to 33.6% at 4 or more down. From 70-79 it falls from 30.9% at 0-1 down to 17.7% at 3 down.
Under 70, a 180 finish was rare: 10.5% at 2 down and 2.9% at 4 or more down. Read across any row and the wickets column changes the picture as much as ten extra runs would.
Cells under 100 innings: 90-99 / 4+ down (44); 100+ / 3 down (73); 100+ / 4+ down (20).
View the data: chance of reaching 180 from the 10-over score
| 0-1 down | 2 down | 3 down | 4+ down | |
|---|---|---|---|---|
| Under 70 | 13.4% | 10.5% | 5.1% | 2.9% |
| 70-79 | 30.9% | 23.4% | 17.7% | 14.3% |
| 80-89 | 55.9% | 49.0% | 42.5% | 33.6% |
| 90-99 | 76.0% | 71.4% | 67.6% | 31.8% |
| 100+ | 91.7% | 87.6% | 91.8% | 75.0% |
Some cells are thin. The 90-99 at 4 or more down cell rests on 44 innings and the 100+ at 4 or more down cell on only 20, so I give those figures little weight. If you set these chances against a pre-match total line, remember that the pre-game line can no longer be bet once the halfway state is known. The live line is the one you are actually facing.
Branch DThe halfway score sets the floor and ceiling
This chart splits final totals into bands for each 10-over score. Under 70 at halfway, 62.3% of innings finished under 150 and only 0.7% reached 200. At 100+, the picture flips: 70.1% finished on 200 or more and just 0.3% finished under 150.
View the data: where the innings finished, by 10-over score
| Under 150 | 150-179 | 180-199 | 200+ | |
|---|---|---|---|---|
| Under 70 at 10 ยท 2,127 | 62.3% | 31.7% | 5.3% | 0.7% |
| 70-79 at 10 ยท 1,430 | 24.3% | 54.1% | 16.5% | 5.1% |
| 80-89 at 10 ยท 1,250 | 7.8% | 43.9% | 33.6% | 14.6% |
| 90-99 at 10 ยท 770 | 2.6% | 27.0% | 36.8% | 33.6% |
| 100+ at 10 ยท 592 | 0.3% | 9.8% | 19.8% | 70.1% |
The 80-89 band is the most open one. In that band, 43.9% finished on 150-179 and 33.6% on 180-199, so there is real width in the outcome. That is where I spend most of my thinking, and where wickets do most of the sorting.
Branch EHalfway scores and back-half runs have both climbed
In 2012 the average 10-over score batting first was 70.5, with 85.4 runs added in overs 11-20. In 2026 those figures were 84.2 and 92.9. Both lines rise, and the halfway score has risen faster.
This is the main caveat for the whole study. Because scoring has accelerated, the all-years tables understate what a modern halfway score becomes. The figures also pool leagues with very different grounds and conditions. These are past frequencies, not a system, and they guarantee nothing.
Years with fewer than 150 qualifying matches are left out; 2026 covers matches up to mid-September.
View the data: halfway score and back-half runs by year
| Score at 10 overs | Runs added overs 11-20 | |
|---|---|---|
| 2012 | 70.5 runs | 85.4 runs |
| 2013 | 70.2 runs | 86.8 runs |
| 2014 | 73 runs | 88.2 runs |
| 2015 | 73.5 runs | 87.5 runs |
| 2016 | 73.5 runs | 87.2 runs |
| 2017 | 78.1 runs | 87 runs |
| 2018 | 78 runs | 90.6 runs |
| 2019 | 75.9 runs | 89.5 runs |
| 2020 | 76.3 runs | 88.8 runs |
| 2021 | 75.2 runs | 88.4 runs |
| 2022 | 77.4 runs | 93.1 runs |
| 2023 | 78.8 runs | 92.7 runs |
| 2024 | 79.5 runs | 91.1 runs |
| 2025 | 81.8 runs | 93.7 runs |
| 2026 | 84.2 runs | 92.9 runs |
I treat the earlier tables as a baseline and shade them upward for recent seasons. I also adjust for the ground, the dew and how the surface played in the powerplay.
If this happensโฆ
At 5 or more down, sides added 63.5 runs on average, against 100.9 with none down. Fix the wickets column first, then read the score.
Doubling the halfway score held in 74.1% of innings at 2 down and 75.2% at 3 down. It is much weaker at 5 or more down, at 55.7%.
From 80-89 at halfway, the chance of 180 ran from 55.9% at 0-1 down to 33.6% at 4 or more down. Conditions and the batters still to come matter most here.
Questions bettors ask
How many runs are scored in the last 10 overs of a T20?
Across 6,169 first innings, the side batting first added 89.9 runs on average in overs 11-20. That rose to 100.9 runs with no wicket down and fell to 63.5 runs at 5 or more down.
Does a T20 score double after 10 overs?
Usually, if a side is 2 to 4 wickets down: the final total at least doubled in 74.1% of innings at 2 down and 75.2% at 3 down. At 5 or more down it held in only 55.7%.
What 10-over score usually leads to 200 in a T20?
Of innings on 100+ at 10 overs, 70.1% finished on 200 or more. From under 70 at halfway, only 0.7% reached 200.
I'm Arjun Deshpande, based in Mumbai, and I write the cricket match predictions at cricketscoretips.com โ reading the pitch as closely as the form.
View profile โ
