Babar Returns, New Attack Arrives: Pakistan vs West Indies 1st Test Preview — Tarouba, July 25

 

Saturday morning in Tarouba, Trinidad. The Brian Lara Cricket Academy — a ground named after the greatest batter the Caribbean has produced, a man who made 400 not out in a Test match on this island and whose name hangs over every contest played here as both inspiration and standard. Pakistan arrive with a new captain, a new bowling attack, and the same old question that has followed them across every Test series outside Asia for the better part of three years: can they compete when the conditions do not assist their spinners, when the pitches move, and when their top order — so often the team's weakness away from home — is asked to perform under pressure?

The answer begins on Saturday. West Indies — who finished their ODI series against New Zealand just four days ago and must now shift entirely into Test mode — bring their own set of questions. Roston Chase, their captain, has been managing a finger injury that kept him out of the ODI series and has only recently been cleared to lead the side despite lingering swelling. The Brian Lara Academy surface is known to be sluggish and spin-friendly as the match progresses — which favours West Indies' spin resources but also raises questions about whether their pace bowlers can take enough wickets in the first two days to put Pakistan under genuine pressure before the pitch turns.

Two Tests. Two Caribbean venues. Crucial World Test Championship points at stake. And a Pakistan side under Babar Azam that has something to prove — both on the field and in the dressing room. Here is everything you need to know before the first ball.

Babar Azam's Return — and Why It Is More Complicated Than It Looks

The biggest story heading into this series is not the cricket. It is the captaincy. Pakistan arrives with renewed leadership after Babar Azam's return as Test captain. Shan Masood was removed after a run of poor results — Pakistan lost their last four Test series, including a home series to Bangladesh that was one of the most embarrassing results in Pakistan cricket history in recent years. The PCB, faced with a deteriorating Test record and limited options, went back to the man they had removed just over a year ago.

Babar's return to Test captaincy is a marriage of convenience — with few options on the table, the PCB has gone backwards in the hope that it will all work out. That framing, which comes from the people closest to the situation, tells you something important about the mood surrounding this appointment. It is not the triumphant return of a captain who left on a high and was begged back by a grateful board. It is a pragmatic decision made in difficult circumstances, with the hope that familiarity and authority will produce better results than the alternatives.

Babar himself has been measured about it. "My main focus is on discipline, fitness, and performance," he said on taking over. "It is important to understand where and why we have been struggling in Tests." That is an honest statement — and the fact that he leads with discipline and fitness before tactics and strategy tells you where he thinks the problems have been. Pakistan's Test record away from home in the last three years has been undermined not just by talent gaps but by preparation, attitude, and the kind of fractured team culture that surfaces when results go badly for an extended period.

The tour match at Port of Spain gave some encouragement. Babar and Awais Zafar both hit centuries, and Mohammad Ali bagged a five-wicket haul in Pakistan's practice match. Those are the right signals from the right players at the right time. Babar in form is a genuinely different proposition from Babar who is managing captaincy pressure alongside his own scoring concerns. And Mohammad Ali's five-for, on a surface that was not dramatically different from what they will face in Tarouba, is the kind of practice match performance that a bowling attack needs before a Test series begins.

Pakistan's New-Look Attack — and What It Means

The most interesting dimension of this Pakistan side is not the batting. It is the bowling — specifically, the fact that Pakistan have arrived in the Caribbean with an attack that looks genuinely different from anything they have fielded in the last two years.

Pakistan have shaken things up in their quest to remedy their recent poor Test record away from home. Meet Pakistan's new-look attack: Mohammad Ali, Aamer Jamal, and Ubaid Shah. Those three names represent a specific kind of seam-bowling philosophy — pace, movement, varying angles — that Pakistan have not consistently deployed in Test cricket since the brief but brilliant period when Shaheen Afridi, Haris Rauf, and Naseem Shah were all fit and available simultaneously.

Mohammad Ali is the most interesting of the three. He is not express pace — he operates between 135 and 142 kph — but he moves the ball both ways and hits the stumps consistently, which on Caribbean surfaces that offer early movement off the seam is more valuable than raw speed. His five-wicket haul in the tour game was built on seam movement rather than spin or pace, and if the Brian Lara Academy surface behaves as it typically does in late July, he should be effective from the first morning.

Aamer Jamal is the allround option — right-arm medium pace and a batting contribution at six or seven that gives Pakistan genuine depth. His bowling in the last two series he played was inconsistent but capable of genuine quality deliveries when conditions assisted him. Ubaid Shah — the youngest and quickest of the three — has the ability to generate bounce that West Indies' middle order will find uncomfortable on a slow surface where late bounce is the primary variable.

The spin question remains. Sajid Khan — the off-spinner who has taken wickets in difficult conditions — is the primary spin option. In a series where the pitch at Tarouba is expected to turn in the second innings and Port of Spain's Queen's Park Oval has historically been one of the more spin-friendly venues in the Caribbean, Sajid's role could be decisive. Pakistan have been inconsistent in their use of spin in away Tests, sometimes overbowling, sometimes underbowling — getting that balance right in a two-Test series where the margin for error is narrow will be one of Babar's most important tactical responsibilities.

Saud Shakeel's Absence — the Gap Nobody Has Filled

Saud Shakeel has been left out of the West Indies tour because of fitness issues, but Pakistan are expecting him to be back for the Tests in England. That single sentence is perhaps the most significant in Pakistan's pre-series team news — because Saud Shakeel at number five has been Pakistan's most reliable Test batter in away conditions over the last two years. His average of 47 in away Tests since 2024 is the kind of consistency that Pakistan's batting lineup desperately needs, and his absence from Tarouba and Port of Spain is a genuine loss.

Who fills the number five slot matters significantly on surfaces where the first three sessions tend to be the most difficult. Pakistan fans and analysts have debated whether Awais Zafar — who scored a century in the tour match — should come into the XI, and on the evidence of that performance the argument for including him is strong. But Zafar at Test level is an unknown quantity, and asking him to play the Saud Shakeel role in a WTC series away from home in his first or second Test appearance is a significant ask. The batting order question — who bats where, who plays, and who absorbs the pressure in the middle overs — may be the contest within the contest in the first two days of this series.

West Indies: Roston Chase and the Home Advantage Question

West Indies come into this Test series on the back of a 3-2 ODI series defeat to New Zealand — a result that was competitive but ultimately a loss on home soil, continuing a pattern of West Indies finding it difficult to convert home advantage into home victories in bilateral series. Chase returns as Test captain after missing the ODI series, and his own form — 52 Test innings, averaging 37 — is the backbone of West Indies' batting in the middle order.

Their pace attack for the Test series is more potent than what they fielded in the ODIs. West Indies' pace attack might be too much for Pakistan's batters — a view shared across several cricketing platforms in the lead-up — and on the Brian Lara Academy surface where early movement is available, Jayden Seales and Alzarri Joseph have the ability to expose Pakistan's top order before the conditions ease.

The spin resources become dangerous as the series progresses and the surfaces wear. Jomel Warrican — left-arm orthodox, 45 wickets in 18 Tests — is the most experienced spin option, and on turning Tarouba and Port of Spain surfaces in August, he will bowl long spells into the rough outside right-handers' off stump that will test Pakistan's middle order regardless of whether the batting order has been settled by that point.

The key match-up in this series — and one that will be played out across ten sessions in Tarouba before repeating itself at Port of Spain — is Babar Azam against the new ball. If Babar makes runs in the first session of both Tests, Pakistan have a platform. If Babar falls early, Pakistan's batting tends to fold from the top, and the new-look bowling attack is asked to restrict West Indies in conditions where a 250-run first-innings total can become a match-winning score.

The WTC Context — Why This Series Matters Beyond the Result

Pakistan currently sit in the lower half of the WTC standings — the consequences of a poor away record across the current cycle. West Indies are not dramatically better placed. For both sides, this two-Test series is a chance to accumulate points in a cycle where every match counts, and where two wins would significantly improve either side's position ahead of the final stages of the WTC cycle in 2027.

The broader context for Pakistan is even more significant. Saud Shakeel is expected to return for the Tests in England — which means Babar's first series back as captain sets the tone for a schedule that includes England, South Africa, and the Champions Trophy before the WTC cycle concludes. A series win in the Caribbean, with a new attack and a reorganised batting order, would give Pakistan momentum that the last year of poor results has completely stripped away.

The first ball in Tarouba on Saturday morning is not just the start of a two-Test series. It is the start of an attempt to rebuild Pakistani Test cricket's identity under a captain who left under difficult circumstances and has returned with something to prove. Whether this turns out to be a genuine new chapter or another short-term fix dressed up as structural change is the question that cricket in Pakistan — fans, selectors, and players alike — have been asking since Babar's name was put back on the captain's armband.

The answer begins on Saturday. In the Caribbean. At the ground named after the greatest batter who ever lived.

Do you think Babar Azam's return as Test captain is the right decision for Pakistan — or is it a short-term fix that avoids the deeper structural problems in Pakistan cricket? And can Pakistan's new-look pace attack of Mohammad Ali, Jamal, and Ubaid make an impact in Caribbean conditions? Drop your thoughts in the comments below.

Hetmyer's 69* Wins the Final, But New Zealand Take the Series 3-2 — A Complete Review

 

Kensington Oval, Bridgetown, Barbados. Monday evening. The series was already decided — New Zealand had won it 3-1 with their one-wicket thriller here on Saturday — but West Indies had promised themselves, and their supporters, that they would not let the final ODI of the series become a formality. They nearly did not. They nearly won. And in the end, with Shimron Hetmyer striking 69 not out from 64 balls and West Indies chasing 269 off the last ball, the result went to the home side — West Indies won the 5th ODI by 2 wickets with 15 balls to spare — in a match that was simultaneously a consolation and a statement.

New Zealand won the series 3-2. But the final scoreline flatters the visitors slightly. What actually happened across five matches in Providence and Bridgetown was a series that swung dramatically on conditions, individual performances, and moments — the kind of series that produces a Player of the Series winner who played for the losing team in the final match.

That winner was Jayden Lennox. The 19-year-old left-arm wrist spinner who had never played a senior professional match before his ODI debut in the second match of this series finished as Player of the Series with 14 wickets. In five matches. In his first five international appearances. That number — 14 wickets, more than any other bowler on either side — tells you almost everything you need to know about what this series was and why it will be remembered.

The 5th ODI: Hetmyer's Redemption, New Zealand's Final Stumble

New Zealand batted first in the series finale and posted 268 for 9 — a total that looked competitive on the Kensington Oval surface but was, as it turned out, about 20 runs below what the match required to be safe. Will Young made 67 from the top of the order — his best ODI score of the tour. Tom Latham contributed 52 in his characteristically patient style. But New Zealand's middle order failed to accelerate convincingly in the final fifteen overs, and Gudakesh Motie's left-arm spin — 1 for 32 from 9.4 overs — kept the scoring rate below what several of New Zealand's batters were capable of.

Matthew Fisher's 3 for 40 and Mitchell Santner's 2 for 36 had suggested in the 4th ODI that New Zealand's bowling was good enough to restrict West Indies below any target they set. The same attack, in the same conditions twenty-four hours later, did not produce the same result. The difference was Shimron Hetmyer.

Hetmyer had been brought into the West Indies side for the Bridgetown matches specifically because the Kensington Oval surfaces — flatter, faster, less spin-friendly than Providence — suited his style of batting: hard-hitting, front-foot, attacking any ball that was not full and straight. He made 27 in the 4th ODI. In the 5th, he batted through the innings from the moment West Indies were struggling at 134 for 5 in the 30th over — a position that would have meant defeat in most ODIs at this ground.

His partnership of 96 unbroken with Amir Jangoo, who made 51 from number seven, was the difference between West Indies winning and losing this match. Hetmyer's 69 not out came from 64 balls and included three sixes — one off Jacob Duffy in the 43rd over that cleared the boundary at long-on with a swing that suggested he had not been thinking about survival but about the gap between where the ball landed and the rope. He finished it with a six off the penultimate over that took West Indies past the target. The Kensington Oval stood for him. It was the kind of innings that a home crowd in a consolation match deserved — genuine quality in difficult circumstances against decent bowling.

The Series In Full: Five Matches, Five Stories

To understand what this series was, you have to understand what each match produced individually — because no two of the five matches were alike, and that variety is precisely what made the series worth watching from start to finish.

1st ODI, Providence (July 11): West Indies won by 7 wickets. India's debut spinners dominated — Vitel Lawes took 3 for 54 in his first professional match ever, triggering New Zealand's collapse from 234 for 4 to 267 all out. Carty made 95, Hope 87 not out. A one-wicket defeat in Barbados was West Indies' third loss in a row. This was their high point — dominant, tactical, everything working.

2nd ODI, Providence (July 13): New Zealand won by 5 wickets. Lennox struck again — 5 for 19, the third-best bowling figures by a New Zealand spinner in ODI history — and West Indies collapsed from 63 for 0 to 138 all out. New Zealand chased it with wobbles but won with 104 balls to spare. The series was level, and the narrative had been reset completely.

3rd ODI, Providence (July 16): New Zealand won by 6 wickets. Their most controlled performance of the series — the pitch was turning, Lennox and Santner shared eight wickets, and New Zealand's batting was precise without being spectacular. West Indies bowled out for 140. New Zealand cruised it in under 40 overs. At 2-1, New Zealand were in command.

4th ODI, Bridgetown (July 19): New Zealand won by 1 wicket. The series' defining match — played in Bridgetown on the same day the cricket world farewelled Sir Garry Sobers, whose Kensington Oval connection made the venue feel particularly loaded on that particular afternoon. West Indies made 188, Jangoo top-scoring with 51 and Motie contributing 41 late. New Zealand's chase collapsed from 149 for 5 to 149 for 9 as Motie took a five-wicket haul that was as good as any bowling performance of the series. Mitchell Santner, batting at number eight, made 34 not out from 56 balls — hitting every single run scored off the bat in the final push — to get New Zealand home by one wicket. The visitors just about held their nerve in a chase of 189 to take an unassailable 3-1 lead in the ODI series.

5th ODI, Bridgetown (July 21): West Indies won by 2 wickets. Hetmyer's 69 not out, Jangoo's 51. New Zealand 268 for 9, West Indies 269 for 8. A consolation win, yes — but a convincing statement that on Kensington Oval's flat, fast surface, West Indies' batting is capable of chasing anything when their best players are available and in form.

Jayden Lennox: The Series Within the Series

Fourteen wickets in five ODIs. In your first five senior professional appearances of any kind. At the age of 19. On surfaces — Providence's turning, stopping pitches — that were specifically prepared to assist exactly what Lennox does. Those qualifications matter. But they do not diminish what he achieved, because the qualification that counts most is that international batters — experienced, well-prepared, aware of what Lennox was doing — still could not consistently play him. His five-wicket haul in the 2nd ODI was the performance that defined the series. His contributions in the 3rd ODI confirmed it was not a one-off.

Player of the Series for the bowling side in a series the batting side ultimately lost 3-2 is a distinction that does not always happen — usually the series winner produces the player of the series winner. Here, Lennox won it for New Zealand despite West Indies winning the last match. That tells you how dominant his bowling was across the first three games.

As we covered in detail in our full report on the first ODI and our second ODI match report, the emergence of young spinners on both sides — Lennox for New Zealand, Vitel Lawes for West Indies — was the defining storyline of a series that could have been unremarkable. Instead it produced two debut performances of genuine quality, a one-wicket thriller, and a final match that went to the last over. For a five-match ODI series between two teams neither of whom is currently in the top three of the WTC or ODI rankings, that is an exceptional return.

West Indies: Where Does This Leave Them?

West Indies lost the series 3-2 — but the manner of that loss contains as much encouragement as discouragement, which is not a verdict you can reach on every series result. Their 5th ODI win showed that on Kensington Oval in July, against a quality New Zealand side, they can chase 269 and win. Hetmyer at six, Jangoo at seven — a lower-middle order that can contribute 96 unbroken in a chase when everything above it has failed — is genuine batting depth.

The concerns are equally clear. West Indies' top order — Hope, Campbell, Auguste, Carty — produced one fifty-plus partnership across the four completed innings in Providence. On the spinning surfaces that Providence's groundstaff prepared, their batters looked uncertain against sharp turn in a way that suggests the home pitch conditions may have been as uncomfortable for West Indies as for New Zealand. That is a problem. If you cannot bat comfortably on your own pitch, you cannot consistently win at home.

Shai Hope's captaincy has been thoughtful throughout — his tactical decisions in the field have generally been correct, and his batting has provided the anchor role that West Indies need. But as Amir Jangoo put it after the 4th ODI defeat — "a difficult pill to swallow" — the series leaves West Indies knowing they were competitive without being consistently good enough. The difference between those two things is what the World Cup qualification pathway in 2027 will expose if it is not addressed.

New Zealand: Santner's Legacy

Mitchell Santner's series as captain deserves a specific mention beyond the result. He won a series in the Caribbean — always difficult — with a team that had travel-weary players coming off the back of a historic Test series win in England. He managed Lennox correctly — not overbowling him, protecting him when conditions were easy, using him aggressively when the pitch was doing something. He batted number eight and made match-winning contributions twice. And he delivered the post-match comments of a captain who is entirely comfortable with the decisions he made, whether they worked or not.

New Zealand are currently the most complete white-ball ODI side outside India and England. Their depth — Latham, Young, Chapman, Mitchell, Santner, Bracewell, Fisher, Duffy, Lennox — covers batting, pace, allround, and spin without obvious weaknesses. The World Cup in South Africa in 2027 is still eighteen months away. New Zealand will be there. And if Lennox is still developing at the rate he showed in this series, they will arrive with a bowling attack that nobody has yet found a reliable answer to. That, on the evidence of five matches in Providence and Bridgetown, is a terrifying prospect for every team in the tournament.

Do you think Jayden Lennox can sustain this level across different surfaces and conditions — or was Providence specifically designed to produce exactly this kind of spell? And does West Indies' 5th ODI win give you optimism or pessimism about their World Cup chances in 2027? Drop your thoughts in the comments below.

Cummins, Hazlewood, Lyon Return: Australia Name Full-Strength Squad for Bangladesh — But the Real Story Is What Comes After

 

For the first time in almost exactly a year, Australia's Test team looks like Australia's Test team. Pat Cummins is back. Josh Hazlewood is back. Nathan Lyon is back. Mitchell Starc never went anywhere. And the 13-man squad named on Tuesday for the two-Test series against Bangladesh — in Darwin on August 13-17 and Mackay on August 22-26 — is the clearest signal yet that Australia are preparing for what selector George Bailey described as "at least 20 Tests over the next 11 months." Bangladesh are the first hurdle. South Africa, India, and the Ashes in England are what follow. The squad announced today is not built for Bangladesh. It is built for everything that comes after.

That context is essential to understanding both the selection and the selection dilemmas it creates. When you are about to play 20 Tests in 11 months across three continents — beginning in the Northern Territory humidity of Darwin and ending at Lord's in the English summer of 2027 — the two Tests against Bangladesh in August become less about the result and more about getting your best players match-ready before the campaign that actually defines the year begins. Australia are currently top of the World Test Championship standings. They want to stay there. And they cannot do that without Cummins, Hazlewood, and Lyon.

The Return of the Big Three — and What Their Injuries Cost

Cummins, Hazlewood and Lyon were all injured for Australia's last Test in Sydney in January — the fifth and final Ashes Test, which Australia won 4-1 to claim the series. The three absences meant that Michael Neser, Todd Murphy, and Brendan Doggett were all part of that Sydney squad, covering for players who had carried significant injury burdens across the series. Cummins had managed his workload carefully across the Ashes after a hamstring concern. Hazlewood has been plagued by recurring injuries for the better part of three years — hip, side strain, calf — and his availability is, candidly, never something Australia can fully plan around until he is in the nets bowling at full pace. Lyon's hamstring issue, which ended his Ashes series prematurely, was a concern that lingered into the first half of 2026.

All three are now fit. Selector George Bailey said Cummins, Hazlewood and Lyon had "worked extremely hard, individually and with the fitness teams, over the past few months to return from their respective injuries." The phrasing — "worked extremely hard" — is the diplomatic language of selectors who are aware that three of their most important players spent several months uncertain about their own availability and are now being asked to hold themselves together across a 20-Test schedule that will physically punish everyone involved.

Cummins is in line to play his first Test match since December last year. Seven months without a Test match for an Australian captain who averages 26 with the ball in the format is not ideal preparation for Bangladesh, South Africa, and India in sequence. The two Tests in Darwin and Mackay are not an inconvenience on the path to the serious series — they are a necessity, a chance for Cummins to rediscover his rhythm, Hazlewood to confirm his fitness at full pace, and Lyon to bowl 30 overs on turning Darwin pitches before he has to do it in Durban and Chennai.

The Khawaja Problem — And Why It Has Not Been Solved

Usman Khawaja retired from Test cricket after the Sydney Ashes Test in January — a retirement that was announced without drama and accepted with the gratitude that a batter of his consistency and longevity deserves. What it left, however, was a genuine problem that this squad does not fully resolve.

Khawaja was Australia's most reliable top-order batter for the last five years. In that period he averaged 56 in Tests, with centuries in England, India, Pakistan, and at home. The left-handed opening batter who could build an innings from nothing, absorb pressure in the first session, and then accelerate when conditions allowed is not a player type Australia has in obvious abundance. The selectors have not added a fresh batting face to the group — which tells you one of two things: either they believe the solution is already in the squad, or they have not yet found the solution and are buying time with Bangladesh before they need to commit.

Cameron Green and Beau Webster played together in Australia's last Test at Nos. 7 and 8 respectively and the duo look set to continue together with Green likely to move to No. 5 — the position vacated by Khawaja, which was previously Khawaja's slot in the order. Green at number five is a solution of sorts. He averages 35 in Tests — respectable for a middle-order batter, less convincing for the position that needs to anchor an innings when the top three have failed. He is also primarily a bowler who bats rather than a batter who bowls, which means his promotion to five changes the balance of the XI in ways that are not yet fully understood.

Jake Weatherald has been retained as opener and will continue his partnership with Travis Head. Weatherald averaged 22.33 in the Ashes — a figure that reflects the difficulty of opening against a high-quality England attack in English conditions, but also a figure that would concern any selector looking at a 20-Test schedule. He made one half-century in ten innings. Australia need more from their opening partnership than Head carrying it with fifties while Weatherald struggles to convert starts. Bangladesh in Darwin and Mackay is the chance for Weatherald to show that the Ashes numbers were an aberration rather than a baseline.

The Green-Webster Dilemma: Can Both Play?

The selection question that nobody in Australian cricket has yet properly answered is whether Cameron Green and Beau Webster can play in the same Test XI simultaneously — and if so, what the batting order looks like when they do.

Green at number five and Webster at number six or seven creates a middle order that contains two genuine allrounders, neither of whom is the specialist number five that Khawaja's retirement left vacant. The combined bowling quality they provide — Green's right-arm medium pace and Webster's right-arm medium pace and left-arm spin — is valuable, particularly in spin-friendly conditions. But in South Africa, where the ball moves and bounce is the primary weapon, having two batting allrounders ahead of Alex Carey may leave Australia's middle order exposed if the top three fall cheaply.

The more interesting sub-question is Webster's bowling. Webster has claimed eight wickets with the ball in Tests, and added strength to Australia's slip cordon — but his bowling has been a secondary asset rather than a primary selection reason. If Cummins, Starc, Hazlewood, and Lyon are all fit and available, Australia's bowling is arguably the deepest it has been since 2019. The question of whether Webster's batting alone justifies his place ahead of a specialist batter becomes more pressing when the bowling attack is this complete. Bailey acknowledged as much without saying it directly: "The volume of cricket and schedule across the next 12 months are likely to present further opportunities across all formats for many players."

Scott Boland: The Man Who Loses When Everyone Is Fit

The cruellest selection story in this squad is not the one about the player who was dropped. It is the one about the player who was retained but may not play. Scott Boland played all five Ashes Tests when Cummins, Hazlewood, and Lyon were either injured or managing workloads. He took wickets. He was consistently excellent. He is, by any objective measure, one of the ten best Test bowlers in the world — his record at the MCG and in home conditions is extraordinary, and his ability to hit a consistent length at medium pace makes him uniquely difficult to score from in Australian conditions.

Hazlewood's return will force a tough decision for selectors regarding Scott Boland who played all five Ashes Tests alongside the indefatigable Mitchell Starc. The likely XI in Darwin has five genuine bowlers — Cummins, Starc, Hazlewood, Lyon, and one of Green or Webster. Boland, despite his quality and despite his Ashes contribution, is the one who gets left out when the "big three" are available. Boland has typically been the fall guy when the 'big three' of Cummins, Starc and Hazlewood have all been available. That pattern holds here. It is not a slight on Boland. It is simply the consequence of being exceptionally good in a squad that contains three other exceptional pace bowlers who were unavailable and are now available again.

Bangladesh: What to Expect in Darwin and Mackay

This will be Bangladesh's first Test tour of Australia since 2003 — a 23-year absence that tells you something about the scheduling priorities of international cricket and the financial realities of bilateral tours. The pitches in Darwin and Mackay are not the flat, spin-friendly surfaces that Bangladesh's batting thrives on. Darwin's Marrara Stadium offers pace and carry in August — conditions that Cummins, Starc, and Hazlewood will exploit from the first session. Mackay's Great Barrier Reef Arena is a newer venue with less predictable surfaces, but the Northern Queensland conditions in August — warm, occasionally humid — tend to suit pace bowling in the first two days.

Bangladesh have improved considerably as a Test-playing nation over the last decade. Their series win in South Africa in 2025 was their first away series win against a top-eight nation. They have spinners — Mehidy Hasan Miraz, Shakib Al Hasan remains retired but Taijul Islam provides quality left-arm spin — who can be effective on surfaces that assist them. But Australian surfaces in August do not typically assist them. Bangladesh will need to bat at their very best to remain competitive, and their bowling will need to take 20 Australian wickets on pitches that offer everything the fast bowlers want.

Australia sit atop the World Test Championship standings, while Bangladesh are currently in fourth place. The WTC context adds extra significance — two wins for Australia in August extend their lead at the top of the standings going into the South Africa and India tours. Two wins for Bangladesh would be the greatest result in their Test history and would shift the WTC equation significantly. On paper, the former is overwhelmingly more likely. But Bangladesh have surprised before. And Cummins, Hazlewood, and Lyon — however fit they say they are — have not played Test cricket since January. Seven months of preparation does not always replicate seven overs on the first morning in Darwin when conditions are right and the ball is moving.

The Bigger Picture: 20 Tests in 11 Months

The Bangladesh series is the beginning. What follows it is the reason this squad matters beyond the two Tests themselves. The volume of cricket and schedule across the next 12 months — kicking off 12 months containing 20 test matches including tours of South Africa, India and England — is the most demanding Test schedule Australia has faced since the 2019-21 period. Managing Hazlewood's body across that schedule will be the single most important selection management challenge Bailey and Cummins face. If Hazlewood stays fit and bowls at his peak across the South Africa, India, and England tours, Australia are genuinely capable of winning all three series. If he breaks down again — as he has in six of the last eight bilateral Test series — Australia's pace attack loses the variety and quality that makes it so difficult to bat against.

Lyon's management is the secondary concern. At 38, he is approaching the stage of his career where the difference between a four-Test series and a five-Test series matters in terms of recovery time. Two Tests in Darwin and Mackay in August is manageable. Three Tests in South Africa in September is manageable. Five Tests in India in November is a different conversation. Australia will need to think carefully about how many overs they ask of Lyon before the series that matter most.

Bangladesh in August. South Africa in September. India in November. England in 2027. The 13 players named on Tuesday have been selected for all of it, not just the first chapter. That is the correct approach. Whether it produces the right results across 20 Tests in 11 months is the question that Australian cricket will be answering for the next year.

Do you think Cameron Green at number five is the right solution to Usman Khawaja's retirement — or does Australia need a specialist batter in that position before the India series? And is Scott Boland unlucky to be potentially left out despite playing all five Ashes Tests? Drop your thoughts in the comments below.

747 Runs at Lord's: Duckett 141, Rohit 138 — England Win the Series in a Classic

 

Lord's Cricket Ground has hosted 747 men's ODIs across its history. It has seen Viv Richards demolish attacks, Jonty Rhodes produce one of cricket's defining run-outs, and Kapil Dev hold the World Cup aloft in 1983. But on Sunday evening, it hosted something it has never seen before: England post 387 for 3 in an ODI — the highest List A score ever recorded at this ground — and India reply with 360 for 7 in a chase that came agonisingly close but ultimately fell 27 runs short. A combined 747 runs in a single ODI. At Lord's. In a series decider. On a day when Rohit Sharma and Virat Kohli played what may have been their final innings in English cricket. The ground that hosted the first cricket match in 1814 had never seen anything quite like it.

England won the series 2-1 — their first ODI series win against India since 2018, only their eighth overall in 22 attempts. The gap between those two statistics tells you how rare this result is. Harry Brook's team, which had swept the T20I series 4-0 and now completed the ODI series, has produced the most dominant white-ball tour of India that England has managed in a generation. And they did it at cricket's most storied ground, on cricket's most appropriate stage, in exactly the kind of match that the home of cricket deserves.

Match Highlights

Watch the full highlights — Duckett's 141, Rohit's farewell hundred, and the final over drama that settled the series:

Before a Ball Was Bowled: The Sobers Tribute

A minute's silence was observed before the toss — for Sir Garfield Sobers, who passed away earlier in the week at the age of 90. The greatest allrounder the sport has ever produced, a man who scored 8,032 Test runs and took 235 Test wickets across a 20-year career that redefined what was possible for a single cricketer. Lord's felt the weight of his passing, and the tribute — players from both sides standing in silence at the home of cricket — was exactly what the moment required. There is a poetry to the fact that cricket's greatest allrounder was farewelled at Lord's on a day when the sport produced one of its most extraordinary batting performances. Sir Garfield would have appreciated the cricket that followed.

England's Innings: Duckett's Masterpiece and the Lord's Record

Brook won the toss and batted. What followed in England's fifty overs was a batting performance of such sustained quality that the final score — 387 for 3 — almost undersells what was achieved. England did not post 387 by slogging from the first ball. They built it patiently in the powerplay, explosively in the middle overs, and clinically in the death. The architecture of the innings was as impressive as the total.

Ben Duckett and Jacob Bethell opened together, and their partnership of 189 for the first wicket — spanning 30.2 overs — was the foundation on which everything else was built. England's 387 for 3 is now the highest List A total at Lord's, and the platform for it was Duckett and Bethell's opening stand, which combined Bethell's timing through the covers with Duckett's relentless ability to find the boundary at will in any condition on any surface.

Bethell was the aggressor early — he was playing at 85 not out and incredibly close to his second ODI century when Prasidh Krishna finally got the breakthrough, a catch by Rohit Sharma dismissing Bethell at 91. Nine short of what would have been one of the great Lord's ODI centuries — but 91 from 93 balls in a series decider, with a bowling spell later of 1 for 49, earns him the Player of the Match award regardless. It was a complete performance.

Duckett continued after Bethell's dismissal with Root at the other end, and it was the Root-Duckett partnership that produced the innings' most sustained passage of quality. Root — who finished the series as Player of the Series with 249 runs, including his 99 not out in Cardiff — batted with the composure that has defined his entire white-ball contribution this summer. Duckett hits his fourth ODI century as England got closer to the 300-run mark, and Duckett and Root continued to drive England towards a mammoth target as Root approached his own half-century. Duckett was finally dismissed at 141 off a return catch from a Prince Yadav delivery.

141 from Duckett. 91 from Bethell. 74 not out from Root. 41 not out from Buttler in a brief but brutal cameo. England 387 for 3. The home dressing room's mood, as the players came off, was of a team that knew they had posted something that would test any batting lineup in the world. Including this one.

India's Reply: Rohit's 138 — The Innings That Made Lord's Stand

Before the match, the question circulating through the press box and across social media was whether this would be Rohit Sharma's farewell to international cricket. All eyes were on India icon Rohit Sharma, who was rumoured to play his final game for India at the home of cricket, although the BCCI denied his retirement news. As with all the best farewells, the answer came not in a statement but in an innings.

Rohit walked to the crease with India needing to chase 388 — a total that had never been successfully chased in a Lord's ODI — and batted as though the target was entirely manageable and the occasion entirely routine. He attacked from the first over. He pulled Archer for four in the powerplay before the pace bowler had settled into his length. He swept Rashid with the contempt of a batter who has played left-arm spin for 17 years and finds no mystery in it anymore. He reached his fifty from 46 balls. His hundred from 89. Rohit blitzed 138 — his 34th ODI century.

The 138 was, in the context of a lost match and a probable farewell innings, one of the great individual Lord's performances. It was not the innings of a batter in declining form. It was the innings of a batter who arrived at the home of cricket with something to prove — that the doubts about his fitness, his form, and his future that have circulated for the better part of a year were premature. Rohit allayed doubts over his form with a fantastic hundred, his first at Lord's. The ground rose to him when he was dismissed. The applause, coming from supporters of both sides, was the kind that tells you something beyond sport is being acknowledged.

Kohli, at the other end for much of Rohit's innings, made 74 — his highest score at Lord's in international cricket. His 74 was a 133rd score of fifty or more. Those two numbers together — a batter's 133rd fifty-plus score, at a ground where he had previously never passed that mark — suggest a player who arrived with a specific personal ambition and fulfilled it, even if the team result did not follow.

Shubman Gill contributed 77 from the top of the order before falling to Adil Rashid in the middle overs. At 270 for 2 in the 38th over, India were mathematically still in the chase — 118 from 72 balls with eight wickets in hand is demanding but not impossible on this surface. But once Rohit fell, India started to lag behind in the chase. Sam Curran's change-ups proved hard to tackle for the Indian middle order, while Bethell also chipped in with a crucial spell.

The middle-order collapse — that same structural fragility we identified across the T20I series and in the first ODI at Edgbaston — returned at the worst possible moment. Axar Patel and Washington Sundar, who had been India's batting heroes at Edgbaston, were both dismissed cheaply as India's chase unravelled through overs 40 to 47. The asking rate climbed beyond reach. Arshdeep Singh and Gurnoor Brar contributed late cameos — Arshdeep Singh 15 off 6 balls and Gurnoor Brar 18 off 14 balls — but the equation was too steep. India finished on 360 for 7. England won by 27 runs.

Rohit and Kohli: What Lord's Witnessed

Whether Sunday was the last time Rohit Sharma and Virat Kohli played international cricket in England is a question neither the BCCI nor the players themselves have answered definitively. If this was to be the last time Rohit Sharma and Virat Kohli grace English cricket, then so be it. For all who came to Lord's for this third ODI got to see their experienced stars show out. The phrasing in that Cricinfo report — "if this was to be the last time" — tells you everything about the mood in the press box. Everybody felt it. Nobody wanted to say it directly.

Rohit's interaction with Gautam Gambhir on the Lord's balcony after his dismissal — both men visibly emotional, the conversation lasting several minutes — was the image that travelled around the world before the match had even finished. Whatever was said between them will probably never be fully reported. But the context — a 38-year-old batter, in what may be his last international innings at the home of cricket, talking to the man who coaches this India team — made it one of those private moments that sport occasionally makes public without permission.

Kohli's 74 was greeted with the same kind of reception when he was finally dismissed. Applause from both sets of supporters. Appreciation that transcended the result. These are two cricketers — 10,700 and 27,000-plus combined international runs — who have given this sport more than can be summarised in any match report. Lord's was the right place for whatever chapter this is. If it is the last, it was worthy of both of them.

England's Series Win: What It Means

England have now beaten India in an ODI series for the first time since 2018. That eight-year gap is significant — it tells you how difficult India have been to beat at this level for the better part of a decade. The fact that this series was won without Jofra Archer bowling at his peak across all three matches, without Ben Stokes — who retired during the Test series — and on the back of a new captain in Harry Brook who was simultaneously being evaluated for the Test job, makes it a more impressive achievement than the headline result alone suggests.

Brook's captaincy across this tour — T20I and ODI combined — has been one of the defining stories of the summer. As we explored in detail in our full analysis of his Test captaincy prospects, the summer was always going to function as an audition. By any measure — results, tactical decisions, man-management, personal form — the audition has been passed with distinction. The ECB now faces the question of whether to give him the Test job before the Ashes squad is announced, and after a white-ball summer of this quality, the case for doing so has never been stronger.

Joe Root's Player of the Series award — 249 runs across three ODIs, including a 99 not out in Cardiff that he selflessly sacrificed to win the match — is one of the quieter masterclasses of the summer. Root in white-ball cricket has always been slightly underappreciated compared to his Test genius, and yet this series produced the kind of contributions — composed, intelligent, always what the team needed rather than what the statistics required — that remind you why he is the most complete England cricketer of his generation. As we covered in our first ODI report, Root's selflessness at Cardiff was already the defining moment of this series. The Player of the Series award is the confirmation of what everyone watching already knew.

India's Summer: The Honest Assessment

India leave England having lost the T20I series 4-0 and the ODI series 2-1. The combined record across the entire white-ball tour is one series win from two. India will have to take a closer look at their bowling attack as well as their team composition. Did India miss their allrounders?

That question — about allrounders, about the balance of the side, about the structural fragility that the middle-order collapse at Lord's exposed for the third time in this series — is the honest assessment India need to make before the ODI World Cup in South Africa in 15 months. Rohit's 138 and Kohli's 74 are evidence that the senior batters remain capable of match-winning contributions in English conditions. But both batters are approaching the ends of their careers. The middle order — Iyer, Tilak Varma, Axar, Sundar — has not consistently provided what India need when the top order falls early or the asking rate climbs above eight an over.

On this tour, with this squad, on these pitches, India showed they can compete. They cannot yet consistently win. The difference between those two things is the work that lies ahead.

Was Rohit Sharma's 138 at Lord's the perfect farewell innings — whether or not it turns out to be his last? And does England's 2-1 ODI series win, combined with the 4-0 T20I sweep, make this the most complete white-ball tour England have produced against India? Drop your thoughts in the comments below.

One Run. Last Ball. First Final. Los Angeles Knight Riders Win Maiden MLC Title

 

There is a moment at the end of the most dramatic cricket matches where time seems to compress into something almost unbearable. Last ball. Six needed. The bowler running in. The batter swinging. The ball going somewhere. And then — either a roar, or a silence, or something in between that tells you everything before anyone has even moved.

Oakland Coliseum, Saturday night. Shadley van Schalkwyk — the South African seamer who had already yorked Obus Pienaar to break the back of Washington Freedom's chase — ran in to face Lahiru Milantha at the non-striker's end, with Ian Holland on strike needing two runs from one ball to tie, three to win. Holland got a piece of it. The ball went towards vacant mid-on. Milantha, seeing the gap, ran. Holland ran. But the ball did not go far enough, the fielder got across, and the throw to the keeper beat Milantha by three strides. Los Angeles Knight Riders had won by one run. Their first MLC title. In their first MLC final. In front of more than 10,000 people at Oakland Coliseum, the largest crowd in MLC history.

In the background, Dwayne Bravo — LAKR's head coach, the man who had spent the season turning a squad of talented individuals into a team that believed it could win anything — was running onto the field with his arms outstretched before the bails had even settled. Rovman Powell, who had captained Knight Riders for three years across two previous seasons without getting close to a title, was on his knees. "It means everything," Powell said afterwards. "I've played for Knight Riders for years and never won it. We planned and pulled it off." The trophy presentation was pure noise — confetti, fireworks, Bravo dancing with the entire squad as Ricky Ponting stood across the ground doing his best to look composed while his Washington Freedom watched their third consecutive final end in defeat.

How LAKR Got to 164 — and Why It Was Nearly Not Enough

Washington Freedom won the toss and asked LAKR to bat first — a decision that, for roughly fifteen overs, looked entirely correct. Freedom's new-ball bowling was exceptional. Ben Dwarshuis, the left-arm South African seamer who was one of the competition's most consistent performers all season, swung the ball both ways in the Oakland evening air and finished with 3 for 31. Mitchell Owen was sharp at the other end, taking 2 for 14 in his four overs. Nikhil Chaudhary — the right-arm off-break bowler who became Freedom's most reliable spin option across the tournament — claimed 2 for 32. Between those three bowlers, LAKR were tied down through the powerplay and middle overs in a way that had Washington's coaching team feeling comfortable.

What saved LAKR from an uncompetitive total was the opening partnership. Andre Fletcher — the West Indian batter who styles himself "The Spiceman" and who had been in excellent form all season — attacked from the first over, hitting three fours off Dwarshuis in the powerplay and using Lockie Ferguson's extra pace to flat-bat through the covers for four and crack a straight six. By the end of the powerplay, Fletcher had made 38 of LAKR's 54 — a contribution that single-handedly kept his team on the right side of a score that threatened to slip below 150.

Fletcher's eventual dismissal for 47 triggered a middle-order wobble. Colin Munro, who had been slow to get going after a brilliant powerplay from his opening partner, fell for 40 when he finally found his timing — caught at the boundary attempting a hit that the situation did not require. Matthew Tromp made 39 before the wheels came off completely in the last three overs. LAKR were all out in the 19th over for 164 — a total that the commentary team immediately described as "ten to fifteen runs below par" for a final on this surface. That assessment, as it turned out, was almost correct. Almost.

Narine and Holder: The Bowling Performance That Won the Title

The key to understanding why LAKR won this final despite posting an under-par total is to understand what Sunil Narine and Jason Holder did in the first ten overs of Freedom's chase. Between them, across eight overs, they took six wickets for 44 runs. Narine struck three times in the powerplay — removing Matthew Owen first ball with a review that reversed the on-field not-out decision, then dismissing Gous for 40 as he attempted an ambitious sweep that caught a top edge to Holder at slip, then returning to remove Lahiru Milantha in a wicket that shattered Freedom's dream of a middle-order recovery. Holder carved up the middle order with his combination of bounce and movement, ending with 3 for 31 that included the wicket of Freedom's most dangerous batter, Steven Smith, who fell for 11 attempting a pull that found the fielder at square leg.

By the time Freedom reached the 15th over, they needed 46 runs from 30 balls with only four wickets in hand. In a normal T20 final, that is a match that is over. In a MLC final, on a flat Oakland surface with Obus Pienaar still at the crease, it was a match that was just beginning.

Pienaar's 53 — and the Over That Should Have Won Freedom the Match

Pienaar had been batting through Freedom's collapse without anyone noticing, accumulating ones and twos while wickets fell around him. He reached his fifty — a maiden T20 half-century — with a six off van Schalkwyk in the final over that brought the equation down to five needed from five balls. Oakland went quiet. Even Freedom's most vocal supporters seemed to understand that this was the moment where either the fairy tale was completed or it ended in the cruelest way possible.

Van Schalkwyk had other ideas. He yorked Pienaar next ball — clean, precise, the kind of delivery that requires total commitment at the death with the match on the line and a full house watching. Pienaar was gone for 53. Then Holland holed out third ball to a catch that Russell held at deep midwicket. Freedom needed three from the final ball. Holland and Milantha needed to run three, which is effectively impossible against a fielding side that has been set for exactly this scenario for the last two overs.

Milantha got a piece of it. He ran. He was out by three strides. LAKR won by one run.

What This Title Means for American Cricket

The broader story of this MLC final is not just about LAKR's triumph or Freedom's heartbreak. It is about what American cricket has become in four seasons and what it is still becoming.

More than 10,000 people attended Saturday's final at Oakland Coliseum — the largest crowd ever at an MLC match. The previous record was set at the same venue twelve months earlier, during last year's final. The growth is not a fluke or a one-off. The MLC has built a genuine American cricket audience — not just the South Asian diaspora that was always going to show up, but a broader sports audience that has been attracted by the quality of the cricket, the international names involved, and the specific entertainment value of a twenty-over format played under lights in American sports venues.

The names on the pitch tell you what the MLC has become as an attraction: Powell, Narine, Holder, Russell, Fletcher for LAKR. Gous, Smith, Ponting's coaching influence for Freedom. These are not development-level players. They are genuine international stars choosing the MLC as a priority destination — which was not the case when the competition launched in 2023 with its first modest crowds and understandably cautious ambitions.

For Washington Freedom, the loss is the third consecutive final defeat — and that stat tells its own story. Freedom have been the standard-bearer of the MLC since the beginning. Gous finished as the tournament's highest run-scorer with 547 runs. Their world-record T20 chase against MI New York earlier in the season — when three batters scored centuries in the same match for the first time in T20 history — was the moment that made the entire global cricket community pay attention to what was happening in America. And yet they do not have a title. Three finals. Three losses. In cricket as in life, the gap between building something and finishing it is the hardest distance to close.

For LAKR, the question now is whether this title is the beginning of something or a perfect storm of form and timing that may not repeat. Bravo's coaching, Powell's captaincy, Narine and Holder's irreplaceable experience — all of those things are contracted for next season. The core of the squad that won on Saturday night should be available to defend the title. Whether the franchise can maintain the hunger that produced eight wins in a season where three years of underperformance seemed to have been building to exactly this moment is the story of MLC 2027.

For now, Oakland Coliseum is empty and the confetti has settled and Bravo is somewhere celebrating in a way that suggests he does not intend to stop any time soon. LAKR are MLC champions. One run. Last ball. First final. It does not get more dramatic than this.

Do you think LAKR can defend their title next season — or does Washington Freedom's sustained quality make them the favourites to finally break their final curse? And where does this MLC final rank among the greatest T20 finishes you have ever watched? Drop your thoughts in the comments below.

Lord's, Oakland, and Birmingham: The Cricket Weekend That Has Everything

 

Sometimes the cricket calendar produces one of those weekends where every format, every competition, and every corner of the world seems to be producing something worth watching simultaneously. This is one of those weekends. An ODI series decider at Lord's tomorrow that could end Rohit Sharma's international career. An MLC final tonight in Oakland between the competition's two most successful sides. Vitality Blast semi-finals in Birmingham. And three days ago in Cardiff, a Joe Root innings of 99 not out that reminded the entire cricket world — as if it needed reminding — that the 35-year-old from Yorkshire remains the most reliable batter English cricket has produced in a generation. Here is everything you need to know.

Cricket's Designated Hitter: BBL's Bold New Rule Explained — and Why the IPL Numbers Tell the Real Story

 

The Big Bash League has never been shy about experimenting. Power Surge. Bash Boost. X-Factor substitution. The BBL has introduced and discarded more playing innovations than any other franchise T20 competition in the world, and its relationship with novelty has been both its greatest strength and, at times, its most embarrassing liability. So when Cricket Australia announced the "designated batter" rule for BBL|16 — effectively cricket's version of the designated hitter from American baseball — the predictable question was: is this a genuine tactical evolution, or is this another gimmick that will be quietly shelved in two seasons? The answer, this time, is more nuanced than the question suggests. This rule has real potential. It also has real problems. And the IPL data tells you almost everything you need to know about which outcome is more likely.

Different Team, Different Result: India Win the 1st ODI at Edgbaston — But the Questions Remain

 

Three weeks. That is all the time that separated the most embarrassing chapter of India's white-ball cricket in recent memory — 76 all out at Trent Bridge, their heaviest T20I defeat ever — from the most composed ODI performance they have produced in England in years. Same country. Completely different team. Completely different result. India won the first ODI at Edgbaston, Birmingham by six wickets with 28 balls to spare, chasing down 259 thanks to a captain's innings of 80 from Shubman Gill and an extraordinary all-round performance from Axar Patel — 4 for 62 with the ball, 57 not out with the bat — to take a 1-0 series lead. England, dismissed for 258 in the 48th over at one of their supposed fortress grounds, were poor with the bat and had no answer to a bowling attack that finally looked like what India's bowling is supposed to look like.

Lawes Stuns on Debut, Carty and Hope Chase it Down — West Indies Beat New Zealand by 7 Wickets

 

Providence, Guyana. A slow, low pitch that West Indies had specifically requested — a spin-friendly surface designed to neutralise New Zealand's formidable pace attack and give their own spinners something to work with. The plan, as plans sometimes do, worked almost perfectly. New Zealand were bowled out for 267 with one ball of their innings remaining, their last six wickets falling for 33 runs in what had looked like a much more competitive position. And then Keacy Carty and Shai Hope — West Indies' most reliable ODI partnership — chased it down with seven balls to spare, Sherfane Rutherford hitting a six off the last ball he faced to seal a seven-wicket win and a 1-0 series lead.

England Complete Historic 5-0 Whitewash of India: Full T20I Series Review, Analysis and the IPL Debate

 

England Complete Ruthless 5-0 Whitewash: How India's T20I Summer Fell Apart

Men Against Boy: Jofra Archer, Vaibhav Sooryavanshi, and the Battle That Defined This Series

 

There is a quote from Jofra Archer after Bristol that tells you everything about where this contest between fast bowler and teenager now stands. "It's evens now," Archer said after dismissing Vaibhav Sooryavanshi for the second time in two T20Is. "We have two games left and it could go anywhere, so may the best man win." And then — consciously or not — he used a word that cuts right to the heart of this story. "Man." Sooryavanshi is 15 years old. He changes in a different dressing room because English law says he is still a child. Archer is 30, one of the most feared fast bowlers of his generation, and he is not bringing out the kid gloves for anyone. Not even a boy.

Bristol or Bust: Can India Save the Series — or Will England Seal It Tonight?

 There is a phrase in cricket that gets used too loosely — "must-win" — but for India at Bristol on Thursday evening, it applies with unusual precision. Lose, and England seal the series with a match to spare. Lose, and Shreyas Iyer becomes the first India captain in the T20I format to lose three consecutive completed matches at the start of his tenure since the format began. Lose, and the questions that have been building since Belfast — since that Ireland series that now feels like a distant early warning — become unavoidable, public, and very loud.

England, meanwhile, arrive at County Ground Bristol with the kind of relaxed confidence that comes from having done almost everything right. Two wins from two completed matches. A 125-run victory at Trent Bridge that produced India's heaviest defeat in T20I history. A bowling attack that has taken wickets in every phase. A batting lineup that has posted 190-plus in both matches. Harry Brook's captaincy, under the quiet scrutiny of an ECB looking for their next Test captain, has been composed and correct. Everything points towards England finishing the job tonight.

But Bristol has a history of surprises. And India, for all their problems on this tour, still have the talent to produce one if the conditions allow it. That tension — England's dominance against India's desperation — is what makes tonight's match more interesting than the series scoreline suggests.

Shreyas Iyer: The Numbers That Cannot Be Ignored

Let us be precise about where Shreyas Iyer stands, because the numbers tell a story that goes beyond this series. Since taking over the T20I captaincy from Suryakumar Yadav — who won two consecutive T20 World Cup titles — Iyer has now lost ten of his last eleven completed matches as captain across all formats. That run includes the IPL with Punjab Kings, the Ireland series, and two T20Is against England. The one win in that sequence came against a weakened opposition in a low-pressure bilateral fixture.

After Trent Bridge, Iyer did not look for excuses. He called India's performance "atrocious." He described their execution with bat and ball as "awful." He acknowledged that the fielding — which included several costly misfields and a dropped catch at a crucial moment — was below the standard expected. That honesty is admirable. But honesty about a problem and the ability to solve it are different things, and India's issues on this tour have been consistent enough to suggest they are structural rather than accidental.

The captaincy decisions specifically have drawn the most criticism. At Trent Bridge, Shivam Dube came in at number eight — below Harshit Rana, a bowling allrounder — in a chase that required India's most destructive middle-order batter to bat as high as possible. The bowling rotations in Manchester allowed Jacob Bethell to face Ravi Bishnoi in the 17th over while set and in full flow, producing 29 runs from a single over that cost India the match. Tonight in Bristol, with the series on the line, Iyer's tactical decisions will be watched with a level of scrutiny that leaves no margin for the kind of errors that have characterised the previous two matches. As we explored in our series preview before the first match, the pressure on Iyer was already significant before a ball was bowled. It is now considerably higher.

The Samson Question — And Why It Matters More Than People Think

The biggest selection talking point heading into Bristol is whether Sanju Samson returns to the XI. Samson was dropped after three consecutive low scores — 5, 0, and 1 — to make way for Vaibhav Sooryavanshi's debut in Manchester. Since then, Sooryavanshi has played two matches, made 14 and 13 respectively, and been dismissed both times by variations that exploited his eagerness to attack. India's opening combination has not provided the platform their middle order needs.

The case for recalling Samson is straightforward: experience, composure under pressure, and a record in English conditions that is significantly better than his recent scores suggest. The case against is equally straightforward: his form on this tour has been non-existent, and dropping Sooryavanshi after just two matches — when the 15-year-old has shown no technical deficiency, only the natural learning curve of a teenager in international cricket — sends a message about India's patience with young talent that Gautam Gambhir, their head coach, has consistently said he does not want to send.

The compromise position — opening with Abhishek Sharma and Sooryavanshi, with Samson coming in at number four — would require moving Shreyas Iyer down and disrupting a batting order that is already underperforming. There is no clean answer. What is clear is that the decision India make at the toss tonight will tell us something important about whether their management has a plan, or whether they are reacting to results without a clear strategic framework. We discussed Sooryavanshi's debut and what his presence in this squad means in our full report on the Manchester match.

Bristol: What the Ground Gives You

County Ground Bristol is not a neutral venue for this contest. Its dimensions matter — short straight boundaries but wider square boundaries — and the surface at this time of year, during England's ongoing heatwave, tends to offer pace and carry early before flattening out in the second half of the match. The average first-innings score in T20Is at Bristol over the last three seasons is 178. Both completed matches in this series have already exceeded that number, which tells you something about the conditions England and India have been playing in.

India are unbeaten in four previous completed T20Is at Bristol. That record means very little given that those matches featured different squads, different conditions, and a different balance of power between these two sides. But it is worth noting that Bristol's dimensions — particularly those short straight boundaries — should, in theory, suit India's power hitters more than Trent Bridge's flat, wide ground did. If Abhishek Sharma or Tilak Varma can find a straight hitting groove early, the ground will reward them.

Adil Rashid's record at Bristol is also worth watching. He will bowl into rough on a surface that develops grip as the match progresses, and with 166 T20I wickets — now the second-highest in men's T20I history, overtaking Ish Sodhi's 165 on Tuesday — he is the bowler most capable of exploiting any surface deterioration in India's middle overs chase or in England's first innings. India's left-handers — Axar Patel, Washington Sundar if selected — will need specific plans against him.

England's XI: No Reason to Change

Harry Brook has already confirmed England will not change a winning combination. Phil Salt, Jos Buttler, Brook, Jacob Bethell, Tom Banton, Sam Curran, Will Jacks, Liam Dawson, Adil Rashid, Jofra Archer, Josh Tongue — this is the side that has performed in both completed matches, and there is no tactical or form-based reason to adjust it.

Jofra Archer and Josh Tongue as the opening pace pair deserve special mention. In two completed matches they have shared nine wickets between them — six in the powerplay alone — and their combination of outswing, short-pitch pace, and movement off the seam has consistently beaten India's openers before they can settle. Archer's pace, consistently above 88mph, and Tongue's hard-length accuracy create problems from different angles that India's top order has not found answers to. Tonight at Bristol, where the pitch offers early carry, expect the same plan from the first ball.

Brook's captaincy in the field has been the quiet subplot of this series. As we wrote in our full analysis of Brook's Test captaincy prospects, the T20I series was always going to function as an audition for the vacant Test captaincy following Ben Stokes' retirement. Two disciplined, well-organised wins have made that audition go as well as it possibly could. A series victory tonight would make it very difficult for the ECB to look elsewhere.

India's Path to Victory — It Exists, But It Is Narrow

India can win tonight. But the path is specific. They need Abhishek Sharma to do what he did in Durham and Manchester — attack in the powerplay before Archer and Tongue find their rhythm — and they need at least one middle-order batter to build an innings of 40-plus balls rather than the cameos that have defined their batting so far. Tilak Varma is the most likely candidate. He has the technique to handle pace, the temperament to bat through the middle overs, and the power to accelerate when the conditions allow.

With the ball, India need Washington Sundar or Axar Patel — the left-arm spin option — to bowl tightly in the middle overs and deny Bethell and Brook the kind of freedom they had in Manchester's 17th over. Varun Chakravarthy's wrist spin, which has been underused on this tour, could be a match-winner at Bristol if the pitch takes turn in the second innings. The conditions will dictate how much he is used.

The honest assessment is that England are favourites, probably heavily so. But a team that won the T20 World Cup four months ago has the talent to win on any given night. Tonight, with everything to play for and the embarrassment of Trent Bridge still fresh, India may be a more dangerous team than their recent results suggest. As we noted in our full report on the Trent Bridge collapse, the talent is there — the question is whether the planning and execution can match it.

Bristol, 5:30 PM local time. England need one more win. India need everything to go right. It is, whatever the series scoreline suggests, worth watching.

Do you think India can pull off a must-win at Bristol — and should Sanju Samson come back into the XI? Drop your prediction in the comments below.

England Humiliate India by 125 Runs at Trent Bridge — India's Worst T20I Defeat Ever

Trent Bridge has had a difficult few weeks. Ben Stokes retired here eight days ago, watching England lose the series to New Zealand from the dressing room. The same ground hosted one of the most emotionally charged endings in English cricket in a generation. And on Tuesday evening, it hosted something altogether different — a complete, clinical, merciless England performance that reduced India to 76 all out in 11.4 overs and handed them the heaviest defeat in their T20I history. England won by 125 runs. The series lead is now 2-0 with two matches to play. India, the reigning T20 World Cup champions, have not won a single game on this tour.

Anderson's Warning: England Need a Spinner for the Ashes — and They Need One Now

 

James Anderson has been retired from international cricket for nearly two years. He plays for Lancashire in county cricket, makes occasional appearances for the Manchester Originals in The Hundred, and has settled into the role of fast bowling mentor that the ECB offered him when they ended his Test career in July 2024. He speaks carefully and without bitterness about a career that ended before he felt ready for it to end. He is not, by any measure, a man who looks for reasons to criticise the England setup that let him go.

Which is why what he said on the BBC's Tailenders Podcast about England's Ashes tactics carries weight that a more politically motivated voice would not. Anderson is not grinding an axe. He is a 704-wicket Test bowler who watched England lose 3-0 in Australia last winter and saw, with a seamer's eye, exactly what went wrong — and why the same mistake could happen again if England do not address it before the 2027 Ashes series at home.

"The all-pace attack 100% worked in the first innings," Anderson said. "We landed a few blows." And then came the qualification. "But Head knew they were bowling short, so he just sat on the back foot and hit his areas." The problem was not the strategy in isolation. The problem was that England had no alternative once Australia's batters adapted to it. "I just wonder whether we lack a nuance — a bit of something different and a change of pace, whether that is a spinner or a slightly different pacer. There was no frontline spinner to just bowl four overs."

That is the critique. Now let us look at whether it is correct — and what it means for where England go from here.

What Actually Happened in Australia

England arrived in Australia for the 2025-26 Ashes with what McCullum and the selectors believed was their strongest available seam attack. They were without James Anderson — retired since 2024 — but they had Gus Atkinson, Brydon Carse, Josh Tongue, and Mark Wood. The plan was to bowl short and hard, exploit Australia's middle order against pace on bouncy Australian pitches, and use the conditions that Anderson himself had often found so difficult in his own Ashes tours.

In the first innings of Brisbane, it worked. Australia were put under genuine pressure. Travis Head — who had tormented England in 2023 with an aggressive counter-attack that made the short-pitched plan look naive — was dismissed for a modest score. England had Australia in trouble.

Then came the second innings, and Anderson's point became the post-series headline. Head made 87 off 59 balls. He simply sat back and hit everything pitched short. Once he had clocked the length, he was never troubled by it again — because England's seamers could not change the plan. There was no spinner to slow the over rate, change the angle, bowl to the rough, and force the right-handers to play in a way they were less comfortable with. England's all-pace attack, which had looked like a strength in the first innings, became a limitation the moment Australia's best player identified and neutralised the central idea.

England lost the series 3-0. They came home to a New Zealand series that they lost 2-1. They ended the summer with Ben Stokes retired, the WTC ranking at 7th, and an Ashes series in England in 2027 looming on the horizon. As we explored in our three-year Bazball review, the bowling attack's inability to take 20 wickets against the strongest opposition has been the single most persistent problem of the Stokes-McCullum era. Anderson's critique connects directly to that pattern.

The Spinner Question — England's Most Complicated Debate

Anderson's specific point about a frontline spinner is the most interesting part of his analysis, because it is also the most contested. England's position on spin bowling in Test cricket has been deliberately aggressive since 2022 — they have picked Jack Leach selectively, used Shoaib Bashir in specific conditions, and leaned on the pace quartet as the primary attacking option in almost all conditions. The results in England have been strong. Spin on English pitches in summer conditions is rarely decisive anyway. But in Australia — where pitches deteriorate from day three onwards, where the rough outside the right-hander's off stump becomes a weapon in the second innings — the absence of a high-quality frontline spinner is a genuine tactical gap.

Stuart Broad, speaking around the same time as Anderson, added his own layer. He pointed to Travis Head's method specifically — the way Head identified that England were bowling short and simply relocated his back foot, playing everything off the back of a length. England's seamers, once Head had cracked the plan, had no variation to offer. A spinner — bowling flatter, slower, potentially into rough — would have presented a fundamentally different problem. England had no such option available.

The counterargument, made by those who defend the all-pace approach, is that England's spinners have not been good enough to justify the selection on bowling merit alone. Shoaib Bashir has shown promise but is not yet ready to be England's primary attacking spinner on Ashes pitches. Jack Leach has been in and out of the side for three years and has never quite nailed down the kind of consistency that would make him automatic. The problem, in other words, is not just tactical — it is that England do not have the spinner to execute the plan Anderson is describing.

Which brings us to Rehan Ahmed. The leg-spinner, who made his Test debut at 18 under the Bazball selection philosophy — an approach we discussed when looking at how England and India have both embraced backing young talent — is currently the most exciting spin option England have. He is 22. He took wickets in Pakistan on debut. He has played sporadically since. If Anderson's critique is correct, the urgency around Rehan Ahmed's development becomes the most pressing bowling selection issue in English cricket right now — more immediate, in some ways, than the captaincy question.

What McCullum Must Answer

Brendon McCullum is still England's head coach. He survived the Ashes review. He survived the New Zealand series defeat. He has the backing of Rob Key and — for now — the ECB. But as we noted in our piece on Harry Brook's captaincy prospects, the post-Stokes era requires McCullum to do something he has not yet had to do in four years as head coach: build something new rather than maintaining something established. Stokes was the emotional and tactical foundation of everything that worked. The bowling philosophy was as much Stokes' instinct as it was McCullum's design.

Without Stokes as captain, McCullum now has to answer Anderson's question directly. Not in a press conference — in a selection decision, a training programme, a development pathway. The answer to "do England need a frontline spinner for the 2027 Ashes?" is almost certainly yes. The answer to "which spinner, and how do we get them ready in 12 months?" is the harder question — and it is the one that McCullum needs to solve before England announce their Ashes squad next year.

There is also a broader tactical implication that Anderson's critique raises. England under Stokes and McCullum became the best attacking team in the world in favourable conditions. The Ashes 2023 series — 2-2 at home, a moral victory if not a trophy — showed they could compete at the highest level. But every series away from home against top opposition since 2022 has produced the same result: England's plan is identified, countered, and they have nothing in reserve. India 4-1. Australia 3-0. The pattern is consistent enough to be a structural problem rather than a sequence of unlucky results.

Anderson's Deeper Point

What makes Anderson's comments more than a retired player criticising his former team is the specific nature of the observation. He is not saying England bowled badly. He is not saying the all-pace approach was wrong in principle. He is saying that without variety — without something the opposition cannot simply sit back and counter — England's attack becomes predictable the moment a batter of Travis Head's quality works out what they are doing.

That is a bowling coach's observation, made with a bowling coach's precision. Anderson knows better than almost anyone alive what it feels like to operate as the change of pace in an England attack — to bowl 70mph away-swing after Stuart Broad has been hitting the pitch at 85mph, and to watch batters suddenly unable to find their rhythm. The disruption of variety is not just tactical — it is psychological. It forces batters to reset, to make decisions at different speeds, to commit to shots at different tempos. An all-pace attack, however hostile, allows a settled batter to find one rhythm and stay there.

England will host Australia in 2027. The series will define whatever era succeeds Bazball — and the new captain, whoever it is, will be defined by that result more than any other. The bowling attack that takes the field in that first Test needs to be better than the one that lost 3-0 in Brisbane in December 2025. Anderson has identified, clearly and specifically, the most important thing that needs to change. Whether McCullum and the new captain act on it is the question that the next 12 months of English cricket will answer.

Do you think Anderson is right that England need a frontline spinner for the 2027 Ashes? And is Rehan Ahmed the answer — or does England need to find someone else entirely? Drop your thoughts in the comments.