India A vs New Zealand A, 1st Unofficial Test: 113, Then 228/4 — Where the Scoreboard Stops Explaining

Second session, Day 3. The board reads 228/4 from 66 overs, a run rate of 3.45. Directly above it hangs another number: 113. That is the innings in which India A first fell apart, and it is the one number in this entire file that arrives without a single line of explanation.

I do not have the ground. I do not have the toss. No pitch report, no account of who took the wickets in the first innings, no statement of whether this match is scheduled for four days or five. What I have is a live-score feed: no byline, no reporter, and six of fourteen information points marked, in plain type, source — none.

The notebook opens where the scoreboard stops explaining.

18 June 2026, Rusholme. I was seventeen and scoring a Manchester & District Cricket League second XI match. Rusholme CC were bowled out for 84 chasing Didsbury's 264/6 — a defeat by 180 runs. That afternoon I filled a sixty-four-page notebook: the smell of cut grass, a fielder's borrowed spikes, the captain's silence, the long walk to the bus stop. I never pitched it. It was for me. That was the day the pitch-side method began — look at the human residue after the scoreline.

Fallowfield, autumn 2026. I watched a Lancashire Bob Willis Trophy fixture on a laptop — Emirates Old Trafford, zero spectators, members' seats empty, and the loudest thing in the frame a groundskeeper's rake. I wrote 1,500 words on it; two rejections, then a Manchester cricket newsletter published it. That is where I learned to write absence as a character rather than a backdrop. It is the lesson this report needs: the most present thing in it is the thing that is missing.

So first, what is this match. It is an unofficial Test — not an ICC-recognised one. That has hard consequences: no Test caps, no World Test Championship points, no official record. It is a bilateral A-team series, which means a development tour and a selection audition running at the same time. Do not read it as a league fixture, and do not read it as an ICC event. Its real status is that what happens here shapes the senior squad list for the next two years.

Which is why the names here are not merely names. Dhruv Jurel — who has played Test cricket, who has kept wicket for India — is dismissed here as the fourth wicket. Devdutt Padikkal is at the crease, and his score is not recorded in the feed at all, which tells you something about the state of the coverage. Yash Rathod is 1 not out from five balls. On the other side there is Zak Gibson, twelve overs with three maidens in them, and Jayden Lennox, the left-arm spinner, going at 5.43 an over. Those four names are the entire architecture of this match.

Now the arithmetic, because in this file the numbers deserve more trust than the language. New Zealand A made 317 in the first innings. India A were bowled out for 113 — a deficit of 204. By the second session of Day 3, India A had reached 228/4 in 66 overs. Subtract: 228 minus 204 leaves 24 runs, with six wickets in hand. India A have a lead, not control — twenty-four runs, six wickets, and the recognised batting gone.

One detail deserves recording here, because it is the biggest clue of the day. The follow-on threshold is 200 in a five-day match and 150 in a three- or four-day match. India A trailed by 204. Both thresholds were cleared. The implication is plain: New Zealand A did not enforce the follow-on, or rather declined to. That is not a cricket decision so much as a management one. On an A tour, fast bowlers' workloads carry as much weight as the result, and the host side wants its own batters to face the same surface on which the visitors collapsed. I cannot state this with high confidence, because the scheduled length of the match is nowhere recorded and tour-specific playing conditions can depart from the standard Laws. But what is written points this way.

The bowling split hides another clue. Gibson, the seamer, bowls twelve overs with three maidens. Lennox, the left-arm spinner, concedes at 5.43. That split suggests the ball was newer or shinier, seam movement was available, and the surface offered the spinner little. A collapse to 113 fits that picture. This is inference, not proof — there is no pitch report and no ground named. I will not sell the inference as a fact.

Then the moment the day rests on. 65.1 overs, 227/4. Jurel out — caught by substitute McKay, bowled Gibson, 2 off 12. The fourth wicket. A batter who has kept wicket for India in Test cricket returns from the second innings of an unofficial Test with two runs from twelve balls, and that information sits in the brackets beside a substitute fielder's catch. After him, one run came from five balls, and at the end of the 66th over the score was 228/4. Those five balls are the real story. A side that was 204 behind, that had already been dismissed for 113, whose experienced keeper-batter had just gone for two, scores one run in five balls. That is not aggression. That is stabilisation. And stabilisation lasts exactly as long as Padikkal is there.

This is where I disagree with the obvious reading, and I will say it plainly. Anyone who reads the journey from 113 to 228/4 as a 'recovery' is reading the least useful number in the match. A side bowled out for 113 that then makes 228/4 at 3.45 on the same surface has not found form — it has found either changed conditions or a drop-off in the opposition's bowling depth once the new ball was spent. The feed offers evidence for neither. Who took the wickets in the first innings is not recorded. So I will not treat the recovery as a conclusion; I will treat it as a question. The 113 demands an explanation. The 228/4 is still waiting for one.

There is a second layer here, and it runs past cricket. We habitually read A tours as a queue for senior caps — who moves up, whose turn it is. The refusal to enforce the follow-on suggests these tours are managed environments where the result sits second and process first. The scoreboard is read as a CV, not as a league table. For Jurel this match is not 'two off twelve'; it is the question of whether he can bat long, and today gave no answer. For Rathod it is five balls of waiting. For Gibson it is three maidens in twelve overs — a sentence he is sending his selectors. And for Padikkal it is the fourth morning, which has not yet been written.

One more thing belongs in the ledger, because it is not this coverage's lie but its silence. There is no English report of this match — only a live feed. No dispatch reached the Hindi or Tamil desks. In the one country where Test cricket still fills grounds, its most consequential development fixture is running without a venue, without a toss, without commentary. Empty seats are not silence; they are a held breath — and here the seats were not empty, the coverage was. The difference is that gate receipts get counted. Coverage does not.

I do not chase the result; I chase the sentence it leaves behind. This match has left one sentence so far, and it is unfinished: twenty-four runs, six wickets, and a batter whose score appears in no feed.

The fourth morning will decide where that sentence closes. If Padikkal bats through and the lower order adds a hundred or so, New Zealand A will face a target around 200 and this becomes a real contest. If he goes in the first hour, the 113 will repeat itself and the 228/4 will have been a day's delay. And if that happens, the mention will run to two paragraphs — when the 113 was the number that asked the real question all along.

I learned to read the game from the places it failed to speak. The second session of Day 3 is one of those places. The board says 228/4 and beneath it sits 113, and nobody is writing what is happening between the two.