From 89/3 to 111 — Twenty Runs, Two Pacers, and the Story of an Incomplete Scorecard in the Irani Cup

First, a confession. I was not at that Irani Cup match. The television screen was not in front of me either; I was in an old room in Liverpool, awake at night, headphones on, and in my hand that notebook which I have been filling after every match since my 2026 Melwood trip. All that reached me was a scoreline: Jammu & Kashmir 89/3 to 111 all out. And two names: Mukesh Kumar, Akash Deep. That is all. No venue, no date, no innings, no toss.

I still hear the hum of my first audio notebook. Cricket's biggest stories are never written in complete data; they are written in the gaps of data, inside the silence, where the ordinary viewer never looks. Seven wickets for just twenty-two runs — that number is itself a sentence. But which sentence? To understand that, I must first explain what the Irani Cup actually is, and why the collapse of a single innings matters so much.

The Irani Cup is an annual fixture in India's domestic first-class calendar. Each year the Ranji Trophy champion plays a composite eleven called 'Rest of India'. This composite side belongs to no single state; it is a selected team drawn from the best players across the country — a shadow version of the national side. So the match is not merely a contest for a trophy; it is a laboratory where the best domestic talent gets a chance to prove itself.

I remember my days at Prothom Alo in 2026, covering the Wills Cup in Dhaka. I learned then that a scoreline can sometimes say more about a team than an entire season — if you know which question to ask. This J&K collapse is exactly such a moment. A side that had proved itself across a whole domestic season suddenly broke apart in a single session.

The Irani Cup holds a particular place in the Indian calendar. It sits far from the IPL's glittering light, largely in the shade. There is no franchise here, no auction, no massive broadcast deal. There is only the red ball, five days of patience, and the eyes of selectors. That is precisely why this match matters — because this is where tomorrow's Test cricketers are made.

Now to the grammar of the collapse. Cricket's arithmetic never lies, if you know how to count. From 89/3 to 111 all out — that means the last seven wickets fell for only twenty-two runs. This was not a slow erosion; it was a contagious slide, where one wicket quickly pulls down the next two. A red-ball collapse of this kind carries a clear signature: the new batter never settles, and the bowlers are in rhythm. The middle order and lower order fall together, and the scoreboard stops.

I learned in football and esports that the story lives between action and anticipation. So it is in cricket — which bowler takes the over after 89/3, from which end he comes, that is the real turn of the story. Two names matter here: Mukesh Kumar and Akash Deep. Both are pacers, both have played Tests for India, both are from Bengal. That shared identity is no accident.

In red-ball cricket a collapse never happens randomly; it has a specific timing. It often comes after the new ball, or just after the tea break, when concentration slips a fraction. From 89/3 to 111 — a fall like this probably happened in one particular session, where one wicket opened the door to the next. Even without being at the ground, I know what happens in the dressing room at such a moment: one batter unbuckles his pads, a coach quietly takes notes, and the volunteer running the scoreboard simply changes the number.

When two international-standard pacers bowl together in a selected 'Rest of India' side, that gap often turns brutal for a domestic batting line-up. This is no crime and no conspiracy — it is the natural outcome of structure. The Ranji champion is built from the best domestic batters, but they face a bowling attack of near-national standard. This gap is the central tension of the Irani Cup, and it explains why collapses of this kind recur.

Mukesh Kumar and Akash Deep — saying these two names together means recalling a particular generation of Indian pace bowling. Both came through the hard road of domestic cricket, both proved more with less opportunity, and both now stand at the door of the national side. Bowling together on a stage like the Irani Cup means a hard examination for domestic batters — and in that examination, J&K's middle order did not pass.

Repino taught me that a set-piece is really a promise rehearsed in the cold. A new-ball spell in cricket is the same — it is not just skill, it is a plan made in the nets and executed in the middle. The spells of Mukesh and Akash Deep were just that — the fruit of a plan, executed by a selected attack.

Still, a question rises in my mind. Is this pace-driven collapse only the magic of the new ball, or the nature of the pitch? I did not watch the match, did not see the pitch, did not see the toss. I have no over-by-over data, no bowling figures. So here I must be honest: I cannot say how many wickets Mukesh Kumar took, how many overs Akash Deep bowled, or in which innings the collapse occurred. Inventing what is missing would be the greatest sin of my profession. Admitting this truth is not weakness; it is strength.

Here my absence-sensitive eye notices one thing. The voices missing from this story — the pitch curator, the damp outfield, the local spectators, the volunteer running the scoreboard — they are the real witnesses. A scoreline is sometimes the least-spoken part of a match. We see numbers, but we forget the people behind the numbers.

Now I come to the place where I want to stand apart from the rest. The story Indian media may build around this match is almost predictable: 'J&K's batting has collapsed', 'Mukesh-Akash Deep are knocking on the national door'. I do not easily agree with either claim.

I learned in football that a transfer is never merely a headline; it is a rhythm breaking in a dressing room. So it is in cricket — seven wickets in one innings cannot be the final verdict on a team's batting quality. J&K earned the right to play the Irani Cup, which means their season was a success. One bad session cannot erase that success. Between the collapse of one session and the failure of a season lies a vast difference.

A bigger question lurks here, one the Irani Cup often brings forward: how good is India's domestic batting, really? When top domestic batters repeatedly fold against international-standard pace, the question becomes — is the problem individual, or structural? That answer is not found in one match, but in many seasons of sample.

But the other side is also true. Praising these two pacers is not the same as drowning in hype. Mukesh Kumar and Akash Deep are both bowling at a time when serious debate is underway in Indian cricket about fast bowlers' workload. Their success is not only a story of skill but of awareness — how much bowling is being loaded onto their shoulders. Domestic and international combined, their calendar is full. We must keep account of that workload, because pacers are exactly as fragile as they are brilliant.

I keep the notebook close because memory has a tempo you cannot stream. This Irani Cup result is likewise a signal that must be read over time. Three things will stay on my radar.

First, the official scorecard. If Mukesh or Akash's figures read four or five wickets, the significance of this result grows; if not, the story changes. Second, J&K's next red-ball innings. Only if they are repeatedly bowled out below 150 can we speak of structural weakness. Third, the national squad announcement. Only if these two pacers' names enter the Test squad will a domestic result create international impact.

I learned in both football and cricket — count the beats nobody applauds, then write the silence around them. Those twenty runs in the Irani Cup may be just a scoreline to many. To me it is a reminder: cricket's real story is never on the scoreboard, but in the gaps of the scoreboard. And those gaps must be filled with witnesses, with data, and with patience. The real answer to this match may not yet be written — it will be written in the next match, the next scorecard, the next session.