Karun Nair Scored 303 and Then Disappeared

Two Indians have scored a triple century in Test cricket. One of them is Virender Sehwag, who did it twice and is remembered accordingly. The other is Karun Nair, who did it once, in December 2016 at Chennai, in his third Test match, and played only three more Tests over the following nine years. There is no comparable case in the modern game — no other player anywhere has made 300 in a Test innings and then effectively vanished from international cricket for the better part of a decade.

The temptation is to file this as an injustice and move on. The more interesting reading is that Nair's career is a precise illustration of how Indian Test selection actually works: not as a meritocracy that rewards individual scores, but as a queue management problem in which timing matters more than runs, and in which the man who was picked as cover for an injury goes back to being cover when the injury heals.

The innings itself

England had made 477 in the final Test of the 2016-17 series and India, batting once, finished on 759 for 7. Nair came in at number five with the match already safe and batted for the better part of two days, finishing unbeaten on 303 from 381 balls, with 32 fours and four sixes — a strike rate a shade under 80, which for a triple century is rapid.

It was not a flawless innings, and the accounts written at the time were clear about that. He was dropped by Alastair Cook at slip on 34 and again by Joe Root when he had 217, and survived a stumping chance off Moeen Ali. Nor was it made in a difficult situation: India were already several hundred ahead when he reached three figures, on a surface offering the bowlers almost nothing by the fourth day.

Both of those qualifications are true, and neither is unusual. Most very large Test innings are made on flat pitches from positions of safety, and almost all of them include at least one let-off. What made this one remarkable was that it was Nair's maiden Test hundred, converted straight past 200 into 300 — a sequence with no other example in Test history from a player's first century.

Why it did not lead anywhere

Nair was in the side in the first place because Ajinkya Rahane had been injured. When Rahane recovered, Nair was the man who came out, which is exactly what a reserve batter is for. He toured, carried drinks, played one further Test in England in 2018, and then was not selected again.

The middle order he was trying to break into was, by any standard, close to impassable. Across the years immediately after Chennai, India's Test batting was some combination of Virat Kohli, Cheteshwar Pujara, Rahane, Rohit Sharma and later Shubman Gill, with a queue of contenders behind them. There was no vacancy for a batter whose record consisted of one enormous score and very little else, and the honest reading of his first-class numbers at the time is that they did not compel a place: solid, not overwhelming.

That is the part of the story usually skipped. Nair did not lose his place because of a conspiracy or a grudge. He lost it because a triple century is one innings, and Indian selection in that period had the luxury of not needing to gamble.

The years in between, and the run that changed the argument

What makes his case genuinely unusual is that he then did the thing players in his position are always told to do, and did it on a scale nobody was prepared for.

Having moved from Karnataka to Vidarbha, Nair produced a 2024-25 Vijay Hazare Trophy campaign that reads like a misprint. He top-scored the tournament with 779 runs in nine matches from eight innings, with five centuries, a best of 163 not out and a strike rate above 124. His average for the competition was 389.50, because he was dismissed twice in the whole tournament. Along the way he set a List A record for the most runs scored without being dismissed — 542.

Those are not the numbers of a player having a good season. They are the numbers of a batter who has become, for a period of months, essentially impossible to get out in that grade of cricket. He backed it up with heavy first-class scoring and an India A call-up, and the pressure on selectors became public: Anil Kumble, among others, argued openly that Nair was the natural answer at number four for the Test side once Kohli's place opened up.

The recall, and what it proved

He got it. Nair returned to the Test side for the 2025 series in England, eight and a half years after Chennai, and by his own subsequent description the return was up and down. He made 205 runs in four Tests, with one fifty, at an average of 25.62 — modest figures in a series played largely on flat surfaces and full of very large scores on both sides. He was left out for the West Indies series that followed, and the language in the coverage shifted quickly from a comeback story to a question about whether the road had ended.

There is no way to make that ending flattering, and it should not be made flattering. But it is worth being precise about what it does and does not prove. It does not prove the selectors were right in 2017 — a player is not retrospectively vindicated or condemned by his form at 33 for decisions made at 25. It also does not prove they were wrong. It proves something narrower and sadder: that a recall which arrives after eight years arrives to a different cricketer, in a different body, against a different bowling attack, with a weight of expectation nobody bats well under.

Compare the trajectory to a contemporary like Mayank Agarwal, who got his chance later but got it in a sustained run of matches. The difference between the two careers is not obviously talent. It is the number of consecutive Tests each was given.

The IPL career, and where it fits

Nair's IPL record is a fair reflection of a top-order batter who was always around and never quite indispensable: a little over 1,700 runs across eleven seasons, spread between Rajasthan Royals, Delhi Capitals, Punjab Kings and Royal Challengers Bengaluru. His 2025 season with Delhi, on the back of the Vijay Hazare run, produced several sharp innings and confirmed he could still hit at the required rate.

It is not the part of his record that carries an argument. Franchise cricket has never been where Nair's case is made — he is a first-class batter with a first-class temperament, and the Twenty20 numbers are the numbers of a competent professional rather than a specialist.

What the career is actually evidence of

Indian cricket produces more batters of Test standard than it has Test places, and it always has. That surplus is why the domestic game is strong and it is also why careers like this one exist: not failures, exactly, but records that stopped short of what they might have been because the queue moved in a different order.

Nair's is the extreme version, and the extremity is instructive. If a triple century in your third Test does not secure a place, nothing does — which tells you plainly that individual scores are not the currency of selection. Runs across a sustained run of matches are, and Nair was never given a sustained run of matches to score them in. When he finally forced the issue at 33 by making himself unignorable in domestic cricket, the game gave him four Tests, which is roughly the number he had already been given at 25.

Within the history of Indian cricket, the 303 will keep its place in the record books whatever happens next; it is the second-highest score by an Indian in Tests and one of very few triple centuries made anywhere. But the more useful thing his career leaves behind is a caution about how the game reads evidence. One vast innings is a fact. A place in a Test side is a judgement about a hundred other things, and the two have less to do with each other than anyone watching Chennai in 2016 would have assumed.