The War of the Last Twenty Minutes: Ahmedabad's Silence and the Arithmetic of Squad Depth

A Tram from Six Years Ago, and the Arithmetic of One Over

On page twenty-seven of my notebook there is a line written in English, because that night the Bengali spelling would not come — “The loudest thing in the world is ninety-two thousand people realising the same thing at the same moment.”

That was 19 November 2026. Melbourne was deep into the night and the last 86 tram had rolled into the depot. The tram that usually carries me home from Southbank was not there that night; what was there was a share-house living room, an ageing laptop, a mug of tea going cold, and Ahmedabad on the screen. The Narendra Modi Stadium. More than ninety-two thousand people inside it.

The match ended on the fourth ball of the 43rd over. India 240, Australia 241 for four. Six wickets, forty-two balls to spare. Before the trophy there was a moment the main camera barely caught — a large part of the crowd went silent at once, and through that silence came exactly one sound, the shouting from the Australian dressing room. I shut the laptop and wrote in the notebook: “A stadium of ninety-two thousand can go quieter than an empty one.”

I still hear the 86 tram humming under that bird.

Because on that tram in 2026 I first understood that a match does not finish in the last over. It finishes much earlier, in some ordinary over, where one person takes a decision and the other team quietly accepts it. In Ahmedabad that over was not the 48th or the 49th. It was the 28th — when Travis Head and Marnus Labuschagne did not once worry about the required rate.

---

A Format That Erodes Depth, and Then Rewards It

The 2026 format was ten teams, nine games each, a single table, and four semi-finalists. From outside it sounds simple — everyone plays everyone, the best four go through. What the format actually does is erode a squad over time. Nine games across roughly six weeks, six different cities, different surfaces, and an Asia Cup immediately before it. Flights, hotels, training sessions, and the small administrative labour of recalibrating pace for each venue.

In football writing I keep returning to the five-substitution rule. It lets the bench breathe, certainly; but it also turns the final twenty minutes into a war of attrition for bigger clubs, where the smaller side survives on heart rather than legs. Cricket has no direct equivalent, because eleven people have to stay on the field for the whole innings. Yet the arithmetic of tournament density governs the same way — the only difference is that the bench space is occupied not by substitutes but by a trained spare batter and the shoulder of a fourth or fifth seamer.

Australia entered this format from a bizarre position. They lost their first two games. On 8 October to India by six wickets in Chennai, on 12 October to South Africa by 134 runs in Lucknow. Two games, zero points, net run rate underground. On paper that is nearly elimination. Then they won nine in a row, and in the final three weeks of the tournament they became a team it was hard, almost impossible, to beat.

A transfer rumor is a folk song waiting for its chorus. Australia's campaign was exactly that song — nobody found the tune in the first two verses, and from the third verse the whole stadium was singing.

---

Ten Matches, Nine Wins, and One Used Pitch

India's league phase is the most under-discussed chapter of this story. Nine matches, nine wins. Rohit Sharma's batting as captain was the tournament's boldest tactical statement — a strike rate in the 125 range at the top, 597 runs in all. These are not merely runs; this was an announcement that in the first ten overs India would not just bat, they would set the tempo of the scoreboard.

Virat Kohli made 765 runs in eleven innings at an average of 95.62, the highest aggregate by any batter in a single World Cup. Mohammed Shami took 24 wickets at 10.70, a late entrant who still set an Indian record for a single edition. Jasprit Bumrah's economy sat in the region of four an over, which is another way of saying the middle overs were played with a hand around the throat.

The numbers only make sense when the chant is still in my ears. So stopping at nine-nil leaves the picture incomplete. What actually happened is that in at least four of those nine wins India did not take the match to the final over — they won it by building pressure through the middle overs. Not at the start, not at the end.

Now the final. 19 November, Ahmedabad. The pitch was slow, and to be more precise, it was a used surface. Pat Cummins won the toss and chose to field. Many questioned the call that day, since a used pitch is supposed to be easier to bat on later — the surface darkens, spin arrives more slowly, the seam stops moving as much, scoring gets easier.

The common belief is that chasing in Ahmedabad is hard. But on that surface the ball came onto the bat slowly, which meant that building a score required time, and time means keeping wickets in hand. If the target sits in the 240s, there is no need to take risk at the top — that, not the toss itself, was Cummins's real tactical decision.

But the story of the match turned at the fall of the third wicket on 47. David Warner, Mitchell Marsh, Steven Smith — all three gone. The instinct in that situation is attack, risk, win or fall. Australia did not attack. Head and Labuschagne added 192, and in that entire stretch they did not play a single unnecessary shot.

Head made 137 off 120 with fifteen fours and four sixes. Labuschagne made 58 off 110. The structure of those two innings is the actual lesson — one anchor, one aggressor, and zero argument about either strike rate. Neither man put pressure on the other, neither stole the other's strike. When Head fell, Australia were already close; Labuschagne and Maxwell finished it without theatre.

This is where my esports notebook earned its keep. In League of Legends, the draft phase and the toss-team selection share one quality: both are decisions that shape the arc of the game while never appearing on the scoreboard. The Baron dance and cricket's overs twenty-five to forty do the same work — what is built there is only harvested later. And the meta shift? In cricket the meta shift has a name: dew and pitch degradation.

Sports culture is a tram route: every stop has a chant and a rumor.

Now the crowd. More than ninety-two thousand people means ninety-two thousand separate scoreboards. That night, across WhatsApp, X and YouTube, a single argument ran: what do you call a team that wins nine matches and loses the final? Some said historic failure. Some said a victim of the format. Some simply posted a picture of Head with no caption. This crowd, this meme-meta, these fresh arguments assembled in ninety minutes — these are now part of the cricket match itself, not an appendix to the scorecard. From streamers to tactics channels, everyone with their own replay, their own slow-motion thirty seconds. As long as that noise kept running, the silence of Ahmedabad could not be reinstated.

---

Choking Is a Comfortable Word

Now comes the part where I refuse the easy sentence. India lost the final. That is true. But choking is a comforting word because it is simple, and simplicity is rarely good journalism.

India were playing a final on a surface that allowed 240, with a squad built around the idea of 350. That is a mismatch between personnel and conditions. Add an injury few people still remember — on 19 October in Pune, against Bangladesh, Hardik Pandya injured his ankle and did not play again in the tournament. That removed a specific luxury: an extra seamer and an extra finisher in the same body. The gap was only partly filled, and partly filled means reduced tactical flexibility. The absence of that dual-role batter-keeper option tied the team's hands in the last ten overs.

So what am I claiming? That India did not break under pressure; India were playing a different match, and the match became something else. In the final fifteen to twenty overs the scoring rate dropped below five an over, wickets fell at regular intervals, and the modern death-overs assault never arrived. That is not a psychological collapse. That is a structural mismatch.

But honesty demands this, and it is the most important concession in this piece. Those who said Australia caught better and India lost their edge in the field under pressure were right. Australia's fielding in the Kolkata semi-final against South Africa had already proved it. In the bank balance of small moments, Australia were ahead, and in the final that decided it. When the consensus is correct, there is no need to manufacture the opposite.

One more thing deserves saying, because the brevity of a tournament sometimes magnifies the gap between two teams and over-weights the individual determinant. What happened across those last twenty-seven balls was the conclusion of a strategy, not the collapse of a person. In the ledger of my notebook, it is an extra mark erased from a block: the block is permanent, and only the difference inside it is ever recorded.

---

One Question for the Next Cycle

As I write these lines, morning light is reaching the window in Melbourne, and my notebook already carries fresh dates beside 2026 — India escaping South Africa by seven runs in the Barbados final of 2026, India beating New Zealand in Dubai in 2026, and ahead of us a T20 World Cup at home in 2026.

The notebook still smells like kickoff.

That tournament arrives on Indian and Sri Lankan soil, and the question remains the same: when a tournament asks six weeks, six cities and eleven people of you, do you build a batting order around the highest possible score, or around never having your hands tied in the last twenty minutes? The 2026 answer is already in our hands. Whose hands the next one lands in, I am still waiting to find out, notebook open.