The key numbers from the 2010 IPL
S Rajesh26-Apr-2010More runs and more wickets than ever beforeThe IPL this year had one more match than in the first two editions (for the third place), but in terms of runs and wickets, the stats for this year were way ahead: the aggregate of 18,864 runs is 993 runs more than the tally in 2008, while 23 more wickets fell this year than in 2009. That’s mainly because, unlike in the last two years, not a single game was rained out or shortened: the closest we came to a disruption was the bomb blast in Bangalore, despite which a full 20-over game was played that day.The run rate, though, dropped slightly this year compared to 2008, but it was still much more than the 2009 edition which was moved to South Africa. The marginal drop in run rate was largely due to the slower pitches and more difficult batting conditions in the last two weeks. In the first 41 matches of the IPL, teams scored at an average run rate of 8.40 runs per over; in the last 19 games, it dropped significantly to 7.50. That was also the reason why the sixes tally fell short of 600 this year – there were only 159 of them in the last 19 matches an average of 8.37 per game; in the first 41 games, the average was 10.39 per match.
YearRunsWicketsAverageRun rate4s/ 6s200817,93168926.028.301703/ 623200916,32069723.417.481317/ 506201018,86472026.208.121708/ 585Batting and bowling stats for each teamMumbai Indians were the dominant team throughout the IPL, and their domination is reflected in their stats: the difference between their batting run rate and bowling economy rate is 0.80, which is the highest of all teams. Chennai Super Kings improved their numbers considerably towards the end of the tournament, which is why the difference in their rates is a respectable 0.39 despite winning only nine out of 16 matches. Royal Challengers Bangalore are the only other team with a difference of more than 0.20, but the stats for the fourth semi-finalist, Deccan Chargers, is quite poor. They finished with a difference of -0.41, some of which was due to their meek finish to the tournament, when they were walloped by Bangalore in the third-place playoff.The two teams with the worst difference are Rajasthan Royals and Kings XI Punjab, the sides which finished at the bottom of the table. What’s more surprising, though, is that their numbers are that much poorer than Deccan’s.
TeamBat averageRun rateBowl averageRun rateDiff in averageDiff in run rateChennai Super Kings29.828.3324.577.945.250.39Mumbai Indians27.108.6323.937.833.170.80Royal Challengers Bangalore27.918.1626.717.951.200.21Deccan Chargers21.007.6224.338.03-3.33-0.41Delhi Daredevils24.487.9222.567.851.920.07Kolkata Knight Riders30.197.8730.028.190.17-0.32Rajasthans Royals23.188.1328.158.59-4.97-0.46Kings XI Punjab28.478.2632.398.73-3.92-0.47Comparing every stageThe overall Powerplay stats in 2010 were a touch better than those in 2008 – the run rate was marginally higher, at 7.89. That’s thanks largely to Delhi Daredevils (run rate 8.53), Mumbai (8.35), and Punjab (8.02), the only teams with a rate of more than eight.
YearRunsWicketsAverageRun rate4s/ 6s2008535817630.447.70691/ 1352009493318726.377.22554/ 1562010568217632.287.89746/ 123In the middle overs teams were slightly slower than in 2008, with Rajasthan (8.13) the only team to manage a run rate of more than eight. Surprisingly Mumbai (7.14) and Delhi (7.16) were the teams with the slowest run rates.
YearRunsWicketsAverageRun rate4s/ 6s2008709922431.697.87557/ 2412009602722027.396.72387/ 1482010721725428.417.54513/ 211The last six overs too saw a marginal drop in scoring rate compared to 2008 (though they were all higher than the 2009 numbers). Mumbai were the standout team, scoring at 10.97 runs per over, while Bangalore (9.74) and Chennai (9.68) were the others to score at more than nine-and-a-half.
YearRunsWicketsAverageRun rate4s/ 6s2008547428918.949.75455/ 2472009536029018.488.91376/ 2022010596529020.569.24449/ 251The Ashwin and Bollinger factorThe presence of Doug Bollinger, and the decision to open the attack with him and R Ashwin, made a huge difference to Chennai’s fortunes. They had won only three out of eight games till then, but won six out of eight after he came in. The biggest difference was in their bowling in the first six overs: in the first eight matches they were clueless, neither taking wickets nor keeping runs in check – they economy rate of 8.39 was the second-worst at that point.Once Bollinger and Ashwin took the new ball, though, Chennai’s fortunes changes completely, and they became the best bowling team in the Powerplays, taking 13 wickets at an excellent economy rate of 6.35.
MatchesWicketsAverageEcon rateWithout Bollinger81040.308.39With Bollinger81323.466.35Both bowlers were equally effective in the first six, which allowed Chennai to choke the runs and force batsmen into errors. Ashwin and Bollinger both managed economy rates of less than five, which is exceptional in this format.
BowlerBallsRuns concededWicketsAverageEcon rateR Ashwin11489614.834.68Doug Bollinger11494615.674.94The best in the PowerplaysThe table below shows the top batsmen in the powerplay overs in IPL 2010. Sachin Tendulkar, who was the top run getter in the tournament, amassed more than 300 runs at an exceptional average. Virender Sehwag scored at the quickest rate while Adam Gilchrist, who otherwise had a poor IPL, hit the most sixes.
BatsmanRuns scoredStrike rateAverage4s6sSachin Tendulkar3278.24109.00550Jacques Kallis2746.6845.66423Adam Gilchrist2499.2219.152913M Vijay2418.6548.202311Virender Sehwag2409.3526.66387Matthew Hayden2376.9323.70309Michael Lumb2258.8845.00375Sourav Ganguly2196.7373.00355Naman Ojha2087.4726.00305Chaminda Vaas was extremely economical and also picked up eight wickets during the Powerplays. The other revelations were Bollinger and Ashwin, who played crucial roles in Chennai’s success.
BowlerBalls bowledEconomy rateWickets takenAverageChaminda Vaas904.8689.12Ryan Harris964.87515.60Doug Bollinger1144.94615.66R Ashwin1325.00715.71Dirk Nannes1025.17329.33Shane Bond906.26423.50Lasith Malinga1206.65622.16Praveen Kumar1687.25450.75Dale Steyn1627.33633.00Zaheer Khan1447.45444.75The best finishersKeiron Pollard scored the most runs in the last six overs, at an average of more than 13 per over. In terms of strike rate, though, he was pipped to the post by Robin Uthappa, who had a strike rate of nearly 14 runs per over.
BatsmanRunsBallsDismissalsAverageRuns per overKeiron Pollard234107926.0013.12Virat Kohli186110823.2510.14S Badrinath178127725.428.40Irfan Pathan17491443.5011.47Rohit Sharma163105723.289.31Albie Morkel14790624.509.80Angelo Mathews14493436.009.29Robin Uthappa14362435.7513.83Among the bowlers Anil Kumble was outstanding with an economy rate of 6.36, which was one run better than his nearest competitor, Lasith Malinga of Mumbai. Dale Steyn and Muttiah Muralitharan were impressive too, but Zaheer Khan was the only bowler to take ten wickets during the last six overs.
BowlerBalls bowledRuns concededWicketsAverageEcon rateAnil Kumble98104714.856.36Lasith Malinga114140817.507.36Dale Steyn90113618.837.53Muttiah Muralitharan90118716.857.86Zaheer Khan1161641016.408.48More numbers97 – The number of sixes struck by Chennai, the highest in the tournament. Deccan and Bangalore conceded the most sixes – 85 each.
27 – The number of sixes struck by Robin Uthappa, which is one more than Murali Vijay’s tally. Pragyan Ojha conceded the highest number of sixes – 17.
23 – The number of run-outs effected by Delhi, the highest in the tournament and one more than Chennai. Rajasthan’s batsmen were run out most often – 34 times.
72 – The number of wides bowled by Bangalore, which is the highest. The two bowlers leading in this regard are also from Bangalore – Steyn (28) and Praveen (18).
185.71 – Kieron Pollard’s strike rate, which is the highest among batsmen who’ve scored more than 100 runs. Uthappa is next at 171.55.