One Ground, Five Matches: India's Dubai Residency Experiment at the 2026 Champions Trophy

On the night of 9 March 2026, when India chased down 252 against New Zealand at the Dubai International Stadium with four wickets in hand, I already had a sheet open on my laptop. Five matches, roughly 2,400 balls logged — over, batter, bowler, field, wicket type, and the required rate at the moment each ball was bowled. Rohit Sharma's 76 was a row in that sheet. The final was another row. But the number that stuck was not 252 and it was not 76. It was: five matches, one ground, zero flights.

Eight years ago, in June 2026, I stood on a £45 standing ticket at The Oval and watched Pakistan make 338. That night I logged about 222 balls on the back of a match programme and typed them into a spreadsheet when I got home. What has followed me since was not the 180-run margin. It was that the moment Mohammad Amir started pitching the ball fuller than six metres, India's scoring rate halved. I have not opened a match piece with the result since.

This time I was not in the stands. I was in London, 5,500 kilometres away, doing the same thing. And the sheet did what it always does: the game started telling a second story.

Context: this tournament was a logistics setting more than a cricket one

The 2026 Champions Trophy ran from 19 February to 9 March. Pakistan were the hosts, but under the hybrid model agreed between the PCB and the BCCI in December 2026, all of India's matches were played in Dubai. That arrangement did not merely relocate one team's fixtures; it reshaped the whole schedule around them.

India's five matches were Bangladesh, Pakistan and New Zealand in the group, Australia in the semi-final and New Zealand in the final — all at the same venue. No flight in a fortnight. No hotel change. One training net, one dressing room, one temperature, one humidity reading.

Compare Pakistan, who moved between Karachi, Lahore and Rawalpindi: a flight every four or five days, a new hotel, a new surface to relearn. Australia and England travelled inside Pakistan too. New Zealand, India's final opponents, had played in Dubai earlier in the group stage — but with Karachi and Lahore in between.

The BCCI sold this arrangement in political language. I want to read it as a data condition: the format removed a variable that cricket analytics has never properly measured — migration load. Cricket has no standard accounting for the physical cost of moving a squad between matches. Football hands us tidy-looking metrics like distance covered, in which pointless running produces a pretty graph. Here the effect is the opposite: playing five games on one ground leaves no pretty number at all, because the benefit sits inside the body rather than in the ball-by-ball record.

Look at the squad through that lens. India carried four spinners — Ravindra Jadeja, Axar Patel, Kuldeep Yadav and Varun Chakravarthy. For a tournament that runs from Karachi's damp squares to Rawalpindi's harder surfaces, four spinners looks like malpractice. For five matches on one ground, it is the rational answer to a known question. Meanwhile Jasprit Bumrah missed the tournament with the back injury he picked up at the Sydney Test in January 2026. Rather than load an all-format fast bowler with five Tests and a travel-heavy schedule, India rested him outright. That was a medical call, but its premise was the same: the team planned its workload around what was fixed, and Dubai was what was fixed.

Core: what did avoiding the road actually save?

First, the sample and the limit, because without them everything below is just a claim. I coded five matches ball by ball; this is one team in one tournament. n = 5. I will not quote a rate to three decimal places on that. Treat what follows as a hypothesis, not a finding.

Even inside that limit, one thing is clear: travel is not a soft metric; it translates directly into ball speed and decision quality. Relocating mid-tournament leaves you roughly 48 hours to solve the next opponent, and eight to ten of those hours disappear into airports, flights and check-in. In a squad without deep reserves, that loss does not put your five most important players on the field younger; it puts them on the field flatter. In Dubai the 48 hours were 48 hours.

In my sheet the indirect effect showed up. India's fast bowlers held their release points and speeds within a narrow band across the death overs of all five matches — the late-tournament drop-off that normally arrives in the fourth or fifth game did not arrive. I will not call that proof of anything. I will call it a signal that the physical load was light, because a share of the load did not exist.

Now the point where I think most coverage went wrong. We wrote Dubai down as home advantage, and Dubai is not India's home ground. Outside the India-Pakistan fixture the crowds were not enormous, and no cultural claim of home attaches to an ICC venue. This was not home advantage. It was variance reduction. The distinction matters. Home crowds help by giving the bowler noise, pressuring the umpire, handing the batter a familiar surface. What India got here was colder and more valuable: the number of variables that changed overnight collapsed.

And the biggest return on that collapse is paid not on the field but in the selection meeting. If you know the whole tournament will be played on one family of surfaces, you can build a squad that is a precise solution to a single problem — four spinners, two spin-bowling all-rounders, a batting order designed to chase 250 on a slow, low pitch. A travelling tournament charges you for that luxury: you must carry three plans for three conditions inside one squad, and the result is that none of them is fully applied.

That is why I read this tournament less as 'how India won' and more as 'what India were allowed to choose'. Dubai did not make India play better cricket; it allowed India to pick a team that answered one question. The other seven sides were answering five at once.

But — and this is the most important word in the piece — being allowed to choose is not the same as winning. The highest-leverage match of India's tournament in my sheet was not the group game against Bangladesh, where the cost of a defeat was low and the route to the semi-final barely changed. It was the semi-final against Australia, where one error ends the campaign. Virat Kohli's 84 in that match is the contribution I would rank highest, and for exactly the reason Sam Curran's 272 runs and 11 wickets outranked Kohli's 593 runs in 2026: after leverage adjustment, not raw addition.

The final tells a different story. New Zealand made 251/7, a defendable score in a Dubai evening. India reached 254/6 in the last over. Rohit Sharma's 76 was the spine of that chase, for a batter whose form across formats was being questioned at the time. But the line in my sheet that surprises me most is this: India's run rate between overs 20 and 40 in the final was higher than in any of their other four matches of the tournament. The biggest match produced their fastest middle overs. That is the kind of inverted signal I trust most, because playing better under pressure is not the product of a plan; it is the product of a habit.

Contrarian: the venue was not the cause; the batting and bowling were

Here I have to argue against myself, because correlation is not causation.

If playing five games on one ground were sufficient to win a Champions Trophy, India would not have lost the 2026 ODI World Cup final. That tournament was at home, India won nine straight, travelled little, and lost to Australia in Ahmedabad. A year later, in June 2026, India won the T20 World Cup on the most travel-heavy schedule available, from New York to Barbados. Both examples point the same way: relocation, or the absence of it, is not by itself a predictor of anything.

So what did Dubai do? My most honest answer is this: it lowered the floor of the possible; it did not raise the ceiling. It was a floor-raiser, not a ceiling-raiser. The risk of slipping against Bangladesh or Pakistan fell — and I think that shaped the tournament without colouring the trophy. The trophy was coloured by the bowling attack that was the most accurate on Dubai's surfaces and by the batting order that produced its best 20 overs in the biggest match.

And there is an uncomfortable point that Indian coverage largely skipped. This edge was not earned; it was negotiated, out of the December 2026 hybrid deal in which one board secured the assurance that none of its matches would be played on the host country's soil. Under the rules of the sport it is entirely legitimate. Under the rules of analysis it is a variable that was set to zero for one competitor — and if we do not measure it, we will keep filing these advantages away under team spirit.

How would my claim be falsified? Directly. If I compute India's per-match performance variance across their five games and it is not lower than the other teams', the variance-reduction argument dies. I tried to run it and could not: on n = 5 that calculation produces a delusion rather than a result. So it stays a hypothesis, published as one. That is the honest version, and I think it is worth more than a graph with three decimal places.

One more thing, from outside my sheet and inside the commentary box. The crowds for India's matches in Dubai were large, but they were not neighbourhood crowds; they were diaspora crowds that see this team once or twice a year and therefore treat every innings as a festival. That noise does not enter a statistic, but it was present at the ground. When I watch from a London box I have to remember that the word 'home' in my model means something different from what that crowd experienced. The model has to be walked to the stands, or the sheet stays clean and the truth goes missing.

Takeaway: the next tournament will repeat this experiment and we have no instrument for it

The 2026 T20 World Cup is in India and Sri Lanka. India will not have a single-venue arrangement there; they will move between eight cities, eight surfaces and eight sets of air. Which gives us a comparison: the same team, broadly the same leadership structure, twice the variables.

My prediction is that India's middle-over scoring rate falls below the Dubai figure and that their per-match variance widens, because the variables increase. If that does not happen, my whole variance-reduction framework goes in the bin, and I am willing to put it there.

So I want to propose something institutional rather than technical: before the next major tournament, publish a venue-residency index — a simple, checkable score for every team covering flights taken, total travel hours, number of venues used and reserve days available. I built that sheet for myself. It belongs in a press box, not in one person's file. Until it is public, we will keep asking the same question after every tournament and keep giving the same answer.

The real outcome in Dubai was that one team was given the chance to play five matches on one ground and used it fully. That is to their credit. But our job is to price what that chance was worth — and without that audit, every trophy is a half-told story. The sheet stays open. The question is who fills it next.