
David Warner and Chris Rogers took to the bowlers from the word go and scored at more than six-an-over in the early stages. Youngster Lokesh Rahul dropped Rogers off Muhammad Shami in the eighth over at slip with the score at 46-0.
The mistake would prove to be costly as the opening pair would go on to make 200 at almost five-an-over before Warner slashed at a Ravi Ashwin delivery too close to cut and ended up slicing it to Murali Vijay to give India their first wicket. Warner’s 101 came off just 114 balls and included 16 boundaries.
Despite the strong start, the centurion feels Australia still need to do a lot to win, with the pitch offering little for the bowlers. “There was no swing, there was no sideways movement at all, so it was quite challenging for the bowlers,” he said. “It’s going to be
challenging for us as well.”
Rogers was desperately unlucky to miss out on a century as he played the ball on in the next over on 95.
With skipper Steven Smith and Shane Watson having played only one ball between them when the two came together, India sensed a way back into the match with the prospect of some quick wickets.
However, the two picked up from where the openers had left off and put together an unbeaten 144-run stand, albeit at a much slower pace, to ensure that winning his first Test as permanent captain is a distinct improbability for Kohli.
Ashwin then dropped Watson in the final over of the day to cap off a dismal day in the field for India.
“It was a very tough day. It’s very important that we pick ourselves up and try to be as fresh as possible tomorrow,” said Ashwin. “If we can keep them down [to a reasonable score] we can get back into it.”
Australia are also on course to cross the 500-run mark in the first innings for the fourth consecutive time in the series.
Published in The Express Tribune, January 7th, 2015.
Like Sports on Facebook, follow @ETribuneSports on Twitter to stay informed and join in the conversation.
COMMENTS
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ