From 4/2 to 351: KL Rahul's 129 Off 87, and the Broken Small Numbers on the Scorecard

Saturday. At the tea stall on the Farmgate crossing where I have listened to scores for three decades, the afternoon light had just begun to slant when a young man turned his phone toward me. Two numbers on the screen: 4/2. Three overs. Shubman Gill 1, Virat Kohli 0, on consecutive deliveries. No shouting in that shop. Only the knock of cups and one man whispering: 'It's over.'

I have watched many matches end — not from the pitch, but from bedrooms. In 2026, when Neymar's €222 million was carrying him from Barcelona to Paris, I was sitting in that same Farmgate corner, calculating a rickshaw puller's daily earnings against a transfer fee. Tonight the same feeling returned. But four hours later, the same phone brought back another number: India 351/7. KL Rahul 129 not out off 87 balls.

The question of that night still sleeps beside me: who built the road from 4/2 to 351/7 — one man, or a structure?

The match was the third and final ODI of the series, played on a Saturday. India batted first and made 351/7 in fifty overs, at 7.02 runs per over. The three-phase grammar of ODI cricket is almost textbook here: a powerplay collapse (4/2 in three overs), a middle-overs rebuild (Rohit Sharma 92, Ruturaj Gaikwad 57), and a final-ten-overs explosion (Rahul 129*).

One thing I will say plainly, because it is the honesty of my trade. The report names no venue. What the pitch was like, whether dew fell, who won the toss — none of it is written. We know the score; we do not know the soil. A 351 total and a 148-strike-rate century suggest a good batting surface, but that is my inference, not a fact. I am 69, and the one thing this age teaches is that pretending to know what you don't is the most expensive mistake in this business.

West Indies' new-ball spell, through Jayden Seales, was a nightmare for three overs. Then he vanished. That is where the match's story actually begins.

Rahul's number deserves to be opened slowly. Eighty-seven balls, 129 runs — a strike rate of 148.28. In ODI cricket an anchor usually bats at 85 to 100; a finisher climbs above 110. Rahul did not merely touch 148; he sustained it across a fifty-over innings, and he did it after walking in at 4/2. If an innings is only an explosion, it speaks T20; if the explosion survives to the last ball, it speaks the mature language of ODI batting. Rahul spoke the second language that day.

His boundary arithmetic sharpens the picture. Ten fours (40) and six sixes (36) — 76 of his 129, or 58.9 percent, came in boundaries. That ratio is high for a long innings, meaning he hit when he found the ball and chose his ball while hitting. Boundary dependence becomes a danger only when the rest dries up; here the remaining 41 percent arrived too, so strike rotation stayed alive.

But Rahul did not build this mountain alone. Rohit's 92 off 85, at 108.24, was the foundation the building stands on. These two innings complement each other: Rohit bought time, Rahul broke that time into runs. The old ODI truth holds — an innings needs two kinds of patience, one called waiting and one called opportunity.

Here a discrepancy catches the eye, and I cannot leave it unmentioned. Ruturaj Gaikwad's 57 off 69, a strike rate of 82.61. Yet his boundaries were four sixes and only one four. A batter with more sixes than fours usually carries a higher strike rate; here it is inverted. The likely reading: he managed risk through the middle overs, scoring slowly and lofting occasionally. Statistics may call that innings 'slow'; the team ledger calls it the most valuable insurance in the match.

The real structural story is 4/2 to 351/7. Two wickets inside three overs, yet more than seven runs an over. Beneath that downpour sat something larger than one player's day: a system's signature. When your number three, four and five can all hold the tiller, a collapse and a defeat become two different things. India took the first that day; they did not take the second.

Turn to Seales. He took wickets — but at what price is the whole question. 3/45 and 3/62 tell two different stories. At 45 he was sharp; at 62 he was expensive yet effective — the classic wicket-taking-but-leaky bowler. And the report says Gill and Kohli fell on consecutive deliveries, meaning Seales took two wickets in one over, and the incoming batter faced a hat-trick ball. The true hinge of the match was that single delivery — the one no headline carried, because it either happened or it didn't, and history only records what happened.

I will speak here from my own experience. In 2026, scripting a documentary on Japan's dressing room after Russia, I learned that the scoreboard says how many, the dressing room says why. That day too the headline held the result, and the real lesson sat in the locker room. Same here — 351/7 is a result, but 4/2 is the moment a team recognises its own character.

And my bedroom arithmetic, because I do not see numbers only on the field. 129 runs means 87 balls, nearly four and a half hours at the crease. If a young fan watches this innings in a 30-second reel, he loses the emptiness stored inside those 87 balls — the overs when he could not pierce mid-off, when rotation slowed, when his body said 'not today.' I find the weight of the number in a Dhaka bedroom, not a boardroom — because the boardroom counts runs, the bedroom counts the balls in which he survived.

There is another layer I write deliberately: who is watching matters. My ten-year-old granddaughter saw only 129 on the screen; my seventy-year-old neighbour saw the shadow of the West Indies attacks of 2026-80, when 4/2 meant the match was nearly done. Two generations, one scorecard, two meanings. I want to build that bridge myself, because cricket memory travels from father to son by mouth, not by ledger.

Now the crack in this report that everyone steps around.

We argued all evening about Rahul's 129, Rohit's 92, the 351 — the big numbers. But the small numbers are broken. The same report has Gaikwad on both 55 and 57. It has Seales on both 3/45 and 3/62. Two figures cannot both be true. The number that spreads fastest is the number least verified — the disease belongs to our era more than to cricket.

There is a second blind spot we file away in memory's cupboard. The match is named '351/7' — but that is half a match. The report records only India's batting; what West Indies answered is nowhere. We remember one innings as a whole match because our imagination stops at the first innings. Collective memory keeps the big number and forgets the small turn — Seales' hat-trick ball has no fan club.

The third crack is more uncomfortable. We have turned 4/2 into a hero story. But one may ask: is this praise of India's structural depth, or evidence of the opposition's loss of control in the middle overs? Seales was fire for three overs, then a man watched from a distance. Had West Indies' spin and middle-overs bowling run a scheme, 351 would not have happened — 260 would have, and the story of the 129* would read differently. The credit is certainly Rahul's, but the soil he grew in was given by the opposition — and we do not say that, because gratitude and criticism are hard to speak in one breath.

My age obliges one more line: I know Rahul's injury history. A 129* in one ODI is a page of a long body's account, not the whole book. We know only as much as clubs and boards choose to release — and it always arrives at a time that suits them. A fan owns no part of a player's body, only affection; building stories from that affection is my job, and it is also my largest limit.

So what stayed from that day?

Eighty-seven balls, a not-out, and a tea stall in Farmgate where nobody clapped — only one young man whispered, 'Look, he stood up.'

Two questions remain, and they will sit on our shoulders into the next ODI. First: is this Indian depth a structure or a stroke of luck — if 4/2 returns, does 351 return, or does it stop at 170? Second: who verifies the numbers we recite daily — 3/45 or 3/62, 55 or 57?

I am 69, and in this trade I am still learning one thing: matches end, series end, scoreboards reset. But those three overs of 4/2, and that hat-trick ball — they vanish from the scorecard and stay on the fan's shoulders. I write scripts for games that end, because memory refuses the final whistle.