89/3 to 111: What the Irani Cup Collapse Proves, and What It Doesn't

At two in the morning in a Dhaka flat I refreshed the scorecard page. 89/3. Normal. Twenty minutes later I came back and saw 111 — all out. Seven wickets, twenty-two runs. I put the phone face-down on the table, then picked it up again, because I recognise the pattern. Not only in cricket. I recognise it in the last ten minutes of a football match, in a team fight, in an empty stadium in 2026.

I left the print desk after my Ardent Censer sermon: support the story or feed alone. The sermon still holds. In this collapse narrative, two seamers are the heroes and one team is the villain — and nobody is asking who was actually supporting the match, and who was feeding alone.

What the report contained is barely six sentences. Rest of India won the Irani Cup. Jammu & Kashmir went from 89/3 to 111 all out. Mukesh Kumar and Akash Deep triggered the collapse. No venue, no date, no innings breakdown, no bowling figures, no toss result.

The thing the report does not contain is itself the first analytical signal.

It is worth clarifying what the Irani Cup is, because for a Bangladesh readership the structure of this tournament is almost invisible. It is a single first-class fixture run by the Board of Control for Cricket in India. On one side sits the Ranji Trophy champion; on the other, a Rest of India composite XI drawn from across the country. The format is red-ball, multi-day, played under first-class rules.

The structure is itself a message. Rest of India means the names sitting on the next rung of the selectors' sheet, or returning from injury, or in need of a form audit. Often the XI contains full internationals. The Ranji champion, by contrast, arrives at the end of a long, tired season — but arrives with its best eleven.

This is not a best-versus-best contest. It is a composite, international-standard bowling attack against a domestic champion batting line-up. The gap exists on paper; it also shows up on grass.

Why is Jammu & Kashmir in this match? You have to infer it. There is one normal route into the Irani Cup — winning the Ranji Trophy, or at least reaching the final. The report does not say so. That makes it inference, not fact. But the inference is reasonable, because the tournament's structure says it.

There is a second absence, and it is bigger. This match is not a Test, not a T20, not the IPL. It is a node in the Indian board's red-ball development pipeline. Commercial transmission here is close to zero. Ticketing, broadcast rights, franchise valuation — none of it applies. If you go looking for the money story in this fixture, you will find nothing, because there is nothing to find.

Now to the substance. 89/3 to 111 says exactly one thing: the last seven wickets fell for twenty-two runs. Clusters of that size are not common in first-class cricket, but they are not unfamiliar either. The mechanics are specific.

Red-ball batting collapses usually arrive in one of three ways. The new-ball window — the first ten or twelve overs, seam movement, the lbw line. The second new ball — somewhere around the sixtieth to eightieth over, when reverse swing on an old ball meets the bounce of a new one and creates a confusion zone. And the run-rate squeeze — once one batter falls, the next one takes a risk before he has set.

The report does not tell us which of these happened. But the two names tell us a great deal. Mukesh Kumar and Akash Deep are both seamers, both from Bengal, both capped by India. A cluster triggered by those two is not the slow grind of spin pressure. It is a burst — new ball or second new ball.

I have watched Mukesh Kumar's profile for years. He is the workhorse seamer: the third seamer whose job is to hold the pressure over after over, to keep tugging batters outside off stump, and then, just when a batter looks set, to hold the seam upright and produce an lbw or a slip catch. His wickets are often silent wickets. They do not make the highlights reel. They change the weight of the match.

Akash Deep is a different species. He hits the deck. His first spell with the new ball is usually his best — a slightly shorter length, the ball skidding, the batter's premeditated shot breaking down. In first-class cricket this kind of bowler has a defined role: he can take two or three wickets in the first hour and void the opposition's entire innings plan.

What does it mean to bowl those two together? It means putting two different problems in front of the same batting line-up — on one hand a ball that is not swinging but seaming; on the other a ball that is skidding and climbing. A batter who is a fraction late transitioning between the two always has a wicket waiting for him.

Seven wickets for twenty-two runs is almost never six batters making six separate mistakes. It is a system failure. Once the first wicket falls, the rest stop batting to their own rhythm and start batting to the situation's rhythm. It is exactly what happens in a team fight — one pick, then an ultimate, then the whole skirmish resets, and the fight is over. In red-ball cricket the same thing happens on a session scale.

This is where the cleanest translation between esports and cricket hides. How does a cascade or a snowball work in Mobile Legends or League of Legends? One team's mistake is punished by a second mistake, and the second by a third. In the language of economics, every death is an asset for the opponent and a liability for you. 89/3 to 111 is precisely this arithmetic — the price of each wicket rises with time, and by the end batters are playing shots they would never have played at 89/3.

The second new ball deserves separate treatment. In a first-class match there is a window for taking the new ball after roughly eighty overs, and seamers often return in that window. If the collapse happened there, the story changes — it becomes a story of depth shortage and fatigue. If it happened in the first spell, it is a story of technique or mindset. The report confirms neither. I will not hide that uncertainty, because analysing inside the wrong frame produces the wrong conclusion.

The pitch and venue are equally unknown. A collapse driven by seam movement on a green top and a collapse driven by spin pressure on a dry turner produce the same scoreline and completely different stories. You cannot infer pitch character from a scorecard. Those who claim to are cheating their readers.

So does this collapse prove Jammu & Kashmir's batting is weak?

No. Seven wickets in one innings cannot measure a team's batting quality. It is one session, one match. Across a first-class season, a cluster like this happens to almost every side. Winning a Ranji Trophy requires carrying the weight of nine or ten matches; one session does not erase it.

But stopping there leaves the analysis incomplete. If the question is how good Jammu & Kashmir are, the wrong question is being asked. The right question is: how is this fixture structured, and who does that structure favour?

The answer is uncomfortable. Rest of India is a composite drawn from the country's best bowling resources. The Ranji champion is built from one state. The first has more depth at the bottom than the second — that is the rule, not the exception. The collapse in this match is therefore not a surprise; it is the outcome of a structural expectation. When two international-standard seamers bowl at a domestic batting line-up, seven for twenty-two is a probable result, not a miracle.

This is where a second professional habit kicks in. At the 2026 World Cup in Russia I wrote that France's 4-2-3-1 — averaging 39 percent possession in the knockouts, winning on set pieces and transitions — was not cynicism but a tank comp: a low-economy build that knows its own strength and does not attempt anything outside it. Four of France's fourteen goals came from set pieces, per FIFA's official match data. Rest of India's pace attack is the same tank comp. It does not come to perform magic. It comes to make the opponent uncomfortable, and wickets come out of that discomfort.

One more thing is worth noticing. The report contains no bowling figures. No four-wicket haul, no five-for, no economy rate. Who bowled how many overs, who took the new ball, who came back in the second spell to force the collapse — unknown. That absence is itself information. It tells you the report is result-centred, not process-centred. You cannot analyse a result-centred report; you can only build a narrative from it.

I do not predict the meta; I sing the version history until it makes sense. This match's version history is still incomplete, because the part of the scorecard I need — spell breakdown, bowling ends, field settings, DRS usage — is not in my hands.

There is a comparable structure in Bangladesh too. In the National Cricket League and the BCB's domestic calendar, the same question arises: when a domestic side faces a bowling attack of national-team standard, is the result that side's failure, or the natural output of the structure? Journalist colleagues in Dhaka have raised this question many times, and the answer usually points the same way. In a system that pits a composite against a single team, one side holds a structural advantage. That is not a story about individual skill.

The workload ledger belongs here as well. Mukesh Kumar and Akash Deep are both seamers with injury histories, and both feature regularly in national workload discussions. If forcing this collapse required heavy spells from both, those overs were added to their seasonal debt. The trophy from a first-class match goes to a museum; a seamer's fatigue goes to the next series.

Now to the place where I want to break my own story.

The first objection runs like this: two seamers bowled brilliantly, they forced a collapse, that is the story. Correct. But is the story new? Across Irani Cup history, Rest of India has regularly squeezed the champion side. For a composite, that is normal. If the result was expected, why is it being sold as a shock? I am putting that question to my own reporting too.

The second objection matters more, and it points at me. Asian cricket media has an old habit of declaring a good spell a national-team doorway. Selection buzz — I have seen the phrase many times, and most of the time it is exaggeration. Selection is not the output of a single match; it is workload management, injury history, condition-specific roles and the calendar. An Irani Cup spell does not put a seamer into a Test squad; it writes his name on a discussion list. And the distance between a discussion list and a final squad is measured in competition, not highlights.

Writing about transfer windows taught me something: agents write the patch notes. Cricket's equivalent is the manager and the media broker, who convert one good spell into a storyline. It will happen here too. Within forty-eight hours of the figures being published, both names will appear in national-team chatter. That is not bad, but it is not analysis — it is marketing.

The third objection is structural, and it is the most uncomfortable. If Rest of India versus the Ranji champion is routinely one-sided, what is the fixture actually for? Sporting contest, or selection audit? The Irani Cup's commercial weight is close to zero. Its value therefore sits entirely in the talent pipeline. It is not a match; it is an interview.

And interviews have a specific problem: the interviewee does not interview the interviewer. The side that turns up to be interviewed — the Ranji champion — never gets its own risk-taking counted. It arrives after a tired season, stands in front of a composite attack, and if it collapses, the tape reads weak batting. This is where I remember the Ardent Censer line: the one who supports is never counted; the one who feeds makes the highlights.

One more thing nobody will write. Naming two seamers together probably means both bowled heavy spells. India's pace calendar is already crowded, and the gap for domestic first-class cricket between the IPL and bilateral series keeps shrinking. Every extra spell is added to the debt ledger, and the debt is repaid in injuries. The most real risk in this match is not in the trophy; it is in those two bowlers' legs.

Three things to watch in the coming weeks. First, the figures on the official scorecard — who took what, in which spell. Second, Jammu & Kashmir's next red-ball innings — whether the collapse was one session or a pattern. Third, the workload reports, because a seamer's fatigue never appears on a scorecard.

One thing I am keeping for myself. During the 2026 ghost games I learned that silence can be a patch note. Here the silence is an incomplete scorecard. I saw the stadium and the server go quiet when the crowd was the only buff left — and that lesson still holds. What is missing tells us this: we know the result, we do not yet know the process. In cricket the most valuable thing is not the trophy. It is whether anyone is writing the process down.