A 24-Run Lead and the 113 Nobody Explained: India A's Day 3 Leaves the Scorecard Holding Half the Story

Three things I saw — I have written that heading at the top of the first page of every match notebook since 2026. On that June evening in London the old broadsheet cricket page had already closed and I was handed a live blog instead. What I learned then is that the most important things in a match usually hide in the line the scorecard gives the least room to. On the third day of this unofficial Test between India A and New Zealand A, my notebook opened with one entry, and the way the card wrote it: Dhruv Jurel, c sub McKay b Gibson, 2 (12).

Sub McKay. Three words. No press box echoed his name, no highlight package carried that catch. But at the moment the match tilted, the ball was in his hands. Forty years into this job and it still bothers me — the scorecard gives three words to the man who did the hardest thing, and a full paragraph to the man who merely raised a bat.

The only weather report in this entire feed is buried inside bowling figures: seamer Zak Gibson, three maidens in twelve overs, and left-arm spinner Jayden Lennox going at 5.43 an over. A fast bowler with three maidens in twelve is not attacking; he is holding. And a spinner conceding five and a half an over is telling you plainly that there is no turn in the air, or that the batsmen have read him. Those two lines are this match's pitch report. That is all we have been given.

One thing needs saying plainly, because it is the foundation of everything below. What reached me is not a reported feature; it is a live-score feed. No byline, no venue, no toss, no pitch report, no first-innings bowling detail. Six of the fourteen information points carry 'Source: None.' When I sat in an editor's chair in 2026, a match report began with the morning pitch report and ended with the evening quote. Now the score arrives at four in the afternoon and nothing arrives with it. The press room went quiet before the stadium did, and the scorecard is now quiet in the same way — the number is present, the testimony is gone.

What arithmetic survives is clean enough to work on. New Zealand A were bowled out for 317. India A were bowled out for 113 — a deficit of 204. By the second session of Day 3, India A were 228/4 in 66 overs, a run rate of 3.45. Subtract: 228 minus 204 leaves 24 runs, with six wickets in hand.

That is not control. That is a thin, trembling lead that one session can overturn.

Start with the question nobody asked. India A trailed by 204 on the 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. Unless this tour's playing conditions depart from the standard Laws, New Zealand A declined to enforce — they chose to bat again, or chose not to send India A back in. That is the largest tactical fact in the match and it is discussed nowhere in the source.

Why not enforce? The surface answer is that the captain was cautious. My experience says the reason on A tours is usually the reverse. These tours carry four bowlers, two on the bench, and another unofficial Test the following week. Asking a quick to bowl thirty-two overs twice in three days is a way of ruining his next series. A captain who does not enforce is not protecting the result — he is protecting four bowlers' lungs. And it is equally true that if he believed his attack could produce another 113, he would have enforced. Not enforcing is a confession about bowling depth, about life after the new ball. Gibson's three maidens in twelve overs are the same confession in another language. He was not hunting a wicket; he was buying his colleagues a breath.

Now the innings nobody has narrated. A side bowled out for 113 does not reach 228/4 at 3.45 on the same surface unless one of two things happened — conditions genuinely eased, or the opposition's bowling depth fell away once the new ball lost its hardness. The run rate is a statement in itself. 3.45 is not a counterattack. A counterattack runs above 4.5, where the batsman accepts risk. 3.45 means accumulation, counting, squeezing over after over. India A built this innings on patience rather than aggression — and the credit belongs not to any one hundred but to an unnamed batting plan the broadcast never shows.

One technical detail, only one, because it explains the result. Gibson's three maidens tell you the seam position — the part of the ball striking the grass — mattered in the first two sessions. A bowler with three maidens in twelve is hitting one length, from one seam position, into the batsman's front pad. That is not the surface; that is the age of the ball. On the third day, in a second innings, once the ball is old the seam stands up straight and the batsman learns to leave it. India A's 228/4 is the product of that learning. But note the reverse, which is equally true. When the second new ball comes, the seam stands up again.

And that is where the most irritating line on the card appears. Dhruv Jurel — among the most experienced names in this side, a man who has kept wicket for India — fell as the fourth wicket at 227, for two off twelve balls. The recognised top order is gone. At the crease is Yash Rathod, one off five, and behind him the same lower order that wrote 113 in the first innings.

At this moment India A's entire lead rests on one bat — Devdutt Padikkal, who must survive into Day 4. That is not a picture of strength; it is an innings where one more wicket will summon the 113 back into the room.

Now the people whose names never travel beyond a three-word scorecard line. Sub McKay, who took the catch. The local curator who decided how much grass to leave on it this morning, and whose name appears nowhere in the feed. The second XI coach and the tour management who built this calendar. And the scorer whose book records that the fourth wicket fell at 65.1 overs — the only place where this moment is written down. Zak Gibson's name will not appear on any auction sheet. But three maidens in twelve overs is the kind of work only an A tour records, because only here is no broadcast measuring his pressure.

One more point, about data, because it is an old complaint of mine. People look at heatmaps and believe they have understood a player's role — to me that is reading tea leaves. A heatmap shows shape, not job. A scorecard without a pitch report is exactly the same thing. 228/4 tells you where the batsmen stood, not what conditions they walked through. So what I have done here is arithmetic, not analysis. Where the facts were absent, I did not guess — I recorded the absence.

Now the reading that looks easiest from outside. Anyone glancing at the top two lines will say India A fought back superbly, took the lead, hold the initiative. Wrong. Twenty-four runs with six wickets in hand in the last session of Day 3 is not a lead; it is a stay of execution. The number that matters is not 228. It is 113. A team with a 113 in its recent memory cannot use the word control; it can only play with a warning attached.

The second thing people will file under 'caution.' If declining the follow-on was caution, it was caution about workload, not about the result — and the distinction matters. A captain who does not enforce because he fears the result is conceding his team's weakness. I must also concede that the strength of this conclusion is exactly the strength of the information — and the match duration, the venue and the conditions are all absent. This analysis is half-built, and I will call it half-built.

What to watch on the fourth morning is clear. First session. Second new ball. If India A push the lead towards 250–260, the match is alive and New Zealand A must face a real target in the fourth innings. If the last six go for under eighty, we are watching the 113 again in different clothes. And the question nobody in this feed asked — who is the curator, and what did he leave on the surface this morning? Until that answer arrives, we are only adding numbers, not reading cricket.