A 24-Run Lead, Six Wickets Left — and the 113 That Nobody Has Explained

A 24-Run Lead, Six Wickets Left — and the 113 That Nobody Has Explained

The catch at 227

Second session, day three. 65.1 overs. The board read 227/3 and Dhruv Jurel was on strike — twelve balls, two runs. Zak Gibson found the edge, and the catch went to substitute fielder McKay. 227/4. A few minutes later the 66th over was done, the score had moved to 228/4, and Yash Rathod was unbeaten on one off five.

I read that small scoreboard shift three times, because the match sits inside it. Jurel has played Test cricket for India. He walked off as the fourth wicket at 227, which means the recognised top order was gone and the man who replaced him had five balls to his name. The moment India A most needed to consolidate was the moment their most experienced lower-middle-order batter was walking back.

The catch was taken by a substitute, which is not a trivial detail. In A-team cricket the substitute is usually a squad player doing a twelfth-man shift — a man waiting for his own innings while holding on to somebody else's mistake. That is the whole texture of these games.

The scoreboard says all of this. It does not say what the ball was doing in the morning, which way the wind blew, or how a side bowled out for 113 was suddenly batting at 3.45 an over three hours later. That gap is the real story of this match.

The arithmetic

Start with what is actually on the record. According to the Times of India live score feed, New Zealand A made 317 in their first innings. India A were bowled out for 113 — a deficit of 204. By the second session of day three, India A had reached 228/4 in 66 overs at 3.45 an over.

One more number falls out of those three, and it is the spine of this piece: India A's lead is 24 runs, with six wickets in hand. 228 minus 204 leaves 24. A side that made 113 in its first innings can climb to 228 in its second and still be only 24 ahead.

Here is a derived figure that is not in the original feed. In a five-day match, the follow-on is available when the side batting second trails by 200 or more. India A needed 118 to be safe (317 minus 118 leaves 199). They made 113 — five runs short. In a four-day match the threshold is 150, which would have required 168; they fell 55 short.

Five runs. One cover drive, one missed cut, one edge that went to gully instead of slip, and the whole session changes shape. This is what I love about Test cricket: the big decision on one day is usually settled by five runs on the previous one. Five days at Eden Gardens taught me that the story lives in the second chai refill, not the first.

The economics of A-team cricket

A large part of this match exists off the field. This is an unofficial Test. No Test caps, no World Test Championship points, no official record. What gets recorded is the selectors' notebook.

That is the economics of it. The IPL has broadcast rights, gate receipts, a price on every over. An A-team fixture rarely publishes an attendance figure and returns close to nothing on broadcast. The men playing it are not being paid in applause or in television money. They are being paid in the possibility that a selector opens the scorecard the next morning.

So when a player like Jurel — who has already played Test cricket for India — turns up in one of these games, he is standing in an awkward place. The staircase above him is short, and at least three people below are already reaching for the same step. Getting out for two in a match like this is not just a wicket; it is a sentence that gets read aloud in a review meeting.

And this is where thin bowling attacks get exposed. Teams like New Zealand A do not come on these tours only to play. They come to find out whether their fourth and fifth bowlers survive a 90-over day. The final session of a Test usually belongs to whoever has the depth.

The 113 nobody explains

The heaviest number in the file is the one the source does not explain at all: 113 all out, roughly 35.6 per cent of 317 (a ratio I have calculated myself).

I have to be clear about what I know. The feed carries no venue, no toss, no pitch report. That sounds like a technicality. It is not. You cannot write the story of a 113 all out without knowing what the ball was doing. On a ground where the new ball seams, 113 is an excuse. On a ground that eases on day three, 113 is something else entirely.

One clue sits in the economy column. Seamer Zak Gibson bowled 12 overs with three maidens. Left-arm spinner Jayden Lennox went at 5.43 an over.

Three maidens in twelve overs means roughly one over in four produced no run at all. In red-ball cricket that tells you Gibson found a spell where the batter could not score without paying for it. And a spinner conceding at 5.43 tells you the batters went after him deliberately — either stepping out to hit against the turn or staying deep and playing it late.

Both readings are possible, and I will be honest that the data does not let me choose. But one inference holds: if the pitch were turning sharply, a left-arm spinner would not be going at 5.43 in a match where the first innings ended at 113. Either the surface was not doing much, or India A made a conscious decision to target him.

That explains the character of the second innings. 3.45 an over is not the run rate of a side trying to survive. It is the run rate of a side that knows standing still means the deficit grows.

The follow-on question

New Zealand A did not enforce the follow-on. India A trailed by 204, clearing both standard thresholds — 200 for a five-day match, 150 for a three- or four-day match — and yet they batted again. Unless this tour's playing conditions differ from the standard Laws, that was a choice.

The usual reading is bowler workload, or a desire to let the pitch deteriorate further before setting a target. There is a third reading, and I think it is the honest one. Enforcing the follow-on means asking your attack for another 90 overs on the same day, in the same heat, with the same ball. If only two of your bowlers are reliable, you do not take that risk. You send your batters out, add runs, and give the bowlers a night's sleep.

The bowling figures support it. Gibson with three maidens and Lennox at 5.43 suggests an attack running on two engines. What the third and fourth options produced is not in the feed.

If that is right, then 228/4 means something different from what it looks like. It is not New Zealand A's generosity. It is an admission of their own ceiling.

Padikkal's burden, Rathod's wait

Back to 227/4. Jurel out, Rathod in, and at the other end the batter the whole innings rests on — Devdutt Padikkal.

With a 24-run lead and six wickets left, the fourth wicket already gone, what remains is a set batter, a new batter, a wicketkeeper and four bowlers. That is the batting order shape where one mistake puts you back inside the 113.

The direction of the match stops being collective and becomes personal. India A's day four depends on how long one man stays in. If Padikkal survives the morning, the lead moves from 24 towards 80 or 100, and New Zealand A face a fourth-innings target on a surface where a side has already been bowled out for 113 — where even 120 looks like a wall. If he goes in the first hour, India A probably stall near 250, the lead sits around 45 to 50, and the same question returns: how durable is the lower order?

One thing nags at me. If the first innings was purely a new-ball phenomenon, then four wickets in 66 overs — roughly one every 16 or 17 overs — is ordinary Test cricket. But 113 all out does not sit comfortably beside that ordinariness. Something happened in the first innings that is not happening now, and that something is what reporting gives you and a feed does not.

I also watch how much a good innings and a bad one can change the direction of a career in these games. Rathod has five balls behind him and may have a hundred by the fourth morning. His score will matter less than how he stands there.

The contrarian read: this is not a recovery

The number everyone likes is 228/4. The journey from 113 to 228 reads like a comeback. I think that is the wrong frame.

Add it up. India A made 228 in the second innings, but they also conceded a 204-run deficit in the first. Put the two together and their position in the match is plus 24. Had they made 250 first time and been 80/4 now, they would be in worse shape but would not look better. The arithmetic is the same; only the optics changed.

This is not a recovery. It is a session in which a side is paying for its own mistake, with no guarantee the bill is settled.

There is a second, journalistic point. The feed I am working from has no byline, no venue, no toss, no pitch report, no first-innings bowling detail. Six of fourteen information points carry "Source: None." I learned to keep the beat by noticing who saves whom a seat in the press box — and the same instinct applies here. Which facts land in a scorecard and which need a reporter's night's work tells you who owns the story. 113 all out is a number. Why it happened is the news, and it is missing.

When a wicket falls, I look for the person still standing in the same spot — the not-out batter taking guard for the next ball while the ground watches the new man walk in. In this match that person is Padikkal. The feed does not tell you his score. It only tells you he is there.

What to watch

Three things on the fourth morning will decide this. How many overs Gibson bowls — if he gets the new ball and produces three or four maidens, India A will not reach a 60-run lead. What Lennox's economy looks like — if it drops below four, the pitch has turned and batting last becomes the hardest job in the match. And how long Padikkal lasts.

A guess, offered as a guess: if India A reach 300, New Zealand A chase roughly 100 on a surface where a side has already been rolled for 113, and that target can flip in a session. If India A fold near 250, the target is around 50 and the game can end the same day. The gap between those scenarios is 50 runs.

That is Test cricket — five days settled in twenty minutes, and five runs (113 against 118) deciding whether a follow-on question even exists. The question is not whether India A win. It is when someone explains the 113. Until then, this series runs on an unfinished scorecard.