HomeNewsAustralia hammer Pakistan to set 354-run target at Sydney in 4th ODI
Australia hammer Pakistan to set 354-run target at Sydney in 4th ODI
David Warner smacked his 12th ODI century marking a successful day for the Australian batsmen, as the hosts put up a daunting 354–run target against a hapless Pakistan.
David Warner smacked his 12th ODI century marking a successful day for the Australian batsmen, as the hosts put up a daunting 354–run target against a hapless Pakistan, on Sunday, in the fourth ODI. Warner, who had smashed only the fifth century inside the first session on Day One of a Test at Sydney Cricket Ground (SCG) earlier this month, continued plundering runs at ease against the visitors. Warner scored a quickfire 130 at the top, and half-centuries from Glenn Maxwell and Travis Head helped Australia breach the 300-run mark for the first time in the series. On their part, Pakistan remained poor in the field, with several misfields and as many as four dropped catches.
Warner was severe against the Pakistani fast bowlers, who for the first time in the series, got their line and lengths wrong. So far, the pair of Mohammad Aamer and Junaid Khan had managed to keep the Australian openers quiet but Warner ensured to change the trend. He smacked boundaries at will to take Australia past the 50-run total within no time, with him reaching late 30s off just 18 odd balls with 5 boundaries and 1 six.
On the other hand, Usman Khawaja continued to misfire. He opened the innings along with Warner once again, and was happy to play the second fiddle, looking to rotate the strike. In ideal batting conditions, Khawaja was expected to play a long innings and put a disappointing run behind him, but it was not meant to be. In the 18th over, he chased one outside off and gave a simple catch behind the wickets, being dismissed for 49-ball 30 with 2 boundaries.
However, Warner was in full flow by then. He had an ordinary start to the ODI series, but had shown some form in the third ODI scoring a brisk 35. Pakistan bowled in the areas Warner would have liked to score off. He started off by punching boundaries on the off side, and despite having a lull in the middle, ended up scoring a brisk 119-ball 130 with 11 boundaries and 2 sixes.
Interestingly, Warner’s century on Sunday was slower than the hundred which he plundered against Pakistan at the Sydney Cricket Ground (SCG) in the New Year’s Test, which happens to be only the fifth occasion of a batsman scoring a ton before lunch break on the first day.
Khawaja’s dismissal brought Steven Smith at the crease. Smith began with a boundary, and batted fluently till he missed one that angled into him by Hasan Ali. The ball crashed into his wickets in front of middle and leg, and the umpire ruled the decision in favour of the bowler. Smith reviewed, but the ball was clipping the bails on its way.
Smith scored 48-ball 49 with 5 boundaries, but he too remained the second fiddle as Warner took centerstage. The two batsmen added 120 runs for the second wicket off 18.1 overs.
Towards the end, half-centuries from Head and Maxwell bolstered Australia. The two batsmen added exactly 100 runs in just a little more than 10 overs, taking Australia close to the 350-run mark. Both Head and Maxwell made merry against Pakistan, who continued to spill catches and field poorly.
Head scored 51 off 36 balls, hitting 4 sixes and 2 boundaries in the process. On the other hand, Maxwell made 78 off 44 balls with 10 boundaries and 1 six.
For Pakistan, Hasan Ali was the pick among the bowlers as he claimed 5 for 52 off his 10 overs. However, two dropped catches from Hasan took the sheen off his efforts with the ball.
Brief scores:
Australia 353 for 6 in 50 overs (David Warner 130, Steven Smith 49, Travis Head 51, Glenn Maxell 78; Hasan Ali 5 for 52) vs Pakistan
This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Strictly Necessary Cookies
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
If you disable this cookie, we will not be able to save your preferences. This means that every time you visit this website you will need to enable or disable cookies again.