views : 725
3 Min Read
Star India captain Rohit Sharma made the decision to feature in the ongoing Ranji Trophy, representing Mumbai, following a disappointing run in the longest format of the game. After playing three out of five Tests in the Border-Gavaskar Trophy 2024-25, Rohit’s performances were far from his usual high standards. Despite being one of the senior-most players in the Indian team, he failed to make a significant impact in the series, failing to register a noteworthy score across the Tests. This lean patch with the bat prompted the Indian skipper to return to domestic cricket and seek some form ahead of the international fixtures.
In Mumbai's Ranji Trophy clash against Jammu & Kashmir at the BKC Ground in Mumbai, Rohit opened the innings alongside the promising Yashasvi Jaiswal. However, Rohit's struggle continued as he managed to face just 19 deliveries before being dismissed for a meager score of three runs. His brief stay at the crease failed to make a positive impact, further adding to the pressure he faces. Despite his undeniable experience and leadership role in the national team, Rohit's lean form will be a concern for both him and the Indian team management as they look ahead to important international assignments.
Nah man, this is embarrassing 😠pic.twitter.com/4TTdRJAyBW
— Naeem (@NaeemCaptionn) January 23, 2025
Rohit Sharma’s ongoing struggles with the bat have raised growing concerns ahead of the upcoming Champions Trophy 2025. After a string of disappointing performances in the Border-Gavaskar Trophy 2024-25, where he failed to make a significant impact in three of the five Tests, the Indian skipper’s lean patch continues. His underwhelming form in the longest format has left fans increasingly worried, especially with India’s crucial international fixtures looming.
In Mumbai’s Ranji Trophy clash against Jammu & Kashmir at the BKC Ground, Rohit’s frustrations persisted as he was dismissed for just three runs after facing only 19 deliveries. Adding to Mumbai’s early woes was young star Yashasvi Jaiswal, who also failed to capitalize on his opportunity. Jaiswal faced just eight deliveries, scoring a mere four runs before his departure. As a result, Mumbai’s top-order struggles put them on the back foot early in the game, failing to provide the team with a solid foundation. With both Rohit and Jaiswal falling cheaply, Mumbai’s start to the match against Jammu & Kashmir was far from ideal, raising questions about the form of two key players ahead of a crucial season for Indian cricket.
The clash between Mumbai and Jammu & Kashmir saw Mumbai batting first, but they struggled to put up a competitive total. After the early dismissals of Yashasvi Jaiswal and Rohit Sharma, Mumbai's middle order also faltered under pressure. Hardik Tamore could only manage seven runs, while skipper Ajinkya Rahane was dismissed for a modest 12. Shreyas Iyer added 11 runs to the tally, but Shivam Dube failed to make an impact, departing for a duck.
By the 20th over, Mumbai found themselves in deep trouble, having been restricted to just 71 runs with the loss of seven wickets. Jammu & Kashmir’s bowlers put in a disciplined performance, consistently tightening the noose around Mumbai’s batting line-up. The lower order, led by experienced players, now had the responsibility to steady the ship and give Mumbai a respectable total to defend. The situation was dire, with Mumbai’s top and middle-order batters failing to make any significant contributions. As the game progresses, Mumbai’s lower-order will have to step up and deliver if they hope to recover from this precarious position and set a challenging target for Jammu & Kashmir.