India A's Hidden 111, Kamboj's 3/32, and an 'Unofficial Test' With No Named Venue

Three wickets for 32. By tomorrow morning that will be the number in every headline — Anshul Kamboj, 3/32 against New Zealand A. The number is correct and I will not shrink it. But the number that explains this match is 111, and 111 does not appear anywhere in that Times of India live-score report. I had to do the subtraction myself: New Zealand A are 228/7, leading by 117, which puts India A's first innings at roughly 111. Two hundred and twenty-eight minus one hundred and seventeen. That is the whole of the arithmetic.

Now stop and read that report again. No venue. No toss. No weather. Not one line about the pitch. A Test match — unofficial, yes — is in progress and the reader cannot even establish which country it is being played in. A report that cannot supply that much is not a report about cricket. It is a report about us, and about the system that decides which matches deserve coverage and which do not. Nobody had that on the bingo card eight months ago: that the most interesting argument in Indian cricket this week would come out of a fixture whose scorecard runs half-empty.

What an unofficial Test actually is

The wording carries the story. An unofficial Test is a multi-day, red-ball, two-innings match with first-class status but not official Test status. It does not count towards the ICC World Test Championship and its figures do not enter Test records. It sits inside the A-tour framework, the arrangement under which the BCCI and NZC put their senior squad's back-ups against each other in red-ball cricket. The day's play, as recorded: New Zealand A reached 228/7 in 69.2 overs. Captain Rhys Mariu made 76 off 137 balls, Curtis Heaphy 44 off 134, Dean Foxcroft is 33 not out, Mitchell Hay made 24. For India A, Kamboj's three were supplemented by two from Auqib Nabi and one each from Akash Deep and Mukesh Choudhary. Nabi's two came off consecutive deliveries — the nightwatchman Jayden Lennox, then Tim Robinson.

The nightwatchman wicket tells you the shape of the innings

Nobody writes this into a scorecard, but a nightwatchman is sent out when a side has already lost three or four in the closing overs and has decided the real batter must be protected. When Nabi removed Lennox, New Zealand A had already lost wickets cheaply. Robinson went next ball — two in an over, and the hosts entirely dependent on the middle order. What followed is the innings. Mariu and Heaphy consumed 271 balls for 120 runs. Strike rates of 55 and 33. Anyone reading red-ball cricket through a T20 lens will file that as slow batting and mark both names yellow on the auction spreadsheet. In a Test context it is the opposite: it is two batters refusing to fold against the moving ball. A strike rate of 33 is not a crime in first-class cricket played in difficult conditions; it is a survival document.

Kamboj's 3/32 in context, and out of it

Place the return inside the innings. Seven wickets fell; three were his, 42.9 per cent. Two hundred and twenty-eight runs were scored; 32 came off him, 14 per cent. A bowler taking nearly half the wickets while conceding a seventh of the runs was the most effective bowler on the day. No argument there. Beyond that, judgement needs data that is simply absent — no career averages, no pace-versus-spin splits, no home-away record, no ages. Elevating a player on one innings is the mistake this ecosystem makes every season, and then pays for at the auction.

3.29 an over: the pitch, or our blind spot

Two hundred and twenty-eight in 69.2 overs is 3.29 runs per over. Two innings, both under four an over, with two top scorers striking at 55 and 33. That pattern usually means seam movement, uneven bounce, or slow turn. I will not claim it is a green seamer in New Zealand, because the venue is not named. I will say this: if you do not know the ground, you do not know the pitch, and if you do not know the pitch, you do not know whether 111 is a batting failure or the weather's rent. The scoreboard told one story today; the blank space told the truth. India A's four-pronged pace attack — Kamboj, Nabi, Akash Deep, Mukesh Choudhary — has already sent down 69.2 overs, and the report mentions no spinner's workload and no fitness status at all. Four seamers, a multi-day game, day two. That is exactly where the workload question should have started.

The board is the story; the score is its output

I was on the Deccan Chargers beat in 2026 for a Hyderabad daily, covering a side that had finished bottom of IPL 2026 with two wins from fourteen and then won the Johannesburg final the following season. I filed a piece arguing the 2026 disaster was a scouting and selection failure, not a talent failure. The desk wanted 600 words of match report; I handed them an argument with a table inside it. Since then I have kept a spreadsheet of squad turnover, season by season. It is the spine of every episode I record. Why bring it up here? Because fixtures like India A versus New Zealand A are the pipeline of Indian cricket, and nobody covers the pipeline. The Ranji Trophy is the same story: everyone cites it, nobody covers it.

Since 2026, scouting has moved from zonal selection to franchise scouting. The A tour is the last stage where a player proves himself with no camera on him — and that is the second itch. A player raised in a small system gradually becomes a satellite asset, valued somewhere he does not play, only gets sold. I say this knowing I am part of the problem, because I cover the auction too. Somebody has to say the quiet part with the mic on. Let me take you back to the night the handcuffs came out — May 2026, when the spot-fixing arrests landed and I spent four months reading charge sheets instead of team sheets. That period taught me that stories are built from documents, not press-conference quotes. The biggest document missing from this report is the name of the ground.

How I could be wrong

Here is the strongest version of the other side, because otherwise this is a mood rather than an argument. A-team live reports are written this way by convention; the score goes in the headline and the venue does not. If I treat every omission as a conspiracy, I become the reflex contrarian I spend my time criticising. Second, if the surface genuinely helped the seamers, 111 is not a humiliation — it is a par score for the day. Third, and most important: Kamboj's 3/32 may be exactly what it looks like, a good bowler on a helpful deck on a good day. My claim is deliberately small. I am not saying India A's batting is broken. I am saying we do not possess the data to say either way, and that absence is the actual story.

What comes next

My prediction, on the record: if New Zealand A's tail pushes the lead past 180 or 200, India A's second innings will not reach 150 and the next-gen batting line will go cold inside a week. If the tail falls quickly, the match is open and Kamboj's second spell becomes the most interesting thing in it. What I will track is not the one-innings 3/32 — it is whether he repeats across the rest of the series, because the question is not whether he took three wickets in a day, it is whether he has a third and fourth spell in him. And the biggest question of all has nothing to do with the score: will the next report name the ground? Eight months is nothing until you watch it happen in real time — and here we are, still unable to establish where the match is being played.