The 113 Question: India A's 24-Run Lead Is a Fragile Edge, Not Control

Third day, second session. Sixty-six overs. Two hundred and twenty-eight for four. That is what the live feed is sending — one line, no commentary attached. But the most important number in that line is not 228. It is 113.

The fourth wicket fell at 227 — Dhruv Jurel, twelve balls, two runs, caught by substitute McKay, bowler Zak Gibson. A man who has played Test cricket walked out in a crisis and walked back after twelve deliveries. Behind him, Yash Rathod — five balls, one run, not out.

In forty-four years I have learned one thing on the nets and not in a press conference: the scorecard never lies, but it never tells the whole truth either. Eight runs can hide a whole boy's story. And a 113 all out can hide an entire innings' story — if you read it as a number and nothing else.

So today I want to read that 113. Because the 228 for 4 has been made by the same team that, on the same ground against the same ball, collapsed to 113. And when one team plays two innings that far apart, on one pitch, in one match, the question is not which innings is 'real'. The question is what changed in between.

What the feed gives, and what it withholds

First, the part that has to be stated, because without it everything else is unfinished. The report this analysis rests on is a live-score feed. No byline. No venue. No word on who won the toss. No pitch report. No first-innings bowling detail. And no statement of whether this match is scheduled for four days or five.

Six of the fourteen information points carry 'Source: None'. That is not a complaint — it is a condition of the method. When all you have is arithmetic and player-level data, you can draw arithmetic and player-level conclusions. You cannot tell me what the pitch did, because you were not standing there.

I stood outside that door long enough to learn what silence costs. In 2026 the Chinnaswamy dressing room was closed to me — the doorman had simply never had a woman ask, so he had no reason to refuse — so I built my own access: 6:45 a.m. nets. Sunil Joshi's arm angle, Vijay Bharadwaj's trigger movement, three hours before any press conference. Four months, three hundred words a day.

Same discipline applies here. What the feed withholds, I have to name as withheld. Because when the single biggest event of a match — a collapse to 113 — is dropped into a report with no explanation attached, that is not an oversight. It is an editorial choice. And that choice has a cost too.

The arithmetic: what twenty-four runs actually means

Now the part I can state with full confidence, because it is only subtraction.

New Zealand A made 317 in the first innings. India A collapsed to 113 — a deficit of 204. In the second innings India A are 228 for 4 in 66 overs.

Lead = 228 − (317 − 113) = twenty-four runs, with six wickets in hand.

The arithmetic is simple and therefore merciless. Two hundred and twenty-eight runs in sixty-six overs is a run rate of 3.45. In a session-by-session red-ball match, 3.45 is not a dominance number. It is a survival number. India A batted sixty-six overs, erased a deficit of 204, and added twenty-four runs on top of it.

One distinction needs to be made plainly, because Hindi cricket coverage gets it wrong constantly: a lead and control are not the same thing. A side twenty-four ahead with six wickets left has options, not safety. If two wickets fall for ten runs tomorrow morning, that same side is 34 for 6 — and then 113 is not a bad dream, it is a template.

That is why this match is still open at the second session of day three. This is what I call a fragile edge, not control. And the biggest enemy of a team standing on a fragile edge is not the opposition. It is the memory of its own previous innings.

The follow-on question: the most interesting thing nobody will discuss

Here is something that will almost vanish from the coverage.

India A trailed by 204 on first innings. The follow-on threshold is 200 in a five-day match and 150 in a three- or four-day match. Both thresholds were cleared. Which means that unless this tour's playing conditions depart from the standard Laws, New Zealand A chose not to enforce — it batted again, or sent India A back in without trapping them.

The reflex response will be: 'New Zealand A missed a trick.' I don't agree, and the reason is structural, not technical.

A-team cricket is a development product, not a competition product. Wickets are not the currency here. Overs are. You are not playing Zak Gibson so that he wins you a match — you are playing him so that in two years he has the habit of bowling a twenty-over spell. Enforcing the follow-on means sending your own bowlers straight back out for a third innings, immediately after a 113-run second innings, in heat, without recovery.

So when you read the scoreboard and conclude New Zealand A went soft, you may be misreading it. That is not softness. It is load management. And it is the least understood part of A cricket — from outside it looks like a match, from inside it is a training session with a public score.

But I have to attach a caveat, because this conclusion rests on an assumption. Whether the match is four days or five is not in the source. If it is four, the meaning of a twenty-four-run lead changes entirely — the fourth session of the fourth day is the fastest of the match, and defending twenty-four with six wickets standing is a different kind of difficulty. That gap is large enough that any 'strategic' conclusion without it is incomplete. I am holding it as an inference, not a fact.

Gibson's three maidens and Lennox's 5.43

Now the number I consider the most revealing in this entire match — and the one nobody has picked up.

Zak Gibson: three maidens in twelve overs. Jayden Lennox, left-arm spinner: economy 5.43.

That pair is a pitch report without a pitch report. A seamer bowling three maidens in twelve overs is finding something in the air or off the seam. And a spinner going at 5.43 at the same time is evidence that India A decided to attack the spinner — not to survive him, to attack him.

What deserves attention is how a team run rate of 3.45 and an individual economy of 5.43 coexist. There is only one answer: India A targeted the spinner at one end and blocked the seamer at the other. That is not instinctive. That is a plan, and it is the most mature part of the innings that reached 228 for 4.

But there is a crack here too. If the spinner is that expensive, why is New Zealand A giving him the overs? The answer is the same structural one. The spinner needs overs too. And that is where the real tension of this match shows: two teams are standing on the same ground, one trying to win and one trying to teach. India A is trying to win, so it attacks the spinner. New Zealand A is trying to teach, so it bowls the spinner.

I am not saying either is wrong. I am saying that before you read this scorecard, you need to know which match's scorecard you are reading.

Jurel's twelve balls

Dhruv Jurel has played Test cricket. He is among the most experienced batters in this innings. And when his team had lost four wickets at 227, when the ghost of 113 was at its most alive, he batted twelve balls and made two.

I will not call that a failure. I will call it a timestamp.

Because the real question is not that Jurel was out for two. The real question is who trapped him in twelve balls — and the answer is Gibson. The same Gibson with three maidens in twelve overs. Same bowler, same conditions, and India A's most experienced batter walked into the same trap.

That is proof of the thing I said above: this pitch can still deliver the jolt that made 113. What has changed is not the quality of the batting. What has changed is the age of the ball and the gap between new balls. At sixty-six overs, with the ball old, the fear of 113 recedes. The moment the ball is new again, the fear returns.

And that is where the whole weight of the fourth morning comes from. If India A survived the night at 228 for 4, the new ball arrives in the morning. Gibson will be fresh. And Jurel's twelve balls are the warning the scorecard recorded and nobody read.

Padikkal: the gap between price and biography

The first auction taught me that a price is a story told too fast. In February 2026 I sat in a Mumbai auction room while the IPL priced cricket for the first time. Royal Challengers Bangalore were spending from a five-million-dollar purse with Rahul Dravid already installed as icon. By April I was on the RCB beat. Seventh place in an eight-team league, and a squad list that changed faster than a newspaper could print it.

What I learned that year still holds: auction price and cricket biography do not travel together. Some players are bought very expensively and their red-ball career moves very slowly.

Devdutt Padikkal belongs in that category — and I say that as a structural fact, not a slight. His name reached the market very early. His red-ball record did not move at that speed. And now, in the second session of day three, with a twenty-four-run lead and six wickets in hand, the entire responsibility of India A's innings has landed on the one batter whose red-ball story is still being written.

This is the moment when auction price and ground reality stand face to face. And that moment never arrives in a press conference. It arrives when the ball is new on the fourth morning and there are only two men at the crease.

I learned that lesson on the night of 29 May 2026 at the Chinnaswamy — the IPL final, lost to Sunrisers Hyderabad by eight runs despite Virat Kohli's 973-run season. A twenty-one-year-old seamer bowled the decisive nineteenth over. At 2 a.m., with the ground empty and litter still in the stands, I made a quiet decision: he would not be the lede. I wrote the defeat through Kohli's season and the team's fielding, and stayed until 4 a.m. so that the young bowler's own words sat in context.

After that I set a rule — never make a player under twenty-three the lede of a defeat. It cost me a few sharp calls from desk editors. It bought me something rarer: by the 2026 season, players were texting me their injury news before the franchise announced it.

The rule holds today. Yash Rathod, five balls, one run, not out. I will not make him the hero of this piece. He is a name on the last line of a scorecard. But I will say this: when Gibson takes the new ball on the fourth morning, the second man at the crease will be him.

The outside misreading: 228 for 4 is not a turnaround

Now the part I wrote this whole piece for.

When people see 113 and 228 for 4 side by side, the conclusion will be: 'India A staged a superb comeback.' That is easy to read, and it is wrong.

Two hundred and twenty-eight runs in sixty-six overs. A run rate of 3.45. Four wickets down. A deficit of 214 erased and a lead of 24 built.

That is not a turnaround. That is a very slow, very laborious, very fragile stop. A turnaround is when you are going at four and a quarter an over and the bowling is breaking. The bowling is not breaking here. Gibson's three maidens say so. What India A did was refuse to repeat its first-innings mistake — it batted slowly.

And that is precisely the point where the outside reading inverts. If the collapse to 113 was a bowling achievement, then 228 for 4 is not the end of that achievement. It is its pause. The new ball can bring it back. Reading this innings as 'success' is the same error as making a young bowler the face of a defeat in 2026 — you mistake one small part of a larger story for the whole story.

The second outside misreading is that 'New Zealand A didn't enforce the follow-on, so it released the pressure.' I have already argued this can be load management. I will add a third angle: if you send India A back in, you send it in carrying the psychological weight of 113. By not enforcing, New Zealand A declined to hand it that weight — it gave it a fresh mind. And the fresh mind made 228 for 4.

So what people are reading as New Zealand A's slackness may be one of the causes of India A's recovery. That is a fully inverted reading, and I know it will sit uncomfortably. But the scoreboard offers no evidence against it.

113 was not an accident

Back to the number I started with.

A team that collapses to 113 in reply to 317 does not suddenly make 228 for 4 in the next innings. Something has to change. There are three possibilities, and the source is silent on all three.

First — the conditions genuinely eased. The pitch dried, the seam went, the ball got old. This is the most common explanation and the least verified.

Second — New Zealand A's bowling depth ran thin. The bowler who produced 113 in the first innings was not as dangerous in the second. This happens constantly in A cricket, because seamers carry over limits.

Third — India A changed its method. It did not repeat its first-innings mistake. And Lennox's 5.43 is the evidence for this third possibility: somebody decided the spinner would be attacked.

My estimate leans towards a mix of the third and the second, not the first. Because if the pitch had eased that dramatically, Gibson could not have bowled three maidens in twelve overs. He did. Which means the ball is still talking.

And that is the real tension of this match. India A has made 228 on the pitch that made 113, not on a new one. So 113 was not a bad day. It is a possibility of a pitch that still exists.

What to watch next

I don't usually predict. In 2026, when I spent sixty-five days inside the UAE bubble — three hotels, a sanitised team bus, sixty thousand empty seats in Dubai and Abu Dhabi — I learned that in an empty stadium you can hear the coaching from the boundary rope. There I watched RCB bowl Washington Sundar inside the powerplay and change fields by batter rather than by over. I filed match reports and, with my old radio ear, a four-hundred-word note on what an empty stadium actually sounds like: studs, a lid, one voice.

That experience gave me a habit: I attach a tactical explainer to every match report, written for fans rather than coaches. Not 'the powerplay spinner took 1 for 22' — 'why the powerplay spinner'.

Same here. Watch three things on the fourth morning, not the scoreboard.

One — how long Gibson's first spell runs. If he bowls five or six overs straight, New Zealand A is in a winning posture. If he is pulled after three, it is still managing loads — and then you will know what this tour is prioritising.

Two — whether Lennox gets a second over with the new ball. If he does, New Zealand A has prepared an answer to India A's attack. If he doesn't, India A's plan against spin keeps working.

Three — who walks in at number seven. This is the most neglected question of the whole match. Everyone knows who bats at three. Nobody asks who bats at seven. But with a twenty-four-run lead and six wickets in hand, the entire outcome of the fourth day rests on it.

If the man at seven can bat thirty overs, India A goes to 350 and this match drifts towards a draw. If the man at seven plays ten balls and leaves — the way Jurel left after twelve — then 113 becomes an option again.

And that is what draws me to this match more than anything. 228 for 4 is not a statement. It is a question whose answer has not arrived. And anyone who supplies that answer on the evening of day three is in the same hurry as the man who mistakes an auction price for a career.

I will wait. Fourth morning, first ball, first spell, first decision. I will write after that.