Home Ground, Not Home: The Venue Ledger the Champions Trophy Scoreboard Never Counted

On March 9, 2026, at the Dubai International Stadium, New Zealand made 251 for 7. India replied with 254 for 6 in 49 overs — a four-wicket win. Rohit Sharma's 76 was the Player of the Match; Shubman Gill was Player of the Tournament. Death-over maths, spin lines, run-rate curves — every account balanced.

I did not open the scorecard that day. I opened the fixture ledger. And the first line that caught my eye belonged not to a batter but to a venue.

The host nation was Pakistan. The trophy-deciding match was played in Dubai. India played five matches in the tournament — all five in Dubai, consecutively, at the same ground, on the same pitch block, out of the same dressing room. New Zealand played group games in Karachi, Rawalpindi and Dubai — three cities, two countries — then travelled to Lahore for a semi-final.

One tournament. Two different geographical realities. The scoreboard recorded neither. That job falls to the fixture ledger.

The ICC Champions Trophy 2026 ran from February 19 to March 9: eight teams, two groups. Pakistan hosted, but under the hybrid model all of India's matches were shifted to Dubai. Four venues in total — Karachi, Lahore, Rawalpindi, Dubai. One of those four sits in another country, on another pitch family, in another climate zone, in another time zone.

Writing about venues is almost automatically writing about politics — that is the default reading in South Asian cricket. From an Australian data desk, the same venue appears differently: a variable left outside the model, a column nobody built. I grew up between the two cricket cultures, and both registers sit within reach. So let me state the vantage up front: this is not a political verdict. It is a ledger reconciliation.

The method is simple, and less glamorous than it sounds. For each team I tabulated four columns: matches played, venues used, travel legs and border crossings, and crowd composition. Without player-tracking data, the fourth column is a visual estimate on my part, and I am labelling it as such — dressing an estimate in the clothes of data is not my job.

Why bother with something this dry? Because what a tournament model does not measure is frequently what decides it. In 2026 I ran a model across 84 matches played through empty stadiums. Home advantage fell from 0.45 xG to 0.12 xG. That number was not an excuse; it was a yardstick nobody had built before the tournament began. Five years later the same question returned in Dubai, only from the opposite direction.

Column one — repetition. Five matches, one ground. In any cricket model the 'venue familiarity' term is small, never zero. Five matches on the same pitch block means that by the second or third game a side knows how much the surface will grip. Which boundary runs quicker, how the wind sits above the wicket, where the cushion is higher — these things settle into the body not once but five times. The opposition relearns every time, and learns only once. Five consecutive matches at one ground is practice for one team and an exam for everyone else.

Column two — travel. Karachi, Rawalpindi, a cross-border flight, Dubai, then Lahore for a semi-final: that was New Zealand's route. India's route was hotel to ground, ground to hotel. Recovery science now suggests long-haul flight load lingers on a sprinter for 24 to 48 hours. Who put those 48 hours on the tournament dashboard? Nobody. The flight clock does not appear on a scorecard.

Column three — the stands. An India match in Dubai means an ocean of expatriate Indian support. This is where the label fails. 'Neutral venue' describes a political status, not an acoustic one. Anyone reading venue neutrality as acoustic neutrality is making a data-entry error — not a political one, an accounting one. The output is home advantage; only the label changed. In the final's television coverage, New Zealand shirts sat at the edge of frame while the centre of the picture belonged to another country's noise.

Column four — the record book. On February 23, in Dubai against Pakistan, Virat Kohli completed 14,000 ODI runs. On March 2, again in Dubai, India met New Zealand in the group stage. In the first semi-final in Lahore, Rachin Ravindra made 108. On March 4 and 5, across two days and two countries, two semi-finals were staged — one in Lahore, one in Dubai. The ledger recorded all of it. What it did not record is simpler still: the host nation did not deliver a single ball of the trophy-deciding match on its own soil.

One blank line in that ledger is also part of the accounting. Afghanistan played its first Champions Trophy — a row in the spreadsheet after two decades outside the fixture list. On the calendar that single line is a significant change; on the data sheet it is larger still, because the longer an absence runs, the less time it needs to form a pattern of its own. An empty fixture list and an empty stadium are both evidence to me, not atmosphere.

Now the part that must be done, or the piece sits unfinished. I am not claiming India's trophy deserves an asterisk. I do not have the data to make that claim. Five matches is such a small sample that one dropped catch, one DRS call, one rain interruption could invert the whole sum. The gap between correlation and causation is the most expensive lesson of my working life — and the older I get, the more clearly I can see the gap.

What can be claimed is weaker and more uncomfortable: this tournament produced a variable and did not measure it. Nothing more. There was no chair for that column at the post-final press conference.

A vantage split needs naming here, because two cricket cultures read the same fixture list in two ways. To a South Asian eye, a venue is a political story — who plays where is the headline. To the Australian desk I file from, a venue is a control variable whose place is in the model, not the narrative. Both readings are correct and both are incomplete. And it is in the narrow gap between those two registers that much of tournament analysis quietly disappears.

The next world tournament will have a venue column too. It always will. The question is who owns it. A match committee in a boardroom will build a roadmap, a fixture list will arrive as a PDF, and the venue line will sit at its default — exactly as it did last time.

I would like someone to put a name at the top of that column before the first ball is bowled. A fixture list is a data structure, and structure is a kind of kindness — it saves us from our own chaos, and especially from our own lazy eyesight.