89/3 to 111: The Irani Cup Collapse Where the Scoreboard Falls Silent

The day is still written on a separate page of my notebook. 89/3. A team was still breathing inside the match, a batting line-up was still building its foundation. Then a few sessions, and the scoreboard read 111 all out. The last seven wickets fell for just 22 runs.

This is not a number that shouts. The opposite — a collapse like this creates a kind of silence around itself, in which nothing much is audible beyond the squeak of the pace bowlers' boots and the ball brushing past the stumps. The frame holds its breath before the crowd decides what it means. To understand what the crowd at the Irani Cup decided that day, I did not need a highlight reel — the gaps between the falling wickets were enough.

I have been watching matches for more than two decades, and days like these have taught me that the truth of an innings never lives in the final scoreline; it lives in the rhythm buried inside it.

The Irani Cup. One of the strangest, least-discussed stages in Indian domestic cricket. Here two very different kinds of entity meet — on one side the Ranji Trophy champion, on the other a "Rest of India" composite eleven drawn from across the country. This is no franchise, no T20 carnival. It is red-ball cricket, a multi-day format where sessions, follow-ons and declarations all count.

Watching Indian domestic red-ball cricket from London, I understand this much — the real job of this stage is not winning but watching. Who is rising, whose arm is still fresh, whose rhythm can knock on the door of the national side. The very composition of Rest of India says this. It is an audit side, an experiment, where domestic stars are blended with names hovering on the edge of the national team.

One thing must be made clear here, because without it the whole match will be misread. This is not an international fixture. ICC rankings do not apply; no national-team index operates here. This is India's internal red-ball structure, where the result of one match is not a verdict on a season but a single step.

Jammu & Kashmir reaching this stage is itself a statement. It means a strong Ranji season stood behind them, a trophy stood behind them. A team arrives here over a whole year — winning match after match, on difficult pitches, on difficult tours, in poor light, on wet outfields. Then suddenly one session, and everything shrinks into the number seven wickets. I will try in this piece to restore the relationship between that journey and that session.

Let us look at the structure of the collapse. 89/3 means three wickets have fallen, but the batting is still standing. Then the last seven wickets for just 22 runs. This is not slow erosion. It is a cluster — the most feared and most familiar rhythm in red-ball cricket, where one wicket summons two more.

That cycle has a specific anatomy, and it matters. Early with the new ball, the seamer searches for his length. When he finds it, the ball moves away a touch, comes in a touch, and a doubt grows between the batsman's pad and bat. A wicket falls. Then a new batsman arrives, and his first ten balls are the most fragile — he is watching, taking time. At that very moment the seamer plays one notch higher. Second wicket. Then the set batsman, under pressure, reaches for a big shot. Third wicket. Those three steps together make a cluster.

Here lies the real information: seven wickets for 22 runs means the side did not lose through seven separate mistakes, but through one sustained momentum-break. A wicket fell, then a batsman changed, then the new batsman's first ball, then another wicket. Once this cycle starts it is hard to stop, because no one can play the big shot and no one can take their time either. The side is trapped from both directions.

Mukesh Kumar and Akash Deep — both red-ball seamers, both names that have touched the national side. Having bowlers of this kind in a Rest of India attack means a quality gap, which is normal in this tournament. A composite eleven, where the best seamers are gathered, faces a domestic champion side. On paper the match is uneven, and in red-ball cricket that unevenness doubles, because here an innings means the patience of hundreds of balls — and that patience is the first thing to break in a collapse.

But here is my caution. I do not have any individual figures from this match for these two seamers — how many wickets, what economy, how many overs, nothing. Only one sentence: they triggered the collapse. So I will not make a final claim about their skill. What I can say concerns rhythm and structure — this pair probably worked together in a new-ball spell, or a first-change spell. Two names arriving together usually means the responsibility was shared, not one man's solo.

And this is where the Irani Cup shows its true character. This stage is a page in the selectors' notebook. Performance here does not mean only a match; it means a knock on a door. Doing well for Rest of India means writing your name into the national red-ball list. So for Mukesh and Akash Deep the value of this day is cricketing, not commercial. There is no big money here, no thicket of sponsorship, only one calculation — who is ready.

From my flat in London this becomes clearer still. Where IPL auction numbers and contract news drown everything else, this red-ball window is almost silent. Nobody talks about its broadcast value, nobody runs the franchise arithmetic. Yet it is precisely from this place that the seamer is made whom everyone will search for months later on a bigger stage. Seen from the centre of the colonial cricket circuit, the real factory becomes visible — not on the stage, but in that small notebook beside the ground.

A team's batting is not its whole season; it is one session of one innings. 89/3 to 111 — this number is not the definition of Jammu & Kashmir's cricket. It is the definition of one day, one session, one new-ball window. Those who read the scorecard as a scorecard alone will see a team's fall. Those who read the innings as a story will see a side trying to stand, and a gust of pace erasing it.

And that gust has a cost nobody calculates. Two injury-prone red-ball seamers whose overs must be managed across a year — in the Indian calendar, where domestic and international matches run side by side, a long spell means not just a match won but an accumulated load. In this match's arithmetic that is invisible, but across a season it matters. The faster a collapse happens, the more overs pile onto the seamer's shoulder — a simple sum nobody does.

I have seen many erasures of this kind. Sometimes inside a kit man's folded jerseys, sometimes in the silent notes of a selector sitting in a corner of the dressing room. The real story of a collapse is never fully on the scorecard. A highlight reel edits out the fear; the pitch remembers it in the grass.

Now to my objection. The way results like this are usually read — "Jammu & Kashmir fell apart," "the pace attack broke them" — is a comfortable story, but an incomplete one. Collective memory always remembers the collapse, but forgets the context. And that forgetting is the real trap.

The truth is that a Rest of India attack facing a domestic champion means an uneven fight — written into the very structure of the tournament. Losing here is no disgrace; it is the natural result of that structure. Jammu & Kashmir arrived here by winning, not losing. By winning a trophy. That journey is not erased by one session's collapse, just as a trophy does not deny a bad day. Two truths must be held side by side, or we end up writing either an epic or a charge sheet.

The second objection runs the other way. The way Mukesh and Akash Deep's names may rise into national-team talk after this match is natural, but that too risks the same trap. Concluding from seven wickets in one innings that the bowling attack is extraordinary is a rush. One innings is never proof of a seamer's skill, just as one innings is never proof of a batting line-up's weakness.

I want to stand between these two traps. I will not turn the collapse into an epic, nor the seamers into miracle-workers. In a red-ball match a session simply goes this way — sometimes the batsman's, sometimes the bowler's. The real verdict comes when the same picture returns again and again. If Jammu & Kashmir's next innings also crumble below 150, then it is time to talk. If Mukesh and Akash hold the same rhythm across the coming matches, then it gets written in the selectors' notes. On a single match's evidence, both deserve time.

This caution applies to me too. My INFJ mind loves to find a beautiful counter-truth — "the collapse was really a story of triumph," that kind of twist. But if the evidence does not force that twist, I should cut it. Here the evidence says only this: a collapse happened, two seamers triggered it, the match was won by Rest of India. Beyond that is inference, and I will not dress inference in the clothes of fact.

What must be watched is not the collapse but the consistency. Jammu & Kashmir's next red-ball innings — will they pass this off as a nightmare, or is this the start of a pattern? The workload of Mukesh and Akash Deep — both are the kind of seamers whose overs must be counted across a year, because the Indian calendar is cruel. And the selectors' window — if their names enter the red-ball squad, then this one session will become the first page of a larger story.

When I write, I write that silence, between the whistle and the roar, where the story actually lives. This Irani Cup collapse is the same kind of silence — a scoreboard that stopped, with a question still hanging in the air.