New Zealand tour of India
223

India vs New Zealand: Why Did Parthiv Patel Choose KL Rahul Over Sarfaraz Khan?

India’s former wicket-keeper Parthiv Patel has made a surprising revelation regarding the second Test match against New Zealand in Pune. He suggested that the Indian team might opt for KL Rahul over Sarfaraz Khan, despite Khan’s impressive century, raising eyebrows among fans and cricket analysts alike.

Parthiv Patel has suggested that the Indian team may prefer KL Rahul over Sarfaraz Khan.
Image: Parthiv Patel has suggested that the Indian team may prefer KL Rahul over Sarfaraz Khan / © The JBT

After losing the first Test match against New Zealand by 8 wickets at M. Chinnaswamy Stadium in Bengaluru, the Indian team may consider changes to their playing XI. In this context, former wicket-keeper Parthiv Patel suggested that the team might favour KL Rahul over Sarfaraz Khan, despite Khan’s impressive second-innings score of 150 off 195 balls. This decision could significantly impact India’s strategy for the upcoming match.

KL Rahul struggled in the match, managing only 12 runs, prompting the team management to seek a better performance from him in the next game. With Shubman Gill likely returning, KL Rahul could replace Sarfaraz Khan in the lineup. The Indian team hopes to strengthen their batting order for the upcoming match.

Parthiv Patel Keeps KL Rahul over Sarfaraz Khan

In the statement given by Parthiv Patel, he has said that the Indian team should show faith in KL Rahul who is an amazing batsman for the team. He said:

“The question will be whether Sarfaraz Khan will get to play or they will go with KL Rahul. I will still play KL Rahul, the way the team has shown faith in him. I am thinking like that based on how the team’s thinking has been.”

The Indian team management faces a crucial decision ahead of the upcoming Test match. As the Pune Test looms, it’s a must-win situation for India and it will be interesting to see whom they choose to include in the lineup.

Comments

Thank you! We’re reviewing your comment.
We were unable to post your comment. Please, try again.