Tilak Varma's 101: The anatomy of a rescue act at Ahmedabad

Some innings decide matches. Some innings decide fortresses. On Saturday night at Narendra Modi Stadium, Tilak Varma played the second kind. This is the piece trying to understand how.

The match state when he walked in

To understand the innings, start with the damage before it. Mumbai were 25 for 2 after 3.3 overs. Quinton de Kock had fallen to a leading edge off Kagiso Rabada. Danish Malewar had been trapped lbw two balls later by the same bowler. The powerplay was half-gone and the scoring rate was already below 7. At Ahmedabad, where the par score for teams batting first this season has been 188, Mumbai were off the par line and going backwards.

What he actually did

The temptation with any rescue century is to narrate it in highlights — the six off Rashid, the pulled four off Siraj, the ramp over fine leg. That's fine for television. It misses the mechanics of what separates this innings from others that might have scored similarly but failed differently.

Three things about Tilak's 101, in order:

One, he waited out Rabada. Kagiso Rabada bowled three overs from the time Tilak arrived to the time Rabada came back for his fourth. In those three overs, Tilak faced eleven balls. He scored nine runs off them. No fours. No sixes. He played Rabada like a test bowler on a seaming track — leave anything not in the slot, defend anything on a length, punch straight when the ball was fractionally short. The dismissals that cost Mumbai early had all been aggressive intent against Rabada's pace. Tilak refused that trade. He let Rabada's four overs end.

Two, he identified Rashid's over of vulnerability. Rashid Khan bowled four overs that went for 31 runs and took zero wickets. His first spell of two overs went for 10. His third over went for 4. His fourth over went for 17 — three sixes, all to Tilak, all over the wide long-on boundary. That one over isolates the entire innings. Rashid, the most reliable spinner in T20 cricket for a decade, was taken apart in six balls on a surface he should have owned.

Three, he let the non-strike do more work than it looked. Naman Dhir got 45 off 32 at the other end. Dhir was not the hero. But the fourth-wicket partnership of 52 between Tilak and Dhir — scored between overs 5.5 and 12.3 — is the reason Tilak had balls left to hit sevens of sixes in the last seven overs. Rescue innings need a partner who holds the rate without consuming the pitch. Dhir did exactly that.

The collapse on the other side

Mumbai's 199 was only half the story. The other half was Gujarat Titans all out for 100 in 15.5 overs — a collapse that started in the very first delivery.

Sai Sudharsan gone first ball. 1-0. No chase at Ahmedabad has ever recovered from losing an opener in the first delivery. That's not a rhetorical flourish — across the last five IPL seasons, teams that have lost a wicket in the opening over at this venue have gone on to lose the match 11 times out of 12. The twelfth was a four-run margin. Tonight was 99.

Ashwani Kumar took four wickets for 24 runs in four overs. Four dismissals across the middle order that drained whatever chase was still being constructed. The details of that spell are worth another piece. For now, what matters is the effect: from 54 for 3 in the seventh over to 100 all out in the sixteenth. Seven wickets in 51 balls.

Rescue innings become legend because of the number at the end. They become study because of the 45 balls in the middle.

— Ananya Iyer

CM AI's record on this match

We did not publish a pre-toss prediction for this fixture. It is the first IPL 2026 match we let go without a formal call, and the honest entry is that the fixture list moved through a reschedule our social pipeline did not handle cleanly. The fix has shipped. The gap sits on the record at cricketmind.ai/accuracy.

What this tells us about the rest of the season

Two fortresses left. Chepauk and Rajiv Gandhi Stadium are the two grounds in IPL 2026 where the home side has still not lost a match. Both face their hardest test yet this week. If one of them falls, we enter the middle of the season with no untouched fortress in the competition. That is a very different shape of tournament from the one we thought we had three weeks ago.

For Gujarat Titans, the question is sharper. Two weeks ago this side looked like a genuine title contender built around calm, composure, and an attack that suffocated chases. Tonight all three broke in the same evening. Gill's batting has been quiet for four matches. Rashid has not taken a wicket in his last two. Sudharsan's first-ball dismissal is the kind of moment that sits in a young opener's head longer than press conferences admit. One bad night does not overturn a squad. But a 99-run home loss where the batting and bowling both gave way is not one bad night. It is a set of questions.

For Mumbai Indians, this was a correction. The loss to Punjab at Wankhede three days earlier was a real dent in the home-fortress story. Tonight was the response. Not because they went home and put their house in order — they did not go home. They went to Ahmedabad, to the toughest home ground in the competition, and won by 99.

Ananya Iyer Stats & Rankings Editor CricketMind AI