Australia’s late declaration on Saturday, the fourth day of the fourth Ashes Test, left many confused, especially with rain forecast on day five in Sydney.

After taking a 122-run lead in the first innings, Australia were expected to score quick runs and get England to bat again on day four in the fourth Test match. A forecast of showers on Sunday, the fifth day of the match, had fans and experts guessing that the hosts would look to declare early, and have England bat for the majority of day four.

It was not to be, as Australia batted for a total of 68.5 overs on Saturday scoring 265-6, leaving the visitors to see off only 11 overs in the end of the day. England were set a target of 388 runs, seemingly a tall ask for a side who have yet to reach 300 in the series so far.

The visitors batted through the 11 overs for 30 runs, most importantly, without losing a wicket, which further left many puzzled at the timing of the declaration.

Cannot grasp why we batted past drinks?
Cost Green his wicket & put Carey on a hiding to nothing.
Too often ‘team sacrifices’ like that are forgotten later when stats are sprouted & compared, teams are selected & players dropped.#Confused #Ashes

— Nathan Adcock (@nathan_adcock22) January 8, 2022

Lovely from Khawaja, but not quite sure why Australia haven’t declared.

— Lawrence Booth (@the_topspin) January 8, 2022

AUS have 113 overs to bowl ENG out in Sydney
It took them 113.1 overs to do it in Adelaide

#AUSvENG

— Swamp (@sirswampthing) January 8, 2022

Why is Australia batting on?

— Rick Eyre on cricket (@rickeyrecricket) January 8, 2022

I guess Australia are still batting because Mark Wood is still bowling#Ashes

— Ben Gardner (@Ben_Wisden) January 8, 2022

Not having a pop for having a pop’s sake, but too much sentimentality. Understand waiting for Green’s 50 (confidence, etc.). But Aus shudda declared. No realistic Eng chase, considering injuries. Just waiting for Khawaja’s 2nd 100; every over bowled = 1 less Eng to face. #ashes

— Isabelle Westbury (@izzywestbury) January 8, 2022

Some, though, felt that the declaration was not ill-timed.

Sheesh, the declaration was fine. There’s no guarantee of winning depending on when you declare. If you can’t bowl them out in 110 overs then well played England. #Ashes

— Andrew Faulkner (@AndrewFaulkner9) January 8, 2022

Some cheekily stated that Pat Cummins timed his declaration to perfection, to Jack Leach from picking up a hattrick.

Australia declare, denying Jack Leach a hat-trick ball! Ollie Pope takes his fourth catch, equalling the record for a sub fielder! England have about 50 mins to bat tonight.

— Will Macpherson (@willis_macp) January 8, 2022

A very alpha move there from Cummins to declare with Leach on a hat-trick. #Ashes

— Alex Fair (@AJFair85) January 8, 2022

Bold move from Pat Cummins to declare and deny Jack Leach a chance at a hat-trick, but just one more example of how Australia’s been a step ahead, and more… #Ashes

— Matt Digby (@DigbyMatt) January 8, 2022

Spare a thought for Jack Leach. Left stranded on a hattrick and on the cusp of a hard fought 5 wicket haul as Australia declare 😭 #Ashes

— Aatif Nawaz (@AatifNawaz) January 8, 2022

Sign up to bet365 to be entered into a draw for the chance to win a Wisden t-shirt of your choice, terms and conditions apply, more information here 18+ begambleaware.org