228/7 and a 117-Run Lead: India A's First Innings Was 111, and It Isn't Printed Anywhere

228 for 7. 69.2 overs. A lead of 117.

Three numbers are printed in the Day 2 report. The fourth is buried inside them. Subtract 117 from 228 and India A's first innings was 111. The report never states it; the reader has to derive it, and the moment he does, the whole day reads differently.

The cost of that omission lands on the reader. Until 111 surfaces, "New Zealand A made 228 for 7" sounds like a slow, patient innings. Once 111 surfaces, it becomes the completed ruin of an entire innings the scorecard has not yet bothered to record. One number changes the text.

Gahunje, February 2026. I was 24, a junior video analyst, and every report that week said the pitch did the work. I logged all 1,043 deliveries of that morning — release point, length bucket, trigger movement — because I wanted the release point, not the weather. The rule I have kept since: the number the report withholds is the first number you extract. Today it is 111.

The full ledger for Day 2:

| Metric | Figure | |---|---| | New Zealand A | 228/7, 69.2 overs | | Run rate | 3.29 per over | | Lead | 117 runs | | India A first innings (derived) | ~111 runs | | Rhys Mariu (capt) | 76 off 137 balls, SR ~55 | | Curtis Heaphy | 44 off 134 balls, SR ~33 | | Dean Foxcroft | 33* | | Mitchell Hay | 24 | | Anshul Kamboj | 3/32 | | Auqib Nabi | 2 wickets, consecutive balls | | Akash Deep / Mukesh Choudhary | 1 wicket each |

What the report does tell us: after early losses the New Zealand A middle order rebuilt the innings, and Auqib Nabi broke the tempo by removing Jayden Lennox and Tim Robinson off successive deliveries. What it does not tell us: the venue, the toss, the weather, or how many overs any bowler sent down. This is an unofficial Test — first-class status, no official Test status.

A run rate of 3.29 with strike rates of 55 and 33 looks dead in the T20 dictionary. In the red-ball dictionary those are job descriptions. Mariu's job was to bat 137 balls, because as captain his task was the session, not the score. Heaphy's job was to hold the other end. A batter who faces 134 balls at a strike rate of 33 was not failing; he was doing the thing he was sent in to do. When two different batters crawl at the same tempo, the cheapest explanation is not that both froze. The cheapest explanation is that the bowlers kept landing the ball in the same place and the batters had nothing to hit.

India A's five wickets are spread across four seamers — Kamboj 3, Nabi 2, Akash Deep 1, Mukesh Choudhary 1, with two still standing. This is a shared attack rather than a one-man show, and that is the real Indian strength here: Nabi's two-in-two came out of collective pressure, not isolated magic. Kamboj's 3/32 is the cheapest return of the day and should be logged as exactly that — a return, not an identity.

One administrative point prices this entire ledger: an "unofficial Test" carries first-class status but not Test status. None of these numbers move the ICC World Test Championship table and none enter official Test records. It is a separate book, and its real pay-off is filed in a player's selection dossier, not in a record book. Anyone citing Kamboj's 3/32 tomorrow as a Test figure is posting to the wrong account.

Two errors will come out of this report, and both are errors I have made before.

First: Kamboj's 3/32 will be converted into "India have found their next fast bowler" inside a week. One innings. No career average, no format history, no home-away splits. I have made this mistake — January 2026, the Bengaluru auction room, a 240-player shortlist, and my note on Jofra Archer ran to two lines at a 72-lakh listing. The room spent 12.5 crore on Ben Stokes and 11.5 crore on Jaydev Unadkat that day. I learned more about valuation from a room of panicking bidders than from any textbook, and the lesson was that my note had the right player in the wrong format. The same trap sits here: reading one innings as a career.

Second: calling 111 a batting crisis. The report does not even name the ground. I cannot tell you whether this was a seaming surface, uneven bounce, or slow turn. When the surface is unreadable, the verdict on the batting is unreadable too. Three blind spots in my model are wide open right now — venue, toss, and the workload of four seamers whose fitness status is not reported. A meta is just a spreadsheet that enough people agreed to believe.

The genuinely under-covered story is New Zealand A's control. A 117-run lead with three wickets left in a low-scoring match is the position New Zealand cricket culture files under quietly effective. Indian domestic media can escalate it into an India A crisis within a day, while the scorecard says the hosts made the visitors play on the hosts' terms. One concession, though: the headline writers beat my model on Day 2 by leading with Kamboj while my ledger spent the first hour insisting Nabi's double-wicket was the bigger turn. The report chose better.

Day 3 opens with the last three wickets. If New Zealand A's tail pushes the lead past 150, India A's second innings becomes a new-ball examination, and the first 20 overs will tell us whether 111 was the pitch or the technique. If the tail falls quickly, the match is open and Kamboj's three wickets remain the day's largest number four days later.

I will track Kamboj and Nabi across the rest of this series with one question: does 3/32 repeat? If it does, a selection file gains an entry. If it does not, this was a good morning, not a career. And the next time you read a live report from this tour, check one thing first — whether the first-innings total is actually printed.