Australia end India's Women's T20 World Cup campaign at Lord's

Lord's has hosted its share of quiet endings. This one was loud. On 28 June 2026, Australia knocked India out of the Women's T20 World Cup with a six-wicket victory in their Group 1 fixture at the London ground, claiming a result that left the Indian side reliant on net run-rate calculations that did not, in the end, go their way. The match, listed for a 14:30 BST start, finished with the Australian chase in hand and the Indian tournament over.

The result is less a shock than a confirmation. Australia arrived as the defending template of the format; India arrived with the most aggressive batting depth in the competition. The meeting at Lord's settled the question of who, on the day, had more margin for error. Australia had it.

A frantic Indian finish, then a measured chase

India's innings ended in the kind of controlled chaos that has become a signature of the shortest format. The BBC's ball-by-ball account records a late flurry in the final two overs, with boundaries and wides flowing in both directions as India pushed their total to 170, a score that looked par on a Lord's surface that had played true throughout the group stage. The Sport live blog carried the contemporaneous notes: India made one change, bringing in Kranti Gaud for Nandani Sharma, while Australia went in unchanged.

The Australian reply did not need heroics. It needed arithmetic. Chasing 171, the top of the order worked the powerplay, absorbed one early wicket, and let the middle order finish the job with overs to spare. The six-wicket margin was less about dominance than about clarity — at no point in the chase did India's bowlers look like taking the remaining wickets at the required rate.

Lord's as a venue, not a verdict

It is tempting to read a Lord's defeat as something more than a group-stage exit, particularly given the venue's symbolic weight in the men's game. It is worth resisting. Group 1 of this tournament has been compressed — rain, a forfeited fixture, and the structure of the format have all left teams calculating run-rates as much as results. India's exit is not a collapse; it is a tiebreaker that went the wrong way. Sky Sports' match report frames the result as a direct elimination, but the underlying numbers — India's scoring rate through the tournament, the marginal difference between progressing and going home — were always going to be the decisive factor.

What the result means, and what it does not

For Australia, the win extends a record of deep tournament runs that has become the default expectation rather than the headline. The squad has the depth to absorb a quiet day from any one player; on 28 June, no Australian batter needed to be exceptional, and none were.

For India, the immediate reading will be harsher than the performance warrants. The team pushed the tournament's strongest side to a target that required a full chase; the batting order found runs when the innings looked in danger of stalling; the bowlers were, by the standards of the tournament, economical until the chase settled. The gap was small. The format does not always reward small gaps.

The road from here

Australia advance to the next stage of a competition whose knockout rounds begin in the days ahead. India go home, and the post-mortems — a missed over here, a dropped catch there, a net run-rate column that came up short by a fraction — will run for as long as the squad is in the air. Lord's will not be where the tournament is decided. It is, however, where India's was.

This desk covered the fixture with priority on wire reporting from Sky Sports, the BBC, and The Guardian's live blog. Where the accounts diverged on the precise margin of Australia's chase, the Sky Sports match report — the only one of the three to give a definitive six-wicket figure — was taken as the headline number.