New Ball, Old Story: In the Irani Cup, 89/3 Became 111 — Seven Wickets for Just 22 Runs

New Ball, Old Story: In the Irani Cup, 89/3 Became 111 — Seven Wickets for Just 22 Runs

In my Liverpool basement studio, the tea had gone cold long before. The scorecard was live on screen, and I could not look away — Jammu & Kashmir 89/3. Then it happened, not slowly but all at once, the death of an innings. 111. Seven wickets, just twenty-two runs.

The number is dry, but a story hides inside it. When the J&K innings shattered in the Irani Cup, it felt less like reading a fresh set of patch notes and more like watching an old, familiar script in which only the colours of the shirts and the season change. Mukesh Kumar, Akash Deep — two names, two pace bowlers. And that is all. There are no individual figures in the source, no venue, no innings sequence. Yet this very blank space speaks to me the most, because it tells me the real story is not on the scoreboard but behind it.

I am 59, born in Bangladesh, now based in the UK. From joining the sports desk of The Daily Star in 2026, through a decade and a half of regional football broadcasts, to launching an online show called 'Rift Report' from a Liverpool basement in 2026 — across that whole journey one thing I learned is this: the gap between a match on the field and a live-service game is smaller than we think. Every new ball is a balance change. Every collapse is an un-patched weakness that the opposing side spotted on their data table long before.

Context: Why the Irani Cup matters even as a domestic fixture

The Irani Cup needs a brief explanation, because many newer fans — the ones who entered cricket through the IPL — do not know this tournament. The Irani Cup is an annual single first-class match in India. It is played between the reigning Ranji Trophy champions and a selected 'Rest of India' eleven. Rest of India is not one team; it is a composite side drawn from across domestic teams, usually featuring national and international-standard players. So on paper it is a 'domestic match', but in practice it is a mini audition room, with selectors sitting in the seats.

The match is played under first-class rules — red ball, multiple days, sessions, follow-ons, declarations. T20 or ODI logic cannot be transplanted here; this is a wholly different meta. And this is exactly where my first objection arises.

In 2026, standing on stage at Liverpool's official World Cup fan zone, I called the England–Colombia penalty shootout a 'Summoner's Rift teamfight' — England vs Colombia was a Summoner's duel, in which Jordan Pickford's save was a support's clutch ward. That 43-second clip went viral, but my real lesson was different: when the mode of play changes, the language of analysis must change too. Watch red-ball first-class cricket through a T20 lens and you will get it wrong. Here a collapse is not just wickets; here a collapse is momentum, confidence and the behaviour of the pitch — three things breaking at once inside one session.

That J&K are playing in the Irani Cup is itself a big piece of information. The right to play this match belongs to the side that wins the Ranji Trophy. In other words, J&K have just had a strong Ranji season, or they would not be here. Yet in this match their innings fell apart at seven wickets for twenty-two runs. That is an anomaly — and this anomaly is the centre of my entire analysis.

Core analysis: the arithmetic of the collapse, the signature of pace, and a hidden audition

The only hard analytical signal in the source is the arithmetic of the collapse. Going from 89/3 to 111 all out means the last seven wickets fell for just twenty-two runs. This is a classic pattern — I call it 'cluster failure', the middle and lower order breaking together. And most importantly, this collapse was triggered by two pace bowlers.

Seven wickets for twenty-two runs — this pattern is not the slow grind of spin; it is the jolt of the new ball. If a spinner had bowled a side out, we would normally see a slow, continuous erosion — one wicket per over, run rate dropping, batsmen stuck at the crease. But seven wickets for twenty-two runs is more than a wicket per over. Spinners do not generate that pace; seam, swing and bounce do.

There is an old saying in cricket — 'one wicket brings two'. In Rift Report language, we can call it a 'rhythm break'. When a new batsman arrives at the crease, he arrives with cold hands, and that is precisely the bowler's golden hour. If the first ball hits the stumps, it enters the next batsman's head; and if an edge falls, the following batsman plays the edge in his mind before he plays the ball. In this way a session turns in fifteen minutes.

Here an important factual caution is necessary. The source contains no individual figures for Mukesh Kumar or Akash Deep — not 4-for-anything, not 5-for-anything. No economy rate, no strike rate, no ball-by-ball data. So I cannot say who took how many wickets, or whose spell was how destructive. All I can say is role-based: both are pace bowlers, and both triggered this collapse. The biggest mistake any cricket analyst could make here would be to invent the missing data. I will not.

Still, one thing can be inferred — because two pace bowlers are named together, this was probably a paired new-ball or first-change spell, where one built pressure and the other cashed in. That is the classic work of a pace pairing. One bowls for 'discipline', the other bowls for 'results'.

Now to the question that determines this match's real value: why did it happen?

Rest of India versus Jammu & Kashmir — this is a story of a quality gap. The Rest of India attack means a group of international-standard pace bowlers. J&K means the Ranji champions — the top representatives of India's domestic batting standard. But there is a gap between top domestic standard and international standard, and that gap becomes visible precisely in matches like this. History says Rest of India often leads in the Irani Cup, because on paper both sides are 'Indian', but one side carries international experience and the other does not.

To me this match is a system-design question. What is the Irani Cup for? Its primary function is not revenue or broadcast — it is to test the talent pipeline. It is a selection audit. And this is exactly where the names Mukesh Kumar and Akash Deep become significant. Both have played for India. Both are the kind of pace bowler who lives on the selectors' radar in the red-ball pipeline. Irani Cup performances historically influence national selection.

But here is my biggest doubt. One session, one innings, one collapse — can we really judge a team's batting quality from that? Watching the game for 43 years, I say no. A side might bat brilliantly all season, and then in this one session everything breaks. That is cricket's greatest cruelty — the beauty of thirty-three innings can be erased in one session.

Now to the meta level, where I am most comfortable. If we think of a session as a teamfight in a game, then 89/3 means the team was in a good position mid-map — three wards placed, river control. Then, when the pace bowlers returned with the new ball, it felt as if the opponent began a perfect teamfight: a CC, a tank engage, a support ult — and in five seconds everything flipped. In cricket those five seconds are spread across three or four overs.

One aspect of this collapse I particularly note — when it happens. In first-class cricket an innings usually breaks at two times: in the morning's first session, when the pitch has dew or fresh seam; and at the day's end, when light fades and batsmen tire. 89/3 to 111 — a fall like this often happens at a session boundary. I do not know the venue or the time, so I cannot say which. But the pattern is familiar.

Another point I want to stress, because it is an old complaint of mine. Data analysts have now entered the dressing room, spreadsheets in hand. But many of their conclusions are detached from the actual rhythm of the match. A 'wagon wheel' graph will tell you who scored how many, but not how the wind changed in the second session, or which ball entered a batsman's head. In this match we have only one number — 22 runs, seven wickets. The number tells me the result, not the cause. And to know the cause I would have had to be at the ground, or at least see the ball-by-ball scorecard.

Contrarian angle: are we really making too much of this collapse?

Now I want to stand against myself, because that is my job. In the last few paragraphs I have turned one collapse into a big systemic story. But what is the strongest conventional view? It is this: 'Rest of India are a good side, J&K played a bad session, end of story.' And honestly, that view fits the source information best. Because all we have is part of one innings.

I admit it: a single session's collapse cannot deliver a final verdict on J&K's batting quality. Just as, without figures, Mukesh Kumar or Akash Deep cannot be called 'elite'. Both directions carry risk — one is over-praise, the other over-blame. The biggest trap of data journalism is drawing large conclusions from a small sample.

The meta is a rumor with a win rate; my job is to ask who benefits from the whisper. In the Irani Cup, one good spell by a pace bowler gets turned over the following weeks into a 'claim for a national return'. It is a familiar narrative pathway. I do not believe the whisper, but I know why it spreads — because it supplies a rationale for the selectors' decision.

And here is my second objection. When we talk about a 'collapse', we usually look for fault in the batsmen. But the question should be: why are collapses like this so regular? The answer is probably not individual but structural. In domestic cricket, the habit of batting against the new ball, the time taken to adjust to pace and bounce — there may be a systematic gap in these areas. If so, then it is not J&K's failure but a question for the whole system.

One more thing. Mukesh Kumar and Akash Deep are the kind of pace bowlers whose workload is regularly discussed in Indian cricket. They are injury-prone, and in India's packed calendar the overs pile up across domestic and international cricket. If both bowled heavy spells in this match — which is inferable, since both triggered the collapse — that adds to their season's total load. It is a silent risk, invisible on the scorecard.

Takeaway: where the story stops, the question begins

The tea in my studio is still cold. The scorecard has changed — 111, all out, match over, Rest of India have won the Irani Cup. But a question is circling in my head, and it is not about the result. The question is: where do the seven wickets of this session go over the next six months? Into the selectors' notebook, or lost in the paper pile of domestic cricket? And will J&K's strong season be diminished by this one innings?

At 59, I have seen many patches come and go; this bard knows a collapse is not a team's identity, it is only one night's story. But he also knows some night stories become history — if only someone writes them down.