Josh Hazlewood became the ninth Australian to reach 300 Test wickets, doing it by dismissing Mehidy Hasan in Darwin during the 1st Test against Bangladesh at Marrara Oval. Worth noting: the milestone arrived at 35 years old, with Hazlewood carrying 299 wickets into the match and finishing the innings with 6-89 as Bangladesh were bowled out.
Jose Hazlewood becomes ninth Australian to 300 Test wickets in 2026
Turning point in Darwin: how Hazlewood got to 300
The 1st Test began on 2026-08-13 in Darwin, and Hazlewood’s landmark fell in the match’s bowling rhythm—he took his 300th wicket when he dismissed Mehidy Hasan. That wicket also extended his personal Test impact: the milestone was recorded alongside a 14th career five-wicket haul in Tests, underscoring that this wasn’t a one-off entry into the club. Cricket.com.au highlighted that Hazlewood had been playing his first Test in a year, having missed the entire Ashes with injury, which adds extra weight to the “timing” of this achievement.
Worth noting: for Australia, the wicket count isn’t just history—it’s a present-day strategic asset. One pre-match report flagged that Australia’s bowling quartet could become the first team to field four bowlers in one XI with at least 300 Test wickets each, a rare lineage that speaks to selection continuity and long-cycle performance.
The number that matters: 299 to 300—and what it means
Hazlewood’s run-up matters because it shows how cleanly the milestone sat inside his long-form output. He had taken 299 Test wickets before this match, and a key pre-match report listed his record entering the Test as 76 matches and 299 wickets at an average of 24.21. Those figures are a useful baseline for India fans watching the Australian bowling machine: steady averages at scale are what differentiate a strike bowler from a one-series wonder.
That said, numbers alone don’t show the match pressure. In the later match report, Hazlewood was credited with 6-89 while Mitchell Starc took 2-79, and Bangladesh were bowled out—so the milestone didn’t just land; it translated into an innings shape. Here’s the thing: when a bowler reaches 300 with a six-for, it changes the way the batting unit calculates risk. It’s no longer “survive the old man”; it becomes “survive the spell that’s delivering control.”
For context beyond Tests, Hazlewood’s broader international record was listed as 232 games and 516 wickets, which helps explain why selection and workload management have been central themes across his career. The skills are there; what the body decides is when—and Hazlewood’s return after Ashes absence made the milestone feel earned rather than automatic.
Momentum and match context: why this wicket altered the contest
Hazlewood’s 300th wicket wasn’t separated from the contest; it sat at the centre of an innings where Australia’s attack tightened. The dismissal of Mehidy Hasan in Darwin came within the 1st Test framework, and the later report’s bowling figures—Hazlewood 6-89 and Starc 2-79—show Australia distributing breakthroughs while keeping the innings under pressure. That’s exactly how wicket milestones should be judged: not by the “calendar moment,” but by how the bowler shaped the outcome.
Worth noting for rivalry-minded viewers: when such milestones happen in home Tests, they often sharpen the next series conversations with India—because India’s batters will face this kind of bowling threat blueprint soon after. If you want a quick comparison of the key confirmed milestones and figures around the landmark, here’s the data in one place:
| Milestone / Metric | Confirmed figure |
|---|---|
| Hazlewood’s club entry | 300th Test wicket |
| Wicket for the milestone | Dismissed Mehidy Hasan |
| Age at milestone | 35 years |
| Career five-wicket milestone | 14th Test five-for |
| Match impact in innings | Finished with 6-89 |
Verdict: what Hazlewood’s 300 means for Australia now
This is the kind of milestone that doesn’t just decorate a career—it reframes a team’s bowling identity. Hazlewood reached the ninth Australian position with a landmark wicket in Darwin, did it at 35, and backed it with 6-89 in an innings where Bangladesh were dismissed. Cricket.com.au’s note that he returned for his first Test in a year after missing the Ashes due to injury makes this feel like resilience, not luck.
For Australia, the bigger implication is depth-of-experience. If the pre-match expectation about Australia’s quartet (four bowlers with 300+ Test wickets each) played out as flagged, then selection debates become about balance rather than “who can take wickets.” For opponents, that means the catch is simple: you don’t just plan for one bowler—you plan for a unit with sustained wicket potential.
If Hazlewood’s milestone reminds any team of one thing, it’s this: long-career control still wins Tests—especially when it arrives in the middle overs and arrives with five-for intent.
Related Articles
- India and Pakistan: Four Critical Questions Defining Cricket’s Most Intense Rivalry
- Decoding the Intense Historical Rivalry Between Australia and India Cricket Teams
- Four Questions That Define Cricket’s Fiercest Modern Rivalry
FAQs
How did Hazlewood become the ninth Australian with 300 Test wickets?
He reached 300 by dismissing Mehidy Hasan in the 1st Test vs Bangladesh at Marrara Oval, Darwin, during the match that began 2026-08-13.
What age was Hazlewood when he took his 300th Test wicket?
He was 35 when he took the milestone wicket.
Did Hazlewood’s 300th wicket come with a five-wicket haul?
Yes—his 300th wicket also meant it was his 14th Test five-wicket haul.
What were Hazlewood’s figures in the innings where the milestone featured?
In the later match report, Hazlewood finished the innings with 6-89, with Mitchell Starc also contributing (2-79) as Bangladesh were bowled out.
Why does this milestone matter for rivalry matchups involving India?
Because it reinforces that Australia’s wicket-taking threat isn’t dependent on one bowler—especially if the attack includes multiple 300+ Test wicket bowlers in the same XI, changing how batters pace their innings against Australia.
Was this article helpful?
Your feedback directly improves future articles on this site.





