The 240 in Ahmedabad: A Baseline Audit of a Final

Hook

November 20, 2026, half past eight in the morning, Manchester. I put the kettle on and opened the laptop. The first line in my notebook was not the score — it read: "Pitch: black-soil strip, slow, dew expected in the second innings." The ODI World Cup final at the Narendra Modi Stadium. India batted the full 50 overs and were bowled out for 240. On first look the number sounds competitive; 240 can be defended in a final. But sitting at my table, a different figure caught my eye: Australia finished on 241, India on 240 — the gap was one run. Six wickets looks like a heavy defeat, yet Australia got there with 42 balls in hand. Those 42 balls were the real story. To see where they were hiding, you need a baseline first.

Context

India had won ten straight matches across the group stage and the semi-final. Australia lost their first two games — to India in Chennai, to South Africa in Lucknow — then won nine in a row to reach the final. The biggest question before Ahmedabad was the pitch; there had already been a controversy about the surface being swapped mid-tournament. Pat Cummins won the toss and chose to field.

Ahmedabad showed two personalities that tournament. Early on it produced runs in bulk; later the black-soil strip slowed down and batting became hard work. The final was played on one of those slow strips, where 250 to 260 in the first innings is automatically filed as a good score. But before filing it, ask: good for whom? For the first innings, or for a second innings played under dew? If the baseline cannot answer that, the number stays hollow.

I had written three limits into my methodology sheet before the match, so I could not cheat myself later. First, only ball-by-ball data from this match. Second, tournament data kept on a separate layer, because one tournament's baseline dies in the next. Third, no variable called pressure, nerve, or big-match temperament — I have no measurable definition for any of them. Data provenance matters here too: no ball-by-ball feed contains a column called dew. You have to build it yourself, by counting outfield conditions, ball-change frequency, and spinners losing grip. A cause that is not in the database can still enter the analysis, but it enters as an assumption, not a verdict.

Core Analysis

Start with the baseline. India: 240 off 300 balls — 4.80 an over. Australia: 241 off 258 balls — 5.60 an over. The gap is 0.80 runs per over, a figure that appears nowhere on the scoreboard. In a final, 0.8 runs per over is roughly forty runs of hidden pressure.

Look at the shape of India's innings. Rohit Sharma made 47 off 31, so the opening run rate was above six an over. After wickets fell, the tempo dropped. Virat Kohli made 54 off 63; KL Rahul made 66 off 107. Rahul's innings was not a failure; someone had to hold the other end. But 66 off 107 is a run rate of 3.7. That means strike rotation and boundaries both slowed in the middle overs. Cricket's dot-ball pressure works like PPDA in football: the more you force a side to take singles and twos, the more boundary-dependent it becomes. Australia did exactly that.

Now Australia's innings. Travis Head made 137 off 120. Before the match, my table listed Head as a risk, because his strike rate against spin and his strike rate against pace are two different numbers. Had India squeezed spin through the middle overs, the final could have turned. Ahmedabad's dew broke that calculation. Once the ball gets wet, spinners lose grip, the ball comes on better, and the second-innings batting baseline shifts upward. That is the mechanism. So Cummins winning the toss was not merely luck — it was the mathematical advantage of batting second on that surface. Marnus Labuschagne's unbeaten 58 turned that advantage into a route where the required rate never came under threat.

India's bowling plan had been built on one thread all tournament: Mohammed Shami was the leading wicket-taker with 24, and Jasprit Bumrah's powerplay line was the side's tightest control. In the second innings, with the ball wet, that control slipped. Spinners got no grip, swing faded, and the Head-Labuschagne pair began taking calm singles. This was not a sudden collapse; it was a mismatch between the physical state of the ball and the bowling plan.

I also ran the out-of-sample check. I looked at the other day-night games at Ahmedabad that tournament to see whether second-innings run rates sat above first-innings rates. The sample is small, so confidence is low — I am stating that plainly. What data existed pointed toward a dew advantage; it did not prove one. Holding that distinction is essential, otherwise a direction gets promoted into a law.

I do not chase narratives; I build a table and wait for them to walk over and take their seat.

Contrarian Angle

There is a trap here. "India lost because of dew" is easy, sweet, and incomplete. If the toss were that decisive, the same pattern would have shown up across the rest of the tournament. It did not; toss-winning sides lost regularly in that event. So in Ahmedabad the toss was a condition, not the sole cause. Miss that distinction and analysis turns into baseline worship.

The opposite reading is just as incomplete: "India could not handle the pressure." Pressure is an inference, not a measurement. If I want a variable called pressure, I must first write down what I am measuring — dot-ball percentage, strike rotation, shot-selection quality, or scoring tempo? Saying "temperament" without a definition pushes cricket back to the level of a storybook.

One more unmeasured thing: the crowd. Ahmedabad was nearly full, and almost all of it backed India. Whether that noise is pressure on the opponent or a weight of expectation on the hosts is something nobody measured. In 2026, empty stadiums handed us a rare controlled experiment, and a measurable home advantage appeared. A standard dataset for crowd pressure in a full stadium does not yet exist. What cannot be measured cannot be used to explain a result.

The eye is a witness; the data is the cross-examination. Watching Head's 137, I too believed Australia were unstoppable. Under cross-examination, it emerged that India were not beaten by one batsman — they were beaten by a second-innings pitch, an innings of 66 off 107, and a shortfall of 0.80 runs per over.

Takeaway

For the next tournament cycle, my plan is simple: a table with four columns — venue, pitch type, toss, second-innings run rate. With a table, nobody needs to complain. And if a side loses a final by one run next time, will you call it a choke? Before you do, write down how you intend to measure it. I will wait.