Cricket Country Staff
Editorial team of CricketCountry.
Written by Cricket Country Staff
Published: Jan 13, 2018, 02:55 PM (IST)
Edited: Jan 13, 2018, 02:55 PM (IST)
Virat Kohli dropped a bombshell at the toss of the India-South Africa second Test at Centurion. In first Test, he had done the same by stating that vice-captain Ajinkya Rahane was dropped and now Bhuvneshwar Kumar.
Less than half-an-hour into the Cape Town Test, Bhuvi, as he is fondly called, with his first spell swung the match in India’s favour by sending back Dean Elgar, Aiden Markram and Hashim Amla inside five overs. Bhuvi not only picked 6 wickets in the match but also consumed the second most number of balls (127) in the Test after AB de Villiers (134). Remember, it was one of the toughest wickets to hang around?
[link-to-post url=”https://www.cricketcountry.com/news/india-vs-south-africa-2nd-test-virat-kohli-makes-wholesome-changes-for-centurion-test-ishant-sharma-comes-in-for-bhuvneshwar-kumar-677789″][/link-to-post]
Centurion will not provide as much movement as Cape Town did, thus the logic. India went for Ishant for his ability to produce extra bounce. The logic did not go well with the pundits and fans who took to Twitter to slam the Indian captain.
Staggered by the exclusion of Bhuvaneswar. Staggered.
— Harsha Bhogle (@bhogleharsha) January 13, 2018
One player gave you a chance in Capetown. And he won't be bowling at South Africa. #BhuvaneswarKumar
— Harsha Bhogle (@bhogleharsha) January 13, 2018
@BhuviOfficial left out..you are kidding me??
— Allan Donald (@AllanDonald33) January 13, 2018
<script async src=”https://platform.twitter.com/widgets.js” charset=”utf-8″></script>
Bhuvneshwar Kumar in the first Test in Cape Town:
– As a bowler: Most wickets among Indians (6 wkts); second-most after Philander (9).
– As a batsman: Faced most balls among Indians (127 balls); second-most after ABD (134).
2nd Test? DROPPED. #SAvInd
— Bharath Seervi (@SeerviBharath) January 13, 2018
Bowlers did their job, which is to take 20 wickets.
Batsmen failed.
Will India win any of the remaining two Tests?#SAvInd
— Bharath Seervi (@SeerviBharath) January 8, 2018
"Perception isn't the truth but it's bigger than truth these days" And may be that's why Bhuvi isn't a part of playing 11. #IndvSAonSonyTen3
— R P Singh रुद्र प्रताप सिंह (@rpsingh) January 13, 2018
Bhuvneshwar Kumar dropped, means Jasprit Bumrah takes the new ball. Not only was Bhuvi India's best bowler in Cape Town, he also lasted longer at the crease than ANYONE else: 127 balls: #SAvIND
— Anand Vasu (@anandvasu) January 13, 2018
Bhuvi’s form comes with ‘conditions apply’. Since the pitch is expected to offer more bounce than lateral movement…therefore, Ishant plays. #SAvsIND
— Aakash Chopra (@cricketaakash) January 13, 2018
"Ishant replaces Bhuvi for some extra bounce" ~ Kohli
Bhuvi in Last test : Best bowler for India (Took 6 wickets in the last test, 2 more than next best). Faced 127 deliveries while batting (Most by an Indian), and got out just once.
Kohli claims to pick XI on 'form'. #SAvIND
— Aditya (@forwardshortleg) January 13, 2018
#Bhuvi bats better than u when the ball swings da #Kohli
— AKSHAY (@akshay14793) January 13, 2018
Why is Smith called brain-fade when kohli proves he is a brainfaden with his selections. We were in the game due to bhuvi. Ask duplessis will he drop philander. He is slow too.. #SAvIND
— Simple (@Mohali_Monster) January 13, 2018
Thread for Test 2, day one: A very puzzled thread, that is. Saha gets a convenient niggle. Bhuvi, who got you in the game at Newlands, is out. KL for Dhawan is the only call that makes sense. And? Rahane remains out. Oh well. Pig-headedness is *not* a virtue.
— Prem Panicker (@prempanicker) January 13, 2018
Unconfirmed reports that Bhuvi failed to lift 470 kg in gym last night. Captain Fitness & team management couldn't take the risk in case of a rhino attack on the field. Sensible.
— A/S 😷 (@slicesofIife) January 13, 2018
https://twitter.com/Nibrazcricket/status/952089841642213376
Bhuvi not in the team?!!! My office is open for explanations.
— Gaurav Kapur (@gauravkapur) January 13, 2018
Can't believe Bhuvi has been dropped. Horses for courses approach of going with Ishant? But dropping the bowler who opened out the game for you in the 1st test & also looked rock solid with the bat in the lower order? Sathyama Kohli ah purinjikave mudila. #IndvsSA
— Mama | 360° Sports Entertainment (@SriniMama16) January 13, 2018
First Flat track, white ball bully over Rahane, now pedestrian Ishant over the best bowler of all formats in India right now, Bhuvi.
That's what happen when ego & arrogance took over a person#SAvIND— Sayan (@Tweets_by_Sayan) January 13, 2018
Three wrong answers from Virat Kohli today –
1. Rohit or Rahane? Rohit. ✘
2. Ishant or Bhuvi? Ishant. ✘
3. Heads or Tails. Heads. ✘— Ramesh Srivats (@rameshsrivats) January 13, 2018
When you drop your best bowler for Ishant Sharma's extra bounce. #Bhuvi #SAvsIND pic.twitter.com/29RZB3lxie
— Dileep Krishna (@benigntumour) January 13, 2018
https://twitter.com/IndianWriterV/status/952088231507517440
Possible selection meeting conv:
Kohli: Saha took lots of catches.
Shastri: Drop him.
Kohli: Bhuvi too quite a few wickets.
Shastri: Drop him.
Kohli: Rohit didn’t make much runs.
Shastri: Embrace him. Are we done? Drink time now? #RSAvIND— Mohan Krishnamoorthy (@mohank) January 13, 2018
Rahane continues to be out of the playing XI. Meanwhile, Parthiv Patel has replaced Wriddhiman Saha, the man who got the 10 dismissal records, in the previous Test. Saha apparently is down with a hamstring niggle.
Do remember that a wicket keeper scoring 20-30 more has to be balanced against a missed opportunity than can cost 70-80…… Unless Saha is injured, not even worth contemplating a replacement.
— Harsha Bhogle (@bhogleharsha) January 13, 2018
India, the No.1 Test side, are trailing 0-1 in the 3-Test series.
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.