102 off 43: Shreyas Iyer Breaks Kohli's Record in Lucknow's Night Air, Babar Still Ahead

Dew and the Required Rate

On Tuesday evening at Lucknow's Ekana Stadium, the dew had just begun to settle as India's innings crossed its midpoint. The 172 West Indies had set was not a huge target in T20I terms, but the Ekana surface is nobody's comfort zone — the ball sometimes stops, sometimes rears to shoulder height. Watching from my Delhi flat, I kept an eye on the small required-rate figure blinking beside the scoreboard and how quickly it moved. At the crease was Shreyas Iyer, batting at number four — the most unforgiving region of the game, where spin operates, the ball is old, and holding tempo is hardest.

What followed is not the story of a single innings. 102 not out off 43 balls. Ten fours, six sixes. A strike rate of 237.2. In other words, nearly five runs every two deliveries. In the middle phase of a T20I, where finishers are usually content with 160 to 180, 237 speaks a different language. And 74.5 percent of those runs came from boundaries — 76 of 102 runs in fours and sixes alone. This is not the innings of an accumulator. This is the innings of a batter who refused to smother spin into the infield and chose to send it beyond the rope. From a Delhi sofa, I learned that tactics can make a grown fan weep — and on Tuesday night there was plenty to weep about.

But a fan's tears and a record's arithmetic are not the same thing. To reconcile the headline with the reality of the pitch, we need to peel back a few layers.

The Lucknow Context

The match was the first of a bilateral T20I series against West Indies, on Indian soil. The series itself is not a major tournament, but it is the run-in to one. In a crowded national schedule, bilaterals are now a window for experimentation — who can lead, who can hold number four, who can bowl at the death. Iyer captained this match, and that is the most important piece of information. When a middle-order batter both runs the team and scores a century at four, it is not merely a personal feat — it is a statement about the team's structure.

West Indies must be seen separately here. Two-time T20 world champions, but their bilateral consistency has been on a downward slope for a while. So this century carries real weight, yet measured against the opponent's tier and the familiar home environment, this innings cannot be called 'proven under all conditions.' T20 arithmetic can be merciless: the same score on a familiar surface and against foreign pace does not always carry the same meaning.

One more thing caught my eye — the toss and the dew. In an evening match, dew favours the chasing side; the ball comes on better, bowlers lose grip. The Stage-1 description does not explicitly mention dew, so this is my inference. But reading Ekana's evening air against a 172 target, it seems the second innings got somewhat easier for batting. Iyer finished the job in 43 balls, suggesting the team was rarely in serious danger — and the eight-wicket margin points the same way.

What the Numbers Say

Iyer's 102 not out is the perfect template of a power-hitting number four — a strike rate of 237.2 with 74.5 percent of runs from boundaries. These two numbers must be read together. Look only at the runs and you miss the tempo. Look only at the strike rate and you miss the durability. Together they show Iyer did not merely attack — he sustained that attack across the middle of an innings.

The comparison lands directly on Virat Kohli. Kohli's previous best chasing innings as India captain was 94 off 50, a strike rate of 188. Iyer passed that mark by eight runs and moved 49 strike-rate points ahead. But the limits of this comparison must be stated plainly: this is a chase-specific and India-captain-specific comparison — it does not license the conclusion that Iyer is a bigger T20I batter than Kohli. Kohli's 94 came in an entirely different match context, on a different pitch, under different circumstances.

Then comes Babar Azam. Babar's best chase score is 122 off 59, a strike rate of 206.8. Babar leads on runs, Iyer leads on tempo. Here lies the biggest error: the record Iyer broke is a volume record, not a rate record. Babar's 122 and Iyer's 102 are not the same kind of innings. One faced more balls for a bigger score; the other scored faster on fewer balls to close the game. They cannot be judged on one ruler.

There is another layer. Iyer is the third Indian captain to score a T20I century, and seventh on the all-time chase list. That seventh place is not stable — a new innings reorders it.

Most useful of all is the batting position. A century at number four means either the top three functioned without dominating, or Iyer's innings was the load-bearing one. In T20, number four means the powerplay is over, spin is active, the ball is old. Scoring 102 there is not just skill — it is match-reading.

What the Headline Leaves Out

This is the uncomfortable part that highlight reels skip. The 'record' broken is 'highest score by a captain while chasing' — not an official ICC category, but a media-defined sub-class. Omit the chasing qualifier and a reader easily assumes it is the all-time overall record. It is not. Include first-innings batting and the top of the list may look different.

The second problem is sample size. One match, one innings — that is a milestone, not a trend. Career average and the last 12 months of form are absent from Stage-1. So 'Iyer's form has changed' cannot be said on this information. A single century does not move a career baseline. The next five to ten innings must be watched.

The third problem is home-soil inflation. Ekana's two-paced surface generally favours bowlers, but a familiar environment, familiar conditions and a comparatively weaker opponent can make an innings look bigger than it is. Score the same against foreign pace, on a difficult pitch, under real pressure, and the reckoning changes.

The fourth problem is the body. Iyer has a documented back-injury history, and he is now batting and captaining — a dual load that raises format-management questions. That detail is not in Stage-1; it is my general observation. Still, a batting captain's workload warrants caution.

The fifth and subtlest problem is the succession narrative. The headline 'breaks Kohli's record' borrows Kohli's halo to inflate one innings. The Kohli comparison is record-relative, not ability-relative. The real story is 'a career-best moment,' not a 'coronation.'

The sixth problem is verification. Every data point here sits at 'Source: None' in Stage-1 — the captaincy fact and the record hierarchy are both single-source and unverified. These numbers should not be cited without cross-checking ESPNcricinfo or official ICC stats.

Now a word on the crowd. The empty stands still had a pulse if you knew where to press. On Tuesday, Lucknow's stands were not empty, but inside that sound was an impatient waiting — every over, fans asked whether the rate was climbing. When Iyer hit sixes, the noise was relief, not celebration. That tells you this Lucknow innings was really a pressure-release innings — and that is nothing to belittle.

Let me add a memory. In 2026, after Sunil Chhetri's hat-trick at the Intercontinental Cup in Mumbai, he posted a video appeal; the next match drew 35,000 fans. I was running from the locker room to the training ground collecting fan chants. I kept listening for the crowd that Chhetri carried with him. On Tuesday in Lucknow I was doing the same — listening for what the fans screamed as Iyer's innings ended, and whether it was truly the announcement of a new era or the thrill of one night.

This caution is against myself. At 64, I know my biggest weakness is dependence on fan approval. It feels good to inflate an innings, because a bigger headline means more reading, and more reading means more applause. But writing cricket from an India base after being born in Bangladesh, I have learned one thing — when writing about a player who turns out for India, the fan's emotion and the statistic's truth must be kept apart. Otherwise we write the story of a coronation where there was, in fact, one extraordinary innings.

What to Watch Next

The question now is what to hold on to from this innings. The answer is clear to me. Watch the next five to ten T20I innings. If the strike rate stays above 150, then this was no one-night flash. If the captaincy persists into the next series, the story shifts from record to role. And if a rest or withdrawal appears in any match, the shadow of the back injury returns.

Keep an eye on Babar's 122. A new chase score reorders the list. And watch Iyer on overseas tours — that is what tests the home-soil thesis.

One question still hangs in my hand. Did 102 off 43 open a new door for Iyer, or did he merely pose for a photo in front of one? The answer will be written in the next innings, not in the headline. Because in T20, the most credible language is not statistics but consistency — and consistency alone answers the questions that a single night's thrill never can.