The First Warning From a Green Top: What India A's 113 All Out Actually Says — And What It Doesn't

Hook: One innings, three sixes, one uncomfortable ratio

I kept refreshing the scorecard through the evening, because the number sitting on the screen did not look like a single-session accident. 113 all out in 39.3 overs. A run rate of 2.86. Five ducks. And inside that same innings, one knock written in an entirely different language: Yash Rathod's 44 off 49, with three sixes and three fours, 38.9 percent of the team's runs on his own.

Three sixes in 49 balls on a green top is a question in itself. Either Rathod had a counter-attacking plan, or the pitch behaved differently during his stay. New Zealand A's 132-run opening stand points to the second explanation. On the same day, on the same surface, one side folded for 113 and the other reached 132 without loss. That is a story about the pitch. It is also partly a story about the batters. It is not entirely about either.

My beat habit is simple. I do not count runs first. I read dismissal modes first. The WhatsApp broadcast rebuilt my beat one trusted contact at a time for exactly this reason: where the catch went, who caught it, which ball was left alone — those small details tell you what the pitch is actually doing. Thirty thousand voices in Mumbai taught me that fandom has a pulse. Four months in the Goa bubble taught me fluent scheduled silence. Both lessons apply when you have to read the silence inside an innings: where a batter stopped, and why.

At stumps, New Zealand A were 135 for 3, leading by 22 with seven wickets in hand. Those three wickets fell in seven deliveries, from 132 for 0. Those seven balls are the most important information in this match.

Context: What an unofficial Test actually is, and why it matters

One structural fact changes the whole reading. This is an unofficial Test: a first-class fixture played under Test-like conditions without Test status. It does not enter ICC records. It does not enter a player's Test statistics. It earns no World Test Championship points. For the board it is a preparation laboratory; for the record book it is a blank page.

New Zealand A are the hosts. A green top is a legitimate home prerogative, and there is an asymmetry here that rarely gets discussed. An ICC-sanctioned Test can attract pitch ratings and demerit points. An A-series cannot. Preparing a green top carries no regulatory cost. This was not a neutral examination of technique; it was designed home advantage.

New Zealand A fielded four seamers — Simon Keene, Zak Gibson, Fraser Sheat and Kristian Clarke. India A's XI was seam-heavy too, with Akash Deep, Mukesh Choudhary, Auqib Nabi and Anshul Kamboj all bowling-capable and all dismissed in the tail. That selection read the conditions correctly and still did not protect the batting.

A reporting caveat belongs here. Every detail in this article comes from a single source, and that source contains no career averages, no home-away splits, no pace-versus-spin splits, no injury history. I am confident about what happened inside this match. I am not confident about career-level judgements. That distinction matters, because cricket discussion goes wrong most often at precisely this point: one day's data used to judge seven years of a career.

Core: The dismissal pattern is the strongest signal, not the total

Four of India A's top five were dismissed by the wicketkeeper or in the slip cordon. That is the defining fact of the innings. Keeper and slip catches mean the ball is moving off the surface — seam or seam deviation. A spin-induced collapse produces a different picture: forward short leg, midwicket, bat-pad. A reckless collapse produces a different picture too: an inflated strike rate, not a run rate of 2.86.

The simplest explanation for this batting failure is conditions plus new-ball skill, not reckless strokeplay. Scoring at roughly three an over, a side does not collapse on its own. It gets dismantled.

There is one exception. Sai Sudharsan's dismissal is the only one among the top five that does not fit the keeper-slip pattern; the mode is not stated in the source. That gap matters. As a left-hander, the angle of the ball into him is different, and that detail would tell us whether the surface was doing a bit both ways or mostly one way.

Of the five ducks, three are named — KL Rahul, Sai Sudharsan, Washington Sundar. The other two are unidentified, presumably tailenders. And a duck is not equal to a duck. A first-ball dismissal and 13 balls for 1 run are entirely different events.

Core: 122 balls, 49 runs — what survived and what did not

Yashasvi Jaiswal made 17 off 45, a strike rate of 37.8. Devdutt Padikkal made 32 off 77, a strike rate of 41.6. Together: 122 balls, 49 runs.

At first glance that reads as failure. Read more carefully, it is partial success. Surviving the new ball on a green top is not easy, and both did it. The failure was in the phase after the ball stopped moving. There is a name for this in coaching: the restart. A batter defending absolutely goes still in the feet, the bat arrives late, the hands never open into a scoring stroke. When the ball suddenly stops doing as much, that frozen state is hard to escape.

This was a conversion failure, not a survival failure. The remedies are different. Survival is fixed in the nets against the moving ball. Conversion is fixed with session-based objectives — for example, a deliberate block of scoring shots in the ten overs after the new ball is seen off.

That is what makes Rathod's innings so awkwardly important. A strike rate of 89.8 inside an innings scoring at 2.86 is close to insurrection. His three sixes suggest either that the pitch was materially easier during his stay, or that his plan was to bank runs before the ball started talking. Without session-by-session scoring data, I cannot settle that — and I would rather name the limit than paper over it.

Core: 13 balls for 1 run is a worse signal than a first-ball duck

Dhruv Jurel, wicketkeeper-batter and captain, made 1 off 13 at a strike rate of 7.7. A first-ball duck can be bad luck. Thirteen balls for one run cannot. It means he was seeing the ball and reaching it, but could not find a way to score.

There are two explanations against the new ball: a technical block, or a decisional one. Captaincy load and this kind of innings are related in my experience, and I will say plainly that this is a pattern, not a proof. Wicketkeeper-captains carry a different attentional tax. Between balls they are setting fields, talking to bowlers, thinking about reviews. Clearing the head before batting is genuinely hard. In this match that tax was visible in his bat.

The sample is small and the inference should stay small. But the flag is worth raising, because the senior series is next and his role there is doubled.

Core: The bowlers gave up more information than the batters

In a 113 all out story everyone talks about the batters. The sharper signals came from the bowling figures.

Simon Keene's 5 for 24 has to be read in two parts. He broke the top order. He also cleaned up the tail. New-ball movement and late-innings accuracy rarely live in the same bowler. Bowlers who swing it early often lose their line at the end; bowlers who are metronomic at the end often lack the early edge. Keene did both, and that is the strongest individual performance signal in the match.

Zak Gibson's three wickets should not be waved away as a support act. He dismissed Jaiswal, Padikkal and Washington Sundar — three of India A's four most experienced, Test-capped batters fell to the second seamer. The 113 came from the sustained pressure of a four-man seam attack, not one hot spell. Sheat and Clarke took one each, economically, filling the fourth and fifth seamer roles across 39.3 overs.

India A's attack worked too, at least late. Three wickets in seven balls from 132 for 0 proves the surface still offered new-ball movement. The difference was continuity. New Zealand A held the pressure with four seamers across 39.3 overs; India A took three wickets in seven balls after conceding 132.

Core: Fifty years of structure against one day's scoreline

India have played 25 Tests in New Zealand: 5 wins, 10 losses, 10 draws, a 20 percent win rate. One Test win in New Zealand since 2026. No series win there since 2026. On the 2026 tour, no innings across four reached 250.

These numbers are not decoration. They are repeated encounters with the same set of conditions. A 20 percent win rate in one country across half a century is not chance; it is a structural adaptation problem.

A methodological caveat is required, or the analysis turns lazy. 'One win since 2026' sounds enormous but describes very few matches. New Zealand tours are usually two or three Tests. A single win or loss carries disproportionate weight in the aggregate. The cause is likely a mixture of conditions and sparse scheduling rather than a psychological block alone.

Core: The gap inside the 'bench strength' story

Indian cricket has a comfortable sentence: the bench is so strong that the second XI could beat many first teams. This match tested that sentence. An A side is the bench. The scores of the four Test-capped batters here were 0, 17, 0 and 1. Those four numbers suggest the drop beneath the first XI is steeper than the narrative assumes — at least on a green top against the new ball.

The counter-argument is fair. A-team XIs are rotated for development and workload. A scoreline from this level cannot indict the senior batting unit. The correct inference is that conditions remain India's binding constraint in New Zealand. The wrong inference is that the senior side will be bowled out for 113.

Contrarian: The outside reading stops in the wrong place

The most popular reading will be that India's Test batting is finished and disaster awaits. It is comfortable, fast and wrong.

First, the structural reason. The match is unofficial. This innings enters no official record, moves no ranking, triggers no pitch-monitoring report. Accountability for it sits entirely inside the board's selection system. A performance that enters no official statistics also generates no counter-evidence, so the reaction risks being larger than the evidence. Dropping or promoting a player on one uncounted innings is possible precisely because of that vacuum.

Second, the conditions. A green top is a legitimate host prerogative with no ICC pitch-rating exposure. What India A faced was designed home advantage, not a neutral test.

Third, and most important, a format trap. Several of the names under discussion — KL Rahul, Jaiswal, Washington Sundar, Jurel — built their reputations largely in white-ball cricket. Reading a red-ball failure on a seaming track as a T20 form signal, or the reverse, is the most common error in post-innings commentary. One format's data cannot deliver another format's verdict.

Fourth, Rahul's duck. A first-innings duck against the moving ball on a green top has close to zero diagnostic value. It becomes meaningful only if repeated across the next two innings.

I should be honest about my own bias too. The appetite for a counter-intuitive angle can twist a simple truth into a complicated one. Here the simplest explanation is probably the right one: green pitch, skilled four-man seam attack with the new ball, and a batting unit whose technique is tuned to subcontinental and Australian conditions.

One under-discussed risk deserves naming. Washington Sundar made a duck and will have to bowl on this surface. For an all-rounder, that combination is the most dangerous profile: batting failure plus a heavy seam-pitch bowling load. That is the classic soft-tissue and workload injury shape. There is no workload data in the source, so this is a warning, not an accusation.

New Zealand A's own performance is a pipeline signal that gets missed. Keene's 5 for 24, Gibson's three wickets, and the Mariu-Heaphy 132-run stand say New Zealand has batting and seam depth beneath the first XI. In their post-Boult, post-Wagner transition, that matters. Both sides are being examined here, and the coverage usually forgets one of them.

Takeaway: The real question is no longer on the scoreboard

Twenty-two runs behind with seven wickets in hand is a recoverable position. The decisive variable is no longer the size of the deficit. The real question is whether India A's seam attack can repeat that seven-ball burst with the second new ball.

The pitch is still doing things; three wickets in seven balls at the close proves it. The first session of the next day will be the most informative passage of the match — how much the new ball moves, who can exploit it, how long the tail survives.

For India A, the second innings should be measured in time at the crease, not runs. How many balls, in which phase, against which seamer. A 25 off 70 that includes 30 balls against the fourth seamer after seeing off the new ball is worth more than 30 off 20 — from the perspective of the people who scheduled this tour in the first place.

I build the room first, then I write the paragraph. This room is not finished yet. In two days we will know whether 113 was a one-day story about a green top, or whether those five ducks were pointing at something larger. The question that will linger is that 122 balls for 49 runs: half the job done, and the harder half — starting again once the ball stops moving — left undone. If that same second phase stalls in the senior series, 113 will stop being an accident. It will be a pattern, and patterns are answered in the nets, not in statements.