Irani Cup: 89/3 to 111 — Seven Wickets for 22 Runs, and a Scorecard That Has Not Yet Told the Whole Story

In my notebook, collapses get a page of their own. Date, the order in which the wickets fell, and a small note in the margin — who was bowling, which end the wind was coming from, whether the keeper stood up or back. The page stays open even after the scorecard is finished, because a collapse never arrives alone; it arrives with a rhythm.

Jammu & Kashmir's innings in the Irani Cup is exactly that kind of page. 89/3 to 111 all out. The arithmetic is simple, and that is what makes it hard — the last seven wickets went for just 22 runs. When a side is 89 for three, it is thinking of 250 at least. Seven wickets for 22 runs means the entire middle order and lower order folded inside a single session.

The scorecard reached me through a short report. No venue, no date, no innings sequence, no individual bowling figures. One sentence — Rest of India won the Irani Cup, Mukesh Kumar and Akash Deep triggered J&K's collapse. I have to work with that limited information, and that is the most honest condition of this piece.

To understand the Irani Cup, you have to hold the shape of the Ranji Trophy in your head. India's domestic first-class season ends once the Ranji champion is settled, and the season closes with a single match — the reigning Ranji champion against a Rest of India composite. Rest of India means a combined XI drawn from the best players across domestic teams, usually featuring cricketers sitting on the edge of the national side.

The structure of this match sends a clear message. On one side is a team that fought through an entire season to become champion — their success is the product of a process. On the other is a composite side with less time together but a higher individual standard. Historically, the composite side tends to be ahead in this kind of fixture. That is not an accident; it is a structural expectation.

One thing needs clarifying here. The Irani Cup is not a commercial competition in the IPL mould. There are no franchises, no auction, no billion-dollar broadcast deal. Its primary function lies elsewhere — keeping account of who is being built in the red-ball pipeline and who is about to be. In Indian cricket, this match is one thread in the rope selectors tug at.

Now to the actual analysis. 89/3 to 111 — seven wickets, 22 runs. The easiest way to measure how severe a collapse is, is to calculate runs per wicket. Here 22 runs fell for seven wickets, an average of just 3.14 runs per wicket. In first-class cricket, the last seven wickets of an innings falling for so few means this was not ordinary batting failure — it was a break in rhythm, where the next batsman had to walk in before the previous one had settled.

The most reliable piece of information in this short report is the mathematical shape of the collapse — a cluster, not a slow erosion. A cluster usually comes from one of two things: the snap of the new ball, or the advantage of the second new ball. Seven wickets falling after reaching 89/3 suggests either that the top order and middle order never connected, or that once one wicket fell, the rest followed very quickly.

The second thing worth noting is that the collapse was caused by two pace bowlers. Mukesh Kumar and Akash Deep — both are fast bowlers who have played for India, both play domestic cricket for Bengal. Their names arriving together suggests this was not the product of long spin spells; it was pressure created by pace with the new ball or the second new ball. My confidence here is moderate, because the report carries no individual figures. How many overs each bowled, how many wickets each took, which end each operated from — none of it is known.

This is where I want to stop and draw a boundary. Seeing two pace bowlers named, it would be wrong to assume this was a one-sided rout in which batsmen simply could not stand up. In first-class cricket, an innings like this is often shaped by how the pitch behaved, the direction of the wind, a change in light, or fatigue carried over from a previous innings. Without knowing the venue, you cannot write a single sentence about the character of the pitch.

Still, one thing can be said. A Rest of India bowling attack is built from international-standard pacers, and they bowl against the batting line-up of a domestic champion side. That quality gap is the central story of this kind of match. A Ranji-winning team walks out with pride, then faces an attack it has not encountered even twice across an entire season.

That gap has a quiet consequence that rarely enters the conversation. For Rest of India's pacers, this match is also an exhibition — a chance to knock on the selection door. The Irani Cup's real function is not commercial; it is selective. Whoever takes five wickets here finds his name in the following week's list of probable national players. That is a familiar path in India's domestic structure.

And right there, a worry surfaces for me. Mukesh Kumar and Akash Deep — both are fast bowlers, and in Indian cricket the conversation about fast-bowler workload is now almost permanent. A domestic first-class match, a long spell inside it to force a collapse, then the international calendar — that sum is not always comfortable. The report carries no over count, so I will only leave the question standing: how many overs of investment did this collapse cost?

The fan-stand angle belongs here too, because reading the scorecard alongside the stands is my habit. The stadium — whether it is the ground in Rajshahi or the one in Jammu — carries a crowd whose rhythm sounds the same. For J&K's cricket followers, this match is seen with different eyes: their team won the Ranji and is playing the Irani Cup, and that itself is the season's biggest event. A single innings' collapse does not erase that achievement. What I saw in my small fan group was not anger but disappointment — one session went wrong, why should an entire season be forgotten?

Seen from Bangladesh, a comparison comes to mind. I kept a notebook through Rajshahi for six weeks, and what I saw there was that when a small team wins a big match, the next task is losing its best player. The Rajshahi Kings story of 2026 was exactly that — success arrived, and immediately eyes turned to the side's best names. — Root: Rajshahi Kings

The underlying structure is no different for Jammu & Kashmir. A Ranji-winning side will send two or three of its best to the national camp the following season, someone will move to a bigger team, someone will lose rhythm. That is how the system works — success is immediately followed by small sides losing their best names. And within that flow, the success of smaller teams becomes short-lived.

I have another habit in my writing — at least three fan comments in every long match report. That is not possible in this match, because I was not in the stands. So the honest route is to admit it and let readers speak: to learn how that evening of collapse was seen by whom, I am trawling Indian domestic cricket fan forums, and the answers will come from there.

Now to the part where the common reading and my reading separate.

The composite side winning was expected, because its individual standard is higher. So reading this result as the fall of Jammu & Kashmir is misleading. It is an expected outcome inside which a collapse took place.

Another angle: one innings does not deliver a verdict on batting quality. 89/3 to 111 — those seven wickets cannot be used to declare J&K's batting weak. Equally, this collapse cannot be called proof of top form for Mukesh Kumar or Akash Deep, because neither man's figures are known. With the limited information in this report, what can be done is to raise structural questions — not to pass judgement.

What matters most is this — the real story sits outside the collapse, in the pipeline. How Rest of India functions in India's red-ball system, where each pacer stands, how far domestic champions can hold up against an international-standard attack — those questions are bigger than the collapse. A session's slide is the news of a match; the state of the pipeline is the news of a season.

And the media's tendency is to inflate two pacers' names into selection buzz. There is nothing wrong in that, but the picture stays incomplete. If one man's figures really are four or five wickets, the story changes; if the two shared four wickets between them, the story is a different one. Selection talk without figures is only guesswork.

In the coming days I will watch three things. The official scorecard — who took how many, how many overs, at what economy. The cumulative overs of these two pacers, because when domestic red-ball cricket and the international calendar arrive together, a fast bowler's body speaks first. And J&K's next innings — if they are bowled out under 150 again, the question outgrows the boundary of one innings.

89/3 to 111 — this number speaks of one innings. The numbers that follow will speak of a season. I have left my notebook open.