Michael Neser removed Will Jacks for a hard-fought 41 after Steve Smith’s one-handed catch in the ongoing Ashes Test, breaking England’s 96-run partnership.
In the ongoing Ashes 2025 Test at Gabba, Michael Neser removed Will Jacks for 41 off 92 balls on Day 4, thanks to a sharp low catch from Steve Smith at first slip. The wicket ended an important 96-run stand for the seventh wicket. This has left England at 224/7, holding a narrow 47-run lead.
Smith reacted swiftly to a late-moving delivery, diving to his left to complete the one-handed catch cleanly. The third umpire confirmed the catch and the stand came to an end.
Neser is continuing his strong spell, completing figures of 3/36 in 13.1 overs. With Jacks gone, Ben Stokes now needs support from the lower order to increase the lead.
NO WAY! NO WAY STEVE SMITH! WOW!#Ashes | #PlayoftheDay | @nrmainsurance pic.twitter.com/4ziSJChGd4
— cricket.com.au (@cricketcomau) December 7, 2025
Interestingly, on Day 2, Will Jacks had taken a running catch to dismiss Steve Smith for 61. Brydon Carse tested Smith with a short ball, leading to a top edge toward backward square leg. Jacks sprinted across from fine leg and dived to complete a brilliant catch.
READ ALSO | Pat Cummins Confirms Comeback for Third Ashes Test in Adelaide
England’s Batting Crumbles on Day 4
In the match, England entered the post-tea session in serious trouble, despite a patient 148-ball fifty from Ben Stokes. Australia maintained full control when Steve Smith pulled off a sharp one-handed catch. Soon after, Brendan Doggett removed Gus Atkinson for 3 off 13. England had reached tea at 193/6 with a narrow 16-run lead.
Earlier on Day 3, England began strongly with 45 in the first six overs. However, for Australia, Scott Boland struck immediately after dinner and Michael Neser removed Zak Crawley and Ollie Pope in quick succession. Joe Root, Harry Brook and Jamie Smith also fell during a chaotic session.
This article follows WicketWatcher’s editorial standards. Learn more in our Editorial Policy or report an issue via our Corrections Policy.