Test
161

IND vs AUS: Mohammed Siraj takes up Rohit Sharma’s role during India vs Australia Prime Minister’s XI

After rain cancelled the first day, the pink-ball practice match between India and Australia Prime Minister's XI became a 46 overs a side game. India's captain Rohit Sharma, chose to bowl after winning the toss, with Mohammed Siraj opening the game using the pink ball.

Mohammed Siraj opened the practice match between India and Australia in place of Rohit Sharma.
Image: Mohammed Siraj opened the practice match between India and Australia in place of Rohit Sharma / © The Cricket Lounge

As Siraj prepared to bowl the first delivery, Matt Renshaw, who was facing, stepped out of his stance. He had been distracted by security personnel standing near the sight screen. At the other end, Sam Konstas was ready to face the next delivery.

After the distraction, Renshaw apologized to Siraj, pointing out the issue near the right-sight screen that had caused the delay. Visibly frustrated Siraj gestured toward the sight screen and made a remark. His comment humorously referenced a popular one-liner from Rohit Sharma during India’s home Test series against England earlier in the year. He said:

Oh bhai garden mai ghoom raha hai kya (Brother are you roaming around a garden)?

In India’s shortened pink-ball warm-up game against Prime Minister’s XI in Canberra on Sunday, Shubman Gill impressed with a classy fifty, putting to rest concerns about his thumb injury. Captain Rohit Sharma surprised everyone by batting at No.4. The Indian team showcased a strong performance, comfortably winning the match by six wickets.

Whether the Indian captain will open in the second Test against Australia, starting Friday in Adelaide remains uncertain. The warm-up game was 46 overs a side contest, with India successfully chasing a target of 241 in 42.5 overs. They continued batting till the final over. Australia’s Test hopeful, Sam Konstas, scored an impressive 107 off 97 balls, but his efforts went unrewarded.

Comments

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