Not 228 but 18: The Colombo Number That Actually Explains India vs Pakistan

It was 10 September 2026, the R. Premadasa Stadium in Colombo. I was sitting in my Kolkata flat with the stream open on a laptop and the television muted. Across the wall my neighbour's TV was running two seconds behind, which meant every ball reached me twice — once on the screen, in silence, and once through the wall, carrying somebody else's hope.

At about 9:40 pm the scoreboard held three numbers. Pakistan 128. All out. And beside it, in a smaller font: 32 overs.

The third number was the quietest and the loudest. Pakistan had 18 overs left. Nobody bowled them. Nobody batted them. By the next morning no headline carried them. The 228-run gap that the night displayed — India's largest ODI win over Pakistan by runs — was not 228. It was 18.

I turned the volume down and finally heard the game.

Context: a date, not a rhythm

India and Pakistan have not played a bilateral series since Pakistan's tour of India in December 2026 and January 2026, three ODIs and two T20Is. Since then they have met only in ICC events and Asia Cups. That is a date on a calendar, not a habit with a rhythm.

The 2026 Asia Cup was played on a hybrid model: some matches in Pakistan, the rest in Sri Lanka. The group game between the two sides, on 2 September at Pallekele, was washed out after India had been bowled out for 266. So the Super Four meeting was their first completed match of the tournament — on a used pitch, in humidity so heavy the covers came and went twice before the evening.

India made 356 for 2. Rohit Sharma 56, Shubman Gill 58, then Virat Kohli 122 not out and KL Rahul 111 not out, an unbroken 233 for the third wicket. Pakistan were bowled out for 128 in 32 overs; Kuldeep Yadav took 5 for 25. The scorecard is complete. What it does not contain is the reading.

The 233 that fell in one place

Start with the innings that broke Pakistan's bowling structure. Pakistan had Shaheen Afridi, Naseem Shah, Haris Rauf and Shadab Khan — four specialists. After that, options.

Playing four specialist bowlers in an ODI means you must hide 20 overs behind a man you publicly call a part-timer and privately do not consider a bowler at all.

Kohli and Rahul did the most boring and most lethal thing available in tournament cricket: they waited. A large share of that 233 was spent on the fifth bowler, and the remainder on the four front-line bowlers' overs that never quite squeezed. I watched that innings twice, once with sound and once without. The second time you hear that the silences between Kohli's shots were also scoring. With the volume off, a shot declined looks as violent as a shot struck.

The second innings: why 32

Pakistan's innings lasted 32 overs, not 50. Read as a scoreline it sounds like pathos. Read as bowling it is a technical failure.

Kuldeep's spell came in the middle overs. On a humid evening when the ball skids, the spinner's first job is to ensure the batter cannot assume every ball is turning. Kuldeep took his five wickets not one by one but as a sequence: he let them read one, gave them the same expectation, and when the expectation settled the ball took a different road. Three pictures went into my image ledger that night: a groundsman dragging the covers at five o'clock, Kuldeep's follow-through (always a fraction late to leave the ball behind, as though a sentence were not quite finished), and the empty ground after 32 overs.

Eighteen overs: the unread third

Playing 32 overs of a 50-over match means leaving 108 deliveries unused. At minimum, a third of the innings came back unspent — the book you had in your hands, returned unread.

Pakistan's ODI batting template in recent years has been: the top three bat long, and whoever follows tries to accelerate and leaves. That template works only when one of the top three is still there at the end. On the day all three went early, nobody was left who could carry 20 overs of responsibility. Colombo was that day. The team did not lose — the team ran out of overs. That is the fine difference between 228 and 18.

Two commentary boxes, one match

That evening I went back and listened to clips from two Hindi-Urdu commentary feeds the next morning. One used the words depth, wicket-taking ability, a barrage of punches. The other used intent, physical fatigue, a shortage of confidence. One match, two grammars. Analysis on one side, psychoanalysis on the other.

I first understood that split at nineteen. In 2026, Shubman Gill scored 372 runs at the Under-19 World Cup and I wrote 1,900 words on his back-foot punch. Somewhere in those 372 runs, I found my first sentence. I did not know then that a number should not be spoken so loudly. I know now. Hard analysis carries the clue to the next ball; easy analysis carries the player's character. The second sells better.

Contrarian: the lie of 228

Everyone remembers 228. Nobody remembers 18. And if you accept 228 as the story, the night looks like a one-off mine of diamonds — India did nothing, Pakistan crumbled.

The truth is reversed. 228 is not the product of one night; it is compound interest on a calendar frozen since 2026. When two teams meet only one-off, at big moments, across different tournaments, with not a single ODI ball bowled against each other in the years between, no coach can build a 50-over batting sample. You cannot fix a middle order across roughly nine or ten meetings in twelve years. Both sides — India included — pick their safest XI every time, because no fixture is minor. No series, no experimentation, no rotation, no rest.

The consequence lands on depth. The side with the deeper bench never has to show it in these one-offs, yet it is the side that wins them. The gap in the calendar became the gap in the scoreline. And that is precisely what both commentary boxes miss: one calls it a confidence deficit, the other calls it a talent gap, and neither looks at the sheet that says how little data these two teams have on each other.

What else the 228 hides: that match followed a rain-wrecked day. On a used Colombo pitch in September humidity, four specialist bowlers' arms get light at a predictable hour, and no model shows you that — the ground does. I have watched enough domestic sides rehearse it: they intend to hold on for fifteen overs, then cannot even squeeze for thirty-five.

The file nobody opens

Every scorecard is a diary someone forgot to hide.

I became certain of this in the pandemic year, when I was not in a press box but watching from a bedroom while the country locked down. In my Kolkata neighbourhood the same lines come back every time — how big the score was, how many wickets fell, who was bowling. Those lines tell you we speak the language of the scoreboard without knowing its story. Sentences about 18 overs rather than 32 are not written in the scoreboard's language. They appear only to the person reading it a second time.

This is not an argument for India, incidentally. The advantage India took in Colombo was not cricket's; it was the calendar's. Pakistan will never get a chance to close that gap until they play five or six ODIs against India in a row — and they will not. This is where I open the file I keep on young players, where each of them gets one paragraph on what he does when he fails rather than when he succeeds. On that measure nobody passes in Colombo, because the queue standing in front of a place in the XI was not about ability at all.

What comes next

The next time these two meet — and it will again be an ICC event or an Asia Cup — the scoreboard will shout a large number. The newspapers will headline that number. And once again nobody will write down why a team left its overs unplayed.

I will turn the volume down again. I will count the overs nobody used. If that number comes out above 15 once more, know that we have watched another match and learned nothing from it.

I genuinely hope it does not. That is the one thing I would like to be wrong about.