CRICMIND.AI
ANALYSIS

Tewatia's Five Sixes: How Rajasthan Chased 224 at Sharjah in 2020

September 27, 2020: Rajasthan Royals chased down 224 — the highest successful run chase in IPL history at the time — powered by Rahul Tewatia's five sixes off Sheldon Cottrell in a single, unforgettable over.

AI
CricMind AI
CricMind Intelligence Engine
··10 min read
Tewatia's Five Sixes: How Rajasthan Chased 224 at Sharjah in 2020

On September 27, 2020, Rajasthan Royals scored 224 in the fourth innings of their season and won a cricket match — the highest successful run chase in Indian Premier League history at that moment, and a total that had never before been overhauled on the biggest T20 stage. That it happened at Sharjah, a postage-stamp ground with boundaries a batter could almost reach out and touch, made the number believable. That it happened because a man who had scratched his way to 17 off 23 balls suddenly detonated five sixes in a single over made it immortal.

Rahul Tewatia's over against Sheldon Cottrell is one of those IPL moments frozen in the collective memory of a generation of fans — the batting equivalent of a jailbreak. It was not the cleanest innings, not the highest score, not even the winning knock in the technical sense. But it was the swing of momentum so violent, so improbable, that it turned a lost cause into folklore. This is the reconstruction of that night: how Rajasthan Royals walked to the edge of defeat against Kings XI Punjab and came back with the most audacious over the IPL had ever seen.

The Setup: A Sharjah Run-Fest

The 2020 IPL was played entirely in the United Arab Emirates, cricket having relocated to a bio-secure bubble in a pandemic year. Of the three venues used, Sharjah was the smallest and by some distance the most brutal on bowlers. Straight boundaries barely stretched past 55 metres. Mishits sailed for six. In that first fortnight, Sharjah became a byword for carnage, and Match 9 of the season would be its signature exhibit.

Mayank Agarwal's masterpiece

Kings XI Punjab batted first and simply refused to stop. Mayank Agarwal produced a maiden IPL century of controlled violence, reaching three figures off just 50 balls, while captain KL Rahul anchored at the other end with a composed 69. Their partnership dismantled the Rajasthan attack, and Punjab closed on 223 for 2 — a total that, on almost any ground in world cricket, is a match-winning score with a comfortable cushion to spare.

224 to win, and a slow start

The equation handed to Rajasthan was stark: 224 to win, 11.2 required per over from ball one, with no margin for a settling period. Steve Smith and Jos Buttler gave it early impetus, and Sanju Samson launched into a counter-attack of pure timing, but wickets kept falling in clusters. By the time Rahul Tewatia arrived, the required rate had climbed toward 14 an over and the innings was tilting away.

The 23 balls that nearly ended it

What is often forgotten in the legend is how badly Tewatia began. He could not middle a thing. Ball after ball squirted to fielders or thudded into the pitch. He crawled to 17 off 23 deliveries at a strike rate barely above 70 — an anchor the chase could not afford, in a phase where every dot was a small death. Commentators questioned why he had been promoted. Rajasthan supporters watching from home had, by any rational read of the scoreboard, already lost the match.

Why Sharjah broke the math

Context matters, and Sharjah's context was extreme. The ground's short square and straight boundaries meant that the usual T20 arithmetic — where a required rate of 14 an over is a near-guarantee of defeat — simply did not apply. A batter did not need to middle the ball to clear the rope; a top edge or a mistimed slog could carry the fence. This is the crucial subtext to Tewatia's over: it was audacious, yes, but it was also played at the one venue on earth where such audacity had the highest chance of paying off. The genius was in the intent — the willingness to swing through the ball when survival instinct screamed for caution — more than in the timing.

The Over That Rewrote the Night

The 18th over. Sheldon Cottrell — Punjab's West Indian left-armer, famous for his crisp military salute after every wicket — running in to a batsman who had done nothing all evening. What followed was the most violent single over in IPL folklore.

Six. Six. A dot. Six. Six. Six. Tewatia struck Cottrell for five sixes in the over, dragging 30 runs from six balls and, in ninety seconds, hauling a dead chase back to life. The man who could not middle the ball was suddenly clearing the ropes at will, each strike louder than the last, the Rajasthan dugout erupting. A required equation that had read impossible was now merely difficult — and at Sharjah, difficult was survivable.

Rajasthan needed a cool head to finish, and Jofra Archer supplied the exclamation mark, a towering six late in the innings sealing the target with three balls to spare. Rajasthan Royals had chased 224 and won by four wickets. The scoreboard read like a misprint. It was not.

The human story underneath the numbers is what gave the night its staying power. Cottrell, a bowler who had built a reputation on his celebratory salute, walked off having conceded 30 in an over he will never forget for the wrong reasons. Tewatia, dropped and doubted for two-thirds of his innings, walked off a folk hero whose name would be invoked every time a struggling batter was given one more over to find his range. In the theatre of T20, few reversals have been so complete or so public.

The Numbers Behind the Chaos

To understand how extraordinary the result was, the two innings are worth laying side by side. Punjab's total was built on a single towering century; Rajasthan's answer was a relay of aggressive cameos, glued together by one over of madness.

Kings XI Punjab — 223/2

BatterRunsBallsStrike Rate
Mayank Agarwal10650212.0
KL Rahul6954127.8
Nicholas Pooran8*4200.0
Karun Nair15*8187.5

Rajasthan Royals — 226/6, won by 4 wickets

BatterRunsBallsStrike Rate
Sanju Samson8542202.4
Steve Smith5027185.2
Rahul Tewatia5331171.0
Jos Buttler2215146.7
Jofra Archer13*3433.3

Sanju Samson's 85 off 42 was, in cold statistical terms, the innings that top-scored and kept Rajasthan in touch through the middle overs. Steve Smith's fifty set the tempo. But it was Tewatia's 53 off 31 — and specifically the 30 runs pillaged from a single over — that flipped the win-probability curve from near-zero to favourite in the space of six deliveries.

A record chase in context

The 224 chased that night was the highest successful run chase in IPL history at the time, and it stood as the benchmark for several seasons before the format's relentless inflation of scores finally surpassed it.

Target ChasedChasing TeamOpponentVenueSeason
262Punjab KingsKolkata Knight RidersEden Gardens2024
224Rajasthan RoyalsKings XI PunjabSharjah2020
223Rajasthan RoyalsKolkata Knight RidersEden Gardens2024

The symmetry is almost poetic: the franchise that redrew the ceiling for run chases in 2020 was also involved, on both sides of the ledger, in the games that later broke it. Sharjah 2020 was the moment the IPL collectively realised that no total was truly safe.

Legacy: What Tewatia's Over Means in 2026

Six years on, the fingerprints of that night are all over how the IPL is played. The chase-anything mentality that now defines the tournament — where a batting side treats 220 as a par target rather than a mountain — traces a clear line back to Sharjah 2020. Franchises rebuilt their middle orders around the idea that a single over of controlled hitting can erase a required rate, and that a batter having a poor day should be backed to explode rather than benched.

Rahul Tewatia's redemption arc also reshaped how teams value the finisher who fails beautifully. A player can be 17 off 23 and still be one over away from hero status; the modern IPL is more forgiving of the slow start precisely because everyone remembers what came next that night. Sanju Samson, who anchored the Rajasthan chase with 85 that evening, carried that fearless template through the rest of his career and remains one of the most destructive top-order forces in the league heading into IPL 2026.

This is also exactly the kind of momentum swing that separates a good prediction model from a great one. CricMind's Oracle engine does not treat a chase as decided until the mathematics genuinely say so — its live micro-layer recalculates win probability ball by ball, meaning an over like Tewatia's would have registered as one of the sharpest single-over probability shifts the system tracks, the curve lurching from near-certain defeat back toward a coin flip in the span of thirty runs. The lesson the Oracle encodes is the lesson Sharjah taught: at these venues, with this brand of hitting, the game is never over.

There is a broader tactical inheritance too. Since 2020, franchises have leaned harder into batting depth, pushing genuine hitters down to numbers seven and eight so that a collapse never fully closes the door. The "impact" mindset — that any single player, on any single ball, can rewrite the equation — is now baked into auction strategy, playing-XI selection, and in-game field settings. When a captain in IPL 2026 keeps a boundary rider back in the eighteenth over of a chase that looks already won, some part of that caution is a ghost of Sharjah, September 2020.

Three Takeaways

  • No total is safe at a small ground. Sharjah 2020 proved that 223 could be chased down, and the psychological ceiling on run chases has been rising ever since — 262 has now been overhauled in a completed IPL match.
  • A slow start is not a lost cause. Tewatia's transformation from 17 off 23 to match-winner in one over is the definitive case study in why modern teams back their finishers through a bad patch rather than panic.
  • Momentum in T20 is non-linear. A single over can move a match further than the previous fifteen combined — which is precisely why ball-by-ball probability tracking matters more than a static pre-match number.

Frequently Asked Questions

What was the final score of the 2020 RR vs KXIP Sharjah match?

Kings XI Punjab posted 223 for 2, and Rajasthan Royals chased it down, winning by four wickets with balls to spare. The 224 target was the highest successful run chase in IPL history at the time.

How many sixes did Rahul Tewatia hit in the over off Sheldon Cottrell?

Tewatia struck Sheldon Cottrell for five sixes in the 18th over, taking 30 runs from the six deliveries and swinging the chase decisively back in Rajasthan's favour.

Who scored a century in that match?

Mayank Agarwal scored a maiden IPL century for Kings XI Punjab, reaching 106 off just 50 balls, while captain KL Rahul supported him with 69.

Was 224 the highest run chase in IPL history?

Yes, at the time. Rajasthan's chase of 224 stood as the highest successful run chase in the IPL until Punjab Kings chased 262 against Kolkata Knight Riders at Eden Gardens in 2024.

Who top-scored for Rajasthan Royals in the chase?

Sanju Samson top-scored with 85 off 42 balls, anchoring the chase, while Steve Smith made 50 and Rahul Tewatia contributed the decisive 53 off 31.

Where was the 2020 match played?

The match was played at the Sharjah Cricket Stadium in the United Arab Emirates, one of three venues used during the pandemic-relocated IPL 2020 season and by far the most favourable to batters.

Why is this match considered legendary?

It combined the highest run chase in IPL history at the time with one of the most dramatic individual overs the tournament has ever seen — Tewatia's five sixes — turning a near-certain defeat into an iconic victory in the space of a single over.

SHARE THIS ARTICLE
This article uses statistical insights generated by the Cricmind analytics engine. AI-generated analysis for entertainment and informational purposes.
TOPICS
Rahul Tewatia five sixesRR vs KXIP 2020 Sharjahhighest run chase IPLIPL historyIPL recordscricket analysis IPL
GET THE FULL AI PREDICTION
Cricmind analyses 278,205 IPL deliveries to predict every match outcome with confidence scores and key factor breakdowns.
VIEW PREDICTIONSMORE ARTICLES
MORE IN ANALYSIS
Editorial Standards

This article was produced by the CricMind Sports Editor, CricMind.ai's AI-assisted editorial identity. All predictions are generated by the Oracle engine and stored immutably before the match. Statistical claims are verified against the IPL 2008-2026 ball-by-ball dataset.

Read our Publication Policy · About CricMind · Contact