Cricket Country Staff
Editorial team of CricketCountry.
Written by Cricket Country Staff
Published: Apr 24, 2017, 05:51 PM (IST)
Edited: Apr 24, 2017, 06:28 PM (IST)
The Indian fans, and also the world cricket, are still talking about the disastrous collapse for mere 49 by Virat Kohli‘s Royal Challengers Bangalore (RCB) against former 2-time champions Kolkata Knight Riders (KKR), in Match 27 of the ongoing Indian Premier League (IPL) 2017 at the historic Eden Gardens Stadium in Kolkata on Sunday. The match itself was a much-hyped one, and had everyone talking prior to the match all over social media. The social media also got heavily engaged during the match. However, following the massive win by Kolkata, the Twitter exploded, as over 2,10,000 tweets were registered. Kolkata won the match by mammoth 82 runs. FULL CRICKET SCORECARD: Royal Challengers Bangalore (RCB) vs Kolkata Knight Riders (KKR), IPL 2017, Match 27 at Eden Gardens
Meanwhile, Bangalore’s Pawan Negi has blamed Bangalore’s horrific batting collapse for the defeat. He added that it was a part and parcel of the game, while also adding that the fair amount of seam movement on the Eden track did allow Kolkata bowlers the advantage, as they managed to restrict Bangalore at the lowest IPL score till date. Negi also did not blame the pre-match shower, which could have helped the Kolkata pacers. Royal Challengers Bangalore (RCB) on Sunday registered the lowest-ever total in the history of Indian Premier League (IPL) 2017. RCB were bowled out for a mere 49 in 9.4 overs against Kolkata Knight Riders (KKR) while chasing a paltry score of 132. This is also the 10th lowest total overall in all T20 cricket.
Chasing a target of 132 to win, RCB were bowled out with more than 10 overs to spare, precisely 62 balls. Among the teams bowled out for lowest total, RCB also faced the least number of overs in their innings.
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 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.