Royals v Knight Riders, IPL 2014, Ahmedabad May 5, 2014

KKR's house of cards

Kolkata Knight Riders lost six wickets for two runs against Rajasthan Royals, the worst such collapse in the IPL

When Gautam Gambhir and Robin Uthappa added 121 for the first wicket in the chase against Rajasthan Royals, it was way more than what the team would have expected from their opening pair. In 103 previous matches, no KKR opening pair had ever added so many; there were only two previous century stands - the highest being 113 - and the aggregate of nine previous opening partnerships for KKR had been a grand total of 99.

So, when Gambhir and Uthappa put together 121 in 14 overs in a chase of 171, KKR would have been fairly confident of the following batsmen managing the remaining 50 runs in six overs. As it transpired, the record opening partnership was only a precursor to a record collapse, as KKR lost six wickets for two runs, the worst six-wicket collapse in the IPL. The collapse included Pravin Tambe's hat-trick, and KKR never recovered from the shock.

The table below lists the worst six-wicket collapses in the IPL, and this one takes the top position by some distance. The next two are instances of teams losing six wickets for seven runs, but those are both lower-order collapses, when teams lost their last six wickets cheaply. A similar top-order crash was seen in the 2011 IPL game between Deccan Chargers and Kochi Tuskers, when Kochi, chasing only 130 for victory, slumped to 11 for 6 and were eventually bowled out for 74. Among the batsmen who succumbed during that collapse were Brendon McCullum, Mahela Jayawardene and Brad Hodge.

Of the nine matches in which teams lost six wickets for 12 runs or fewer in the IPL, eight ended in defeat for the team that collapsed. The only exception was Mumbai Indians, who chased a target of 174 against Chennai Super Kings despite going from 147 for 2 to 159 for 8.

Biggest six-wicket collapses in the IPL
Team For wkts Collapse
Collapse Versus Result
Kolkata Knight Riders 1 to 6 121 for 1 123 for 6 2 for 6 Rajasthan Royals (2014) Lost by 10 runs
Rajasthan Royals 5 to 10 85 for 5 92 all out 7 for 6 Royal Challengers Bangalore (2010) Lost by 10 wkts
Pune Warriors 5 to 10 101 for 5 108 all out 7 for 6 Sunrisers Hyderabad (2013) Lost by 11 runs
Deccan Chargers 5 to 10 150 for 5 161 all out 11 for 6 Delhi Daredevils (2009) Lost by 12 runs
Kochi Tuskers Kerala 1 to 6 0 for 1 11 for 6 11 for 6 Deccan Chargers (2011) Lost by 55 runs
Mumbai Indians 3 to 8 147 for 3 159 for 8 12 for 6 Chennai Super Kings (2012) Won by 2 wkts
Deccan Chargers 4 to 9 149 for 4 161 for 9 12 for 6 Delhi Daredevils (2009) Lost by 12 runs
Mumbai Indians 5 to 10 96 for 5 108 all out 12 for 6 Kolkata Knight Riders (2012) Lost by 32 runs
Rajasthan Royals 5 to 10 105 for 5 117 all out 12 for 6 Royal Challengers Bangalore (2013) Lost by 7 wickets

S Rajesh is stats editor of ESPNcricinfo. @rajeshstats

Comments have now been closed for this article

  • Dummy4 on May 6, 2014, 18:08 GMT

    Next Match, KKR XI should be this---1.Gambhir 2.Uthappa 3.Shakib 4.Lynn 5.Pathan 6.Suryakumar Yadav 7.Russel 8.Vinay 9.Umesh Yadav 10.Narine 11.Piyush Chawla

  • Dummy4 on May 6, 2014, 11:59 GMT

    KKR needs kallis/chris lynn, RN ten Doeschate, sakib and narine. Doeschate and Y pathan will be finisher at no 6 and 7. Order of batting- 1 utappa 2 gambhir 3 kallis/lynn 4 sakib. 5 Suryakumar Yadav/manish. Rest are 8 Vinay 9 Umesh Yadav 10 narine 11 Piyush Chawla . just keep playing 3-4 matches i think kkr will show boost up...

  • Dummy4 on May 6, 2014, 9:57 GMT

    how stupid management of batting order of kkr

  • Dummy4 on May 6, 2014, 5:01 GMT

    You cannot include bottom order collapse ( X for 5 to Y all out ) in this list. What happened in the match is a top order collapse(121 for 0 to 123 for 6). The difference between top order & bottom order collapse is infinite. Greatest collapse ever. Great captaincy by watson

  • Rohantha on May 6, 2014, 4:18 GMT

    Excellent stats and another indication that yesterday's implosion could only be believed if you saw it. Sending Russel in at 3 was pure stupidity for a struggling team looking somehow win a match. Shakib is wasted down the order and should bat at 3 in the absence of Kallis. Unfathomable use of resources!

  • Ashok on May 5, 2014, 21:30 GMT

    Mr. Rajesh, your stats. are amazing. But today's KKR collapse is too shocking for words- 6 wkts. for 2 runs.! An IPL team after 7 matches of playing together should have a settled batting order. It always shocks me to see how Gambhir comes with so many "inventive topsy turvy batting orders". How can Russell, even in wildest dream, come at #3? I presume the Batting orders in T20 are mainly based on ability & current form to fit into certain spot in the order. If a wrong guy is put in the wrong spot, it will cause in loss of teams momentum. With Uthappa & Gambhir having batted that well with 121 runs in 14 overs, an equally strong batsman was needed to follow & continue their momentum such as Shakib or Yadav, in this case. These 2 are technically sound & have scored heavily this season. Yusuf Pathan is #5 batsman- a Finisher. Russell is a tail ending Hitter- say #7 or 8.No wonder Watson & Thambe made a short of next 4 to swing the momentum in RR's favour & too late to reverse it.

  • No featured comments at the moment.