Sports

Ishan Kishan Explains Virat Kohli's Generous Act For Batting Ahead Of Former-IND Skipper In 2nd Test

Wicketkeeper-batter Ishan Kishan has revealed the reason behind India's plan to send him ahead of Virat Kohli in their second innings.

India's wicketkeeper-batter Ishan Kishan.
info_icon

The Indian team came out in the second innings with 'all-guns blazing' as they brought their own version of 'Bazball' in the second Test against the West Indies. (More Cricket news)

The opening pair of Yashasvi Jaiswal and Rohit Sharma put on a 98-run stand in mere 71 deliveries with the latter scoring the fastest Test fifty ever. However, post the duo's dismissals, many thought it was Virat Kohli who would walk in a carry on the momentum for the vistors. But surprisingly, it was Ishan Kisham who walked out at number four. In the post-match interview, the wicketkeeper-batter explained as to why he walked out to bat ahead of Kohli.

Ishan Kishan managed to score a blistering 34-ball 52, his maiden half-century in Tests, before Team India declared their second innings at 181 for two.

"It was really special (the half-century). I knew what the team needed from me. Everyone backed me. Virat backed me and told me 'go and play your game'. Let us hope we will finish the game tomorrow. It was Virat bhai who took the initiative and told me that I should go in. There was a slow left-armer who was bowling. It was a good call for the team. Sometimes you need to take these calls," said Kishan after the day's play.

"We had the plan that we will play 10-12 overs after the rain break and score 70-80 runs. We wanted a 370-380 target," he added.

Thanks to the Indian batters' blitzkrieg, West Indies are set a target of 365 runs, who eventually closed Day 4 at 76 for two, with R Ashwin picking both the wickets. Kraigg Braithwaite's men still require 289 runs to win the second Test.

Important: We are happy to announce that we have successfully completed the migration of our site @outlookindia.com to enhance your experience as valuable user. But due to the scale of operations some data discrepancies may arise. We apologize for any inconvenience and thank you for your patience and understanding during this period.
Advertisement
Advertisement
Advertisement
Advertisement
Advertisement