The most and least productive overs in the IPL
A look at the average number of runs scored in each over in IPL 2010

The 50-over format has been around for so long that players and fans have a pretty good idea of how an innings usually progresses: the first couple of overs are used by batsmen to get their eye in, after which they try to make full use of the fielding restrictions during the Powerplay overs; thereafter, the middle overs are usually a time to consolidate the early gains, before the final slog in the last eight to 10 overs.
The Twenty20 format, though, is so condensed that it's far more difficult to arrive at distinct stages of an innings. Since batsmen attempt to score boundaries almost throughout, do the Powerplay overs really yield a lot more runs than the middle overs? And when do teams really push the accelerator towards the end of their innings? Here's an attempt to find the answers, by looking at the over-wise stats in IPL 2010.
Most of the numbers below are along expected lines: batsmen take an over to get started before trying to make good use of the Powerplays, there's a brief period of consolidation in the middle, and the last four overs are when teams really turn it on. Some of the key points are mentioned below:
- The lowest run rate is in the first over (6.53), which is also the only over when the average is less than seven. Apart from the first over, the lowest run rate is in the eighth over (7.14).
- The most wickets have obviously fallen towards the end of the innings, but excluding the last four overs, the 11th over is the one in which the most wickets have fallen. Forty-two have tumbled in this over, compared with 31 and 33 in the overs before and after it. (If anyone has any specific ideas on why this might have happened, please write in.)
Over | Runs | Wickets | Average | Run rate |
1st | 745 | 21 | 35.47 | 6.53 |
2nd | 955 | 22 | 43.40 | 8.37 |
3rd | 910 | 36 | 25.27 | 7.98 |
4th | 991 | 30 | 33.03 | 8.69 |
5th | 989 | 34 | 29.08 | 8.67 |
6th | 897 | 24 | 37.37 | 7.86 |
7th | 852 | 28 | 30.42 | 7.47 |
8th | 814 | 19 | 42.84 | 7.14 |
9th | 872 | 26 | 33.53 | 7.64 |
10th | 852 | 31 | 27.48 | 7.47 |
11th | 846 | 42 | 20.14 | 7.44 |
12th | 854 | 33 | 25.87 | 7.55 |
13th | 917 | 27 | 33.96 | 8.11 |
14th | 911 | 36 | 25.30 | 8.09 |
15th | 842 | 30 | 28.06 | 7.51 |
16th | 925 | 35 | 26.42 | 8.38 |
17th | 1027 | 42 | 24.45 | 9.53 |
18th | 998 | 46 | 21.69 | 9.58 |
19th | 1013 | 44 | 23.02 | 10.19 |
20th | 926 | 72 | 12.86 | 11.00 |
Digging deeper at that 11th over syndrome, it's strange to see that all teams except Chennai have succumbed to it. Chennai have lost only one wicket in the 11th, averaging more than eight-and-a-half per over, but the others have all lost at least four wickets, with Punjab, Deccan and Rajasthan losing seven.
Team | Runs | Dismissals | Average | Run rate |
Chennai Super Kings | 120 | 1 | 120.00 | 8.57 |
Kings XI Punjab | 117 | 7 | 16.71 | 8.35 |
Kolkata Knight Riders | 116 | 4 | 29.00 | 8.28 |
Royal Challengers Bangalore | 121 | 6 | 20.16 | 8.25 |
Deccan Chargers | 105 | 7 | 15.00 | 7.50 |
Delhi Daredevils | 96 | 4 | 24.00 | 6.85 |
Rajasthan Royals | 90 | 7 | 12.85 | 6.42 |
Mumbai Indians | 81 | 6 | 13.50 | 5.40 |
From the over-wise stats in the first table, it's possible to split the 20-over innings into four parts, based on the run rates. During the Powerplays, teams have averaged round eight runs per over, which drops to about seven-and-a-half between overs seven and 12. Teams pick it up again to around eight per over between 13 and 16 - note that the run rate during this period is exactly the same as during the Powerplays, in IPL 2010. And then, after the 16th over - which is often after the second strategic time-out - teams have really turned it on, averaging more than 10 per over.
Period | Runs | Wickets | Average | Run rate |
Overs 1 to 6 | 5487 | 167 | 32.85 | 8.02 |
Overs 7 to 12 | 5090 | 179 | 28.43 | 7.45 |
Overs 13 to 16 | 3595 | 128 | 28.08 | 8.02 |
Overs 17 to 20 | 3964 | 204 | 19.43 | 10.02 |
Overall, IPL 2010 has been much more high-scoring than the previous edition in South Africa, but the biggest difference between the two seasons is perhaps in the first-over stats. In 2009, the first over fetched 38 wickets - which was double the number from the previous year - while the run rate was less than a run a ball. In 2010 the numbers have gone back to the 2008 levels, with the run rate being higher this year.
Year | Balls | Runs | Dismissals | Average | Run rate |
2008 | 696 | 703 | 19 | 37.00 | 6.06 |
2009 | 684 | 634 | 38 | 16.68 | 5.56 |
2010 | 684 | 745 | 21 | 35.47 | 6.53 |
The other amazing stat last year was the number of wickets that fell off the very first ball - there were 11 such instances in 2009. In 2010 it's happened only three times so far: in the very first match, when Chaminda Vaas dismissed Manoj Tiwary; in the 13th game, when Kolkata's Ashok Dinda dismissed Michael Lumb of Rajasthan; and more recently when Ryan Harris nailed Manish Pandey in the Deccan-Bangalore game in Nagpur.
Year | Balls | Runs | Dismissals | Average | Run rate |
2008 | 116 | 96 | 1 | 96.00 | 4.96 |
2009 | 114 | 55 | 11 | 5.00 | 2.89 |
2010 | 114 | 99 | 3 | 33.00 | 5.21 |
S Rajesh is stats editor of Cricinfo
Read in App
Elevate your reading experience on ESPNcricinfo App.