From 70/5 to 181: Tilak Varma's 51* Was a Win, Not a Solution

Before the 19th over began at that vast Christchurch ground, Tilak Varma was on 17 off 13 balls — a strike rate of 131, which reads slow for the back end of a T20. India were 70/5, chasing 181, and the only set batter at the crease was a 23-year-old left-hander. Nathan Smith came on to bowl that over and it cost 18 runs. Tilak's numbers changed from there: 51 not out off 26, a strike rate of 196.2, and 34 runs off his last 13 balls — roughly 262.

The scorecard says India won by four wickets with a ball to spare and moved 2-0 up in a five-match series. I watched it the way the offshore reader does, at three in the morning in Sydney, and what the scorecard was not saying is this: the win came from one innings, and that innings covered a crack the same slow pitch will reopen next time.

Context: a three-phase game, and India falling in the middle overs

T20 splits into powerplay (1–6), middle overs (7–15) and death overs (16–20). India's 70/5 is not the story of one good delivery; it is a middle-overs failure, and everything after it belonged entirely to the death phase. Christchurch is a big ground — Tilak himself calls it “this huge ground” — and the pitch, in his words, was “slower.” Around 361 runs were scored across both innings, which tells you this was not a surface where aerial hitting alone gets you home. On a track like that, running hard and finding gaps is worth more than clearing the rope.

Now the arithmetic nobody printed but the scorecard hands you. The target was 181, India had lost five wickets for 70 — 111 still needed. The stand with Dhir was 42 off 24 balls; the unbeaten stand with Nitish Kumar Reddy was 69. Forty-two and 69 make exactly 111. The entire chase was completed in two partnerships — this is the story of two pairs, not of a team. That is why the four-wicket margin and the 2-0 lead, taken together, look far more comfortable than they were.

Core: pricing risk on a slow pitch

What Tilak said afterwards is unusually mature for his age. Against spin he was not taking risk, he said — he was looking for gaps and running hard — and when pace arrived, he attacked. This is the oldest and least-used template for a big ground and a slow pitch: control against spin, assault against pace. Most young batters do the opposite — rushing to loft spinners and defending against the quick.

The numbers follow that sequence. Seventeen off his first 13 balls, almost risk-free, all gaps and running. Then 34 off his last 13 — same batter, same pitch, double the speed. In T20 the real signature of a finisher is that late surge after a quiet start, not a boundary off ball one. Two boundaries came in the 18th over, 18 runs came off Nathan Smith in the 19th, and 11 were needed off the last six. The “thriller” was less tight than the cold Christchurch air made it sound; by the final over the pressure sat entirely with India, and Mitchell Santner's last over was a captain's over with nothing left to defend.

From my years of watching matches, the most valuable skill on a big ground is the one commentary never replays — the acceleration of the third stride for a second run, and the way Tilak kept sprinting at the non-striker's end to turn singles into doubles. Some matches are won by deliveries you never see on the broadcast; here they were the defensive pushes that add nothing to the scoreboard in the moment and build the platform for the assault two overs later.

The pairing with Nitish Kumar Reddy has been framed as “the Hyderabadi boys.” It is a warm human detail and a good team-culture story, and it carries little analytical weight. The diagram looked simple until the final ball rewrote it.

Contrarian: what the four-wicket margin hides

Winning from 70/5 with a ball to spare is evidence of a rescue, not of dominance. In an innings where the first five wickets fell for 70, the real news is not the lower order's courage but the top order's fragility. The fault was not one batter's — the shape of the batting order was wrong, and Tilak was simply the right man standing inside it. That distinction matters, because one event can support two opposite readings: “India's bench is deep” and “India's top order can collapse on a slow pitch.” Both are true, and the second is more useful than the first.

Labels like “the finisher's role” get attached very quickly after one innings. Fifty-one not out off 26 is genuinely match-winning, but it is a data point, not a trend. His next two knocks in this series will decide whether the role is real or a single night's work.

One more thing absent from the report: the toss, dew, a dropped catch, a DRS call — none of it is recorded. In a match that runs to the last ball, those small things are exactly what swing results. Treating this win as proof of structural strength would be premature; it was a momentum-driven rescue in which one batter carried the whole risk. Indian cricket media is very efficient at turning a young match-winner into a superstar, and the temperature here is warm — the distance to “next big thing” is still unbridged.

Takeaway: the next three innings answer the question

Across the remaining T20Is I will watch two things: India's score at the fall of the third wicket, and the character of the pitch. If India lose three inside 80 on another slow surface, that becomes a pattern and the word “solution” has to be retired. If Tilak's strike rate sits below 150 on a flat deck, the same question returns from the other side. I keep eleven diagrams beside me because the game always leaves a twelfth in the air. The question is not whether India lead 2-0; it is whose rescue those ten overs from 70/5 will be next time.