Between 113 and 228/4: India A's 24-Run Lead Is an Over-Budget, Not a Score

65.1 overs. Score 227/4. Dhruv Jurel caught at cover — substitute fielder McKay took it, bowler Zak Gibson. Jurel had faced 12 balls for 2 runs. The scoreboard moved to 228/4 and the commentary box announced that India A had recovered from 113 all out.

I did not look at the scoreboard. I looked at the 12.

An India-capped wicketkeeper-batter, rated the most match-ready Indian batsman on this tour, walked back as the fourth wicket at 227 — 12 balls, 2 runs. Had those 12 balls been 40, India A would have begun the fourth morning not 24 ahead but 55-60 ahead, and the price of New Zealand A's entire plan would have changed. The place in cricket writing where "character" and "momentum" get inserted is, in reality, a place that belongs to a ball count.

This report is an audit of that count.

Context: this is not a Test, and that is exactly why it matters

India A versus New Zealand A, first unofficial Test, Day 3, second session. This is not an ICC Test — no caps, no WTC points, no official record. And yet nothing is more valuable in Indian cricket, because whatever happens here is entered directly into a selection spreadsheet. The unofficial Test is where careers are made and broken, and where one innings of 113 can settle the team sheet for the next six months. The second XI is the hardest team in world sport — because the bottleneck there is selection, not talent.

Now the model's assumptions, because in this report they come first and the analysis second. My input is a Times of India live-score/blog-format feed — no byline, no venue, no toss, no pitch report, no first-innings bowling detail, and no statement of whether the match is a four-day or five-day game. Six of fourteen information points carry "Source: None." This is a scorecard-derived feed, not a reported feature.

That means: factual reliability of the score is medium-high, contextual reliability is low. I will run the phase ledger only as far as this feed can carry it — arithmetic, over-budgets, individual balls. Where the base fails, I will mark myself as low-confidence rather than build a clean grid that would not be true.

One arithmetic snag must be settled at the start, because the whole report stands on it. New Zealand A made 317; India A were bowled out for 113 in the first innings — a deficit of 204. The score is now 228/4. Subtract 204 from 228 and 24 remains. That lead only holds if these are India A's second-innings runs and New Zealand A have not batted again — that is, a follow-on situation. The feed does not clarify this. The follow-on threshold is 200 in a five-day match and 150 in a three- or four-day match; under either, a deficit of 204 clears the bar, so the option existed. An alternative reading is that New Zealand A declined to enforce and batted again — but then 228/4 could not be India A's score. So I am working on the follow-on reading and marking it medium-confidence.

Core: six phases, each with its own budget

The phase map said a deficit of 204; the scoreboard said a lead of 24. Both are true. Both belong to the same match.

Phase one — New Zealand A's 317. This is a budget, and its biggest truth is that 317 is not a satisfying score under any conditions. A first-innings 317 in multi-day cricket is usually a debt of a few dozen runs, because it means that in some session or other the bowling side won its share. The problem is that the feed records nothing of how the 317 was built — who anchored, who wobbled, how many runs stood at each wicket. So my read of this phase is incomplete. [Confidence: Low]

Phase two — India A's 113 all out. This is the single largest number in the report and it is entirely unexplained in the source. A 113 all out is not a moment. It is a sequence. And since the feed names no bowler, I will not claim a cause. But there are two clues pointing one way. First — Zak Gibson, a seamer, bowled three maidens in 12 overs. Second — Jayden Lennox, a left-arm spinner, went at 5.43 runs per over. Maidens on seam, 5.43 on spin: that pairing says the new ball's pace and movement were the real issue, and spin could not be stopped from leaking. The 113 collapse fits that picture, even if the feed carries no direct proof of it. [Confidence: Low-Medium]

Phase three — the 204 deficit, and the follow-on decision. This is the least reported and most expensive decision in the match. Choosing to bowl again after skittling a side for 113 is not a technical decision; it is an economic one. The entire purpose of an A tour is to give overs to both sets of players — seamer workloads, a young spinner's confidence, a batsman's second chance. Enforce the follow-on and you demand another 40-50 overs from bowlers you were supposed to protect. So if New Zealand A enforced, it was a selection-economy call that no scoreboard will ever record.

Phase four — 228/4 in 66 overs, run rate 3.45. Here is something nobody is writing. On a surface where one side was bowled out for 113, scoring at 3.45 an over in the second innings is not a small thing. That rate says batting has become easier — either the new ball's bite is gone, or the surface has dried and settled, or New Zealand A's bowling depth thins once the new ball is spent. Which of the three, the feed does not say. But 3.45 does mean that 113 was not the level of the surface — it was an event. And events repeat.

Phase five — Jurel's 12 balls. This phase is small, 13 balls long, and it carries the most weight. Losing the fourth wicket at 227 means the recognised top order is finished. Jurel, 2 off 12 — a strike rate of 16.67. A batsman whose job is both to shepherd the tail and to keep the score moving cannot return in 12 balls without turning a 24-run lead into a figure rather than a cushion.

Phase six — what remains. Yash Rathod 1 not out off 5. Below him, the lower order. Which means the whole budget of Day 4 sits on Devdutt Padikkal's bat — how long he stays, how many overs he eats, and how much rest he gives New Zealand A's seamers before they take the second new ball. India A's lead is not 24 runs; it is however many overs Padikkal can stretch into Day 4.

Contrarian: the accepted story, and the part it drops

Now the strongest version of the opposing case first. Anyone covering this match will write: reaching 228/4 after being bowled out for 113 is proof of character, the team did not fold, young batsmen answered under pressure. And I do not find that case weak. Getting from 204 behind to a lead with six wickets in hand, against the red ball, in the second innings of Day 3 — that is a genuine skill, and there is no reason to deny it.

My objection is elsewhere. The story says the match "turned." I say the match did not turn — its budget was reallocated. And the reallocation happened in two places, one of them invisible. The first: the dying of the new ball, which converted the surface of 113 into the surface of 228/4. That was not a decision by cricketers; it was a decision by the age of the ball. The second, and the real blind spot: the follow-on call that will never appear on a scoreboard but which set the shape of this match. If New Zealand A enforced, they traded control of the game for a tour-management argument — and the credit for India A being within 24 runs belongs partly to that trade.

And a third thing is entirely unspoken: this match has no venue, no pitch report, no toss. That means the 113 is not part of any story — it is a number an Indian selector will enter into a spreadsheet without context. And that is the real problem with the second XI. The Ranji Trophy's problem is relevance, not quality — and the unofficial Test shares it. A 113 with no venue, no pitch and no named opposing bowler is not useful for selection; it is useful for punishment.

I stripped the crowd out, and the truth walked in. Reading a live-score feed makes one thing clear: every line of the blog tells you what happened, none tells you why. The "why" behind 228/4 in 66 overs is recorded in no feed anywhere. And until it is, the 113 can be turned into any story at all — in any direction.

Takeaway: what to watch on Day 4

My years of watching this format say such matches end in only two ways, and both are forecast in the first session of Day 4. If Padikkal survives to lunch and the lead moves from 24 to 90-100, this match drifts to a draw and 113 becomes just a bad morning. If the last six wickets fall inside 60 runs, the phase ledger was right all along and the question moves from the 113 to the overs that preceded it.

Either way, one number I will be counting on Day 4: how many maidens New Zealand A's seamers bowl in the first ten overs with the new ball. If that number goes above three, the whole story of this match is written right there — in the 113, and in all 228 that followed.