The swashbuckling New Zealand skipper Brendon McCullum smashed a 64-ball 158* against Derbyshire in the NatWest T20 Blast on Friday. Riding on McCullum’s thrilling knock Birmingham Bears defeated Derbyshire by 60 runs. Sudatta Mukherjee analyses McCullum’s latest feat against his 158* for Kolkata Knight Riders (KKR) in Indian Premier League (IPL) 2008. READ: Brendon McCullum blasts 158 off 64 balls for Warwickshire against Derbyshire in Natwest T20
The first time was in the inaugural match of Indian Premier League (IPL) 2008. McCullum smashed a 73-ball 158 while playing for Kolkata Knight Riders (KKR) against Royal Challengers Bangalore (RCB). On Friday, he again scored 158, this time off 64 balls. Incidentally, it was McCullum’s second game for Birmingham Bears in NatWest T20 Blast this year.
Both the matches saw McCullum play some similar shots; especially the scoop or ramp shot which has become a staple in McCullum’s big innings. Let us look at how McCullum reached both the milestones.
Team
Runs
Balls
4s
6s
SR
KKR
158
73
10
13
216.43
Birmingham Bears
158
64
13
11
246.87
McCullum took nine balls less than the previous occasion and has a better strike-rate for Birmingham Bears. While he hit three more fours in NatWest T20 Blast, he hit two sixes fewer than he had for KKR.
For Birmingham Bears
Partner
Runs
Balls
Varun Chopra
160
79
Laurie Evans
45
24
William Porterfield
37*
17
For KKR
Sourav Ganguly
61
32
Ricky Ponting
51
41
David Hussey
60
30
Mohammad Hafeez
50*
29
While playing for KKR, McCullum shared four fifty-run partnerships. For Birmingham Bears, he had a 160-run partnership with Chopra, a 45-run alliance with Laurie Evans, and 37 runs with Porterfield.
For KKR
Fifties
Balls
4s
6s
50
32
5
3
100
53
3
4
150
70
2
5
For Birmingham Bears
50
23
5
3
100
42
3
5
150
60
4
2
McCullum took nine balls fewer to score his half-century for Birmingham Bears compared to his KKR innings. However, he smashed an equal number of fours and sixes in his race to fifty. He took 11 balls less to reach his 100 in NatWest T20 Blast. He scored an equal number of fours but two more sixes.
If we compare McCullum’s strike rate against individual bowlers, the ones who faced the wrath of McCullum’s wood were mainly Zaheer Khan and Cameron White. The latter bowled only three balls, but was hit for two sixes and one four.
Bowler
4s
6s
Runs
Balls
SR
Praveen Kumar
2
3
32
16
200
Zaheer Khan
3
2
33
15
220
Ashley Noffke
1
2
24
12
200
Jacques Kallis
3
2
32
16
200
Sunil Joshi
0
2
21
11
190.9
Cameron White
1
2
16
3
533.33
On Friday, it was spinners Chesney Hughes and Scott Elstone — who bowled four balls each — who got smashed royally. However, out of seven bowlers, only Shiv Thakor enjoyed a strike-rate less than 200.
Bowler
4s
6s
Runs
Balls
SR
Nathan Rimmington
3
2
33
13
253.84
Wayne White
3
2
33
13
253.84
Shiv Thakor
2
1
17
9
188.88
Alex Hughes
2
3
36
15
240
Wes Durston
0
2
16
6
266.66
Chesney Hughes
2
0
11
4
275
Scott Elstone
1
1
12
4
300
In the IPL 2008 match, the 15th over of KKR’s innings was the costliestwith 24 runscoming off that over. McCullum hit two sixes and one four in that over. On Friday, the 4th over of the Birmingham Bears’ inningswas the costliest when 18 runscame off the over. McCullum hit two fours and one six.
McCullum scored 44 runs on the off side and 114 runs came on the leg side in IPL 2008. On Friday, 86 came from the off side and 72 runs from the leg side.
Incidentally, in both the matches, McCullum scored 22 runs from singles and took nine twos.
While KKR won by 140 runs after scoring 222, Birmingham Bears won by 60 runs after scoring 242.
TRENDING NOW
(Sudatta Mukherjee is a reporter with CricketCountry. Other than writing on cricket, she spends penning random thoughts on her blog. When she is not writing, you will catch her at a movie theatre or watching some English television show on her laptop. Her Twitter handle is @blackrosegal)
This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Strictly Necessary Cookies
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.