IPL Seasons in the UAE: 2014, 2020 and 2021 Analysed
10 min read2,267 words
The Indian Premier League has left India four times. Once for South Africa, and three times for the Gulf. Those three visits, in 2014, 2020 and 2021, produced 111 matches across Dubai, Abu Dhabi and Sharjah, and they are the single most valuable body of evidence anyone has about what these pitches do to Twenty20 cricket. The same franchises, the same players and the same regulations, transplanted twice inside eighteen months.
We have every delivery of it. What follows is drawn from our own ball-by-ball database, and the numbers are ours unless stated otherwise.
Three visits, three different reasons
2014: an election
India held a general election in the spring of 2014. Polling in a country of that size consumes the security apparatus for weeks, and the state police forces that a stadium fixture requires were unavailable. Rather than compress or cancel, the Indian Premier League moved the opening phase abroad.
Twenty matches were played across the three Emirati grounds before the tournament returned to India for the remaining forty. Our records place seven at Dubai, seven at Abu Dhabi and six at Sharjah. Kolkata Knight Riders took the title once the season was back on home soil.
2020: a pandemic
The second move was total. Covid-19 made a normal Indian season impossible, and the league relocated in full, playing all sixty matches in the Emirates across an autumn window rather than the usual spring one. Our data splits them 26 at Dubai, 22 at Abu Dhabi and 12 at Sharjah. Mumbai Indians won the final at Dubai.
It remains the most complete relocation any major franchise league has managed. Sixty matches, eight squads, a bio-secure environment, a full broadcast, and not a fixture lost.
2021: a broken bubble
The third was an emergency. The 2021 season began in India and was suspended in May after the bio-secure environment failed and cases appeared inside team camps. The tournament resumed in September in the Gulf and finished there.
That accident of scheduling produced the cleanest natural experiment in franchise cricket. Twenty-nine matches in India and thirty-one in the Emirates, in the same season, with the same squads, the same regulations and largely the same personnel. Whatever the difference between the two legs is, it is not selection. Chennai Super Kings won the final in Dubai.
What the scoring actually shows
Start with the aggregate. Across every IPL season we hold, the comparison looks like this.
| Measure | Emirati grounds | Indian grounds |
|---|---|---|
| Matches | 111 | 1,044 |
| Runs per over | 8.00 | 8.53 |
| Average first-innings total | 160.9 | 169.5 |
| Sixes per match | 11.0 | 12.9 |
| Wickets per match | 11.6 | 11.8 |
| Powerplay run rate | 7.56 | 8.14 |
| Death-overs run rate | 9.61 | 10.13 |
| First innings of 200 or more | 9.9% | 18.1% |
Half a run an over, nine runs on a first-innings total, and roughly half the rate of 200-plus scores. That last line is the one that captures how the cricket felt: a big total in the Emirates was a rarity, where in India it became routine.
One caveat has to be attached to that table. The Indian column spans every season from 2008 to the present, including the recent run of seasons in which scoring has exploded, so it flatters the comparison. The fair test is not all-time; it is within-season, and we have two of those.
The 2021 split
This is the single most instructive pair of columns in our entire IPL dataset.
| Measure | 2021 in India (29 matches) | 2021 in the Emirates (31 matches) |
|---|---|---|
| Runs per over | 8.41 | 7.71 |
| Average first-innings total | 168.5 | 150.7 |
| Sixes per match | 13.1 | 9.9 |
| Powerplay run rate | 7.70 | 7.73 |
| Death-overs run rate | 10.10 | 8.74 |
| Chases won | 57% | 68% |
Same season. Same squads. Eighteen runs off the average first-innings total.
The most revealing line is not the headline rate. It is the powerplay, which barely moved at all. Batters scored at essentially the same rate in the first six overs in both countries. Everything that was lost was lost afterwards, and the collapse at the death is severe: from 10.10 to 8.74, well over a run an over, in the phase where matches are decided.
That is a specific diagnosis rather than a general one. The new ball came onto the bat here as normally as it does anywhere. The problem started once the ball was thirty overs old, soft, and being bowled into a slow surface with a long boundary square of the wicket. The shots that clear a rope in Mumbai in the eighteenth over were finding the fielder forty metres in.
The chasing figures point the same way. Sixty-eight per cent of matches in the Emirati leg were won by the side batting second, against fifty-seven in the Indian leg of the same season. Evening dew in the Gulf is heavy in the autumn, and a wet ball at the death takes away exactly the weapons that were already struggling: grip, spin and the slower ball.
The 2014 split
The other within-season comparison, from a decade earlier, tells a compatible story with one difference.
| Measure | 2014 in India (40 matches) | 2014 in the Emirates (20 matches) |
|---|---|---|
| Runs per over | 8.52 | 7.57 |
| Average first-innings total | 169.0 | 151.2 |
| Sixes per match | 13.5 | 8.7 |
| Powerplay run rate | 7.95 | 6.80 |
| Death-overs run rate | 10.48 | 9.12 |
Almost exactly the same gap in the headline numbers, roughly a run an over and eighteen on a first-innings total. But in 2014 the powerplay fell too, and fell hard. Those were April matches, played at the start of a season on squares that had not been used for franchise cricket, and the ball did more early.
2020 is the exception
Given the two splits above, the 2020 season should have been a low-scoring one. It was not.
| Measure | 2020 (all in the Emirates) | 2019 (all in India) |
|---|---|---|
| Runs per over | 8.29 | 8.42 |
| Average first-innings total | 169.5 | 166.7 |
| Sixes per match | 12.3 | 13.1 |
| Death-overs run rate | 10.20 | 10.17 |
A full sixty-match season on these grounds scored at very nearly Indian rates, with a higher average first-innings total than the Indian season that preceded it and an identical death-overs rate.
Three things explain it, and all three are visible in our venue splits.
The squares were fresh. These pitches had been comparatively lightly used through the first half of 2020, and a season that began on rested surfaces started fast.
The load was spread. Sixty matches across three grounds is twenty apiece; the same volume concentrated on fewer squares degrades much faster.
And Sharjah happened. In 2020 the smallest ground in the country produced the highest-scoring venue-season in our entire Emirati sample: 8.87 runs per over and 18.3 sixes per match across twelve fixtures, with an average first-innings total near 178. Short square boundaries, a good surface and a batting-heavy tournament combined into something close to a demolition derby, and it dragged the whole season's numbers upward.
Ground by ground, season by season
The venue table shows how much these surfaces change between visits, which is the finding that matters most for anyone projecting future cricket here.
| Ground | Season | Matches | Runs per over | Avg 1st innings | Sixes per match |
|---|---|---|---|---|---|
| Abu Dhabi | 2014 | 7 | 7.37 | 147.4 | 5.7 |
| Dubai | 2014 | 7 | 7.51 | 148.9 | 8.3 |
| Sharjah | 2014 | 6 | 7.85 | 158.2 | 12.7 |
| Abu Dhabi | 2020 | 22 | 8.09 | 162.5 | 9.8 |
| Dubai | 2020 | 26 | 8.19 | 171.5 | 11.6 |
| Sharjah | 2020 | 12 | 8.87 | 177.9 | 18.3 |
| Abu Dhabi | 2021 | 8 | 8.23 | 159.0 | 9.1 |
| Dubai | 2021 | 13 | 7.93 | 156.2 | 10.5 |
| Sharjah | 2021 | 10 | 7.01 | 136.9 | 9.8 |
Sharjah is the story. In 2020 it was the most productive batting venue in the sample by a distance. Ten months later, in the same competition, it was the least productive venue-season in the sample by a distance: 7.01 an over and an average first-innings total under 140. A ground that had produced 18.3 sixes a match was producing 9.8.
Nothing about the boundary changed. What changed was the square, which had been through a compressed sixty-match season plus everything else staged there in between, and by the autumn of 2021 it was slow, tired and gripping. Anyone reading these grounds as fixed quantities will get them badly wrong; the physical background to that is covered in the explainer on pitch types, and the individual venue characteristics in the guide to the three stadiums.
How the franchises fared
Across all 111 Emirati matches in our records, the win rates were tighter than the conditions might suggest.
| Franchise | Matches in the Emirates | Won | Win rate |
|---|---|---|---|
| Chennai Super Kings | 28 | 16 | 57% |
| Kolkata Knight Riders | 29 | 15 | 52% |
| Punjab (both identities) | 25 | 13 | 52% |
| Mumbai Indians | 28 | 14 | 50% |
| Delhi (both identities) | 30 | 14 | 47% |
| Royal Challengers Bangalore | 28 | 12 | 43% |
| Sunrisers Hyderabad | 28 | 12 | 43% |
| Rajasthan Royals | 26 | 10 | 38% |
Chennai's record is the one that fits the theory. A squad built around spin, low-risk accumulation and disciplined death bowling should travel well to slow, low surfaces, and it did, culminating in a title in 2021 on precisely the pitches that punished more aggressive teams. Rajasthan Royals sit at the other end, having won barely more than a third of their matches here.
Read those figures with some care, though. A hundred and eleven matches divided among ten franchises leaves sample sizes in the twenties, which is small enough that a couple of tight finishes move a team several places. The gap between the top and bottom of that table is nineteen percentage points across roughly twenty-seven matches each, which is a handful of results rather than a law of nature. What the table does establish is that no franchise found these conditions impossible and none found them free. Selection mattered more than reputation, and the sides that picked a second front-line spinner for the Emirati leg generally looked better prepared than the sides that picked a fourth seamer. Anyone building a hypothetical side for these grounds can test that instinct against the playing XI tool.
What it meant for the cricket
Three practical consequences, all of which showed up repeatedly in those seasons.
Par moved. A total that would have been thirty short in India was competitive here, and captains who kept setting Indian targets kept getting them wrong. The sides that adjusted fastest tended to be the ones with a settled spin plan.
Spin got promoted. Wrist spinners and finger spinners bowled more of the middle overs than they would have at home, and did it with better returns, because the surfaces held up the ball and the boundaries square of the wicket demanded a properly middled stroke.
And the toss mattered more, particularly in the autumn windows. Dew is a strategic fact in the Gulf, not a footnote, and the chasing records reflect it.
Anyone who watched all three visits will also have noticed the other thing, which no dataset captures. The stands were largely empty in 2020 and thinly filled otherwise, and the atmosphere of a league built on noise was replaced by the sound of the game itself. The grounds were the same ones that had absorbed Pakistan's home cricket through the previous decade in similar silence, and the same ones that now stage the International League T20 in January.
The wider account of how this country became the sport's standing fallback is in the neutral venue history. What the IPL's three visits added was proof that the arrangement could scale, and a body of data that shows exactly what it costs a batting side to leave India.
Season-by-season records for every franchise sit on the league hub, individual careers in the player index, and the rest of the region's cricket on the regional hub.
Sources and method
Every scoring figure, table and win rate in this guide is computed by us from our own ball-by-ball database of Indian Premier League deliveries, covering all seasons and every venue: 111 matches at Dubai, Abu Dhabi and Sharjah, and 1,044 at Indian grounds. Run rates exclude wides and no-balls from the ball count and include all extras in the runs. Phase splits use the standard powerplay and death-overs definitions carried in our data. Match counts, venues and champions have been cross-checked against published scorecards. The reasons for each relocation are taken from board and league announcements at the time.