113 All Out: What Beat India A in New Zealand Was Not the Green Top, But a 7.7 Strike Rate

The coffee had gone cold on the kitchen table in Melbourne at half past eight in the morning, and on the laptop New Zealand's ground was showing the 39th over of India A's innings. The outfield was green, but the green wasn't the loudest thing on the screen — the shadows of the slip cordon were. Sai Sudharsan's wicket had gone down in that same over I had just opened. The ball was leaving him, the bat was coming down inside the line, and before it reached the keeper there was only a soft, almost apologetic sound. I have heard that sound for years. It is not the sound of a shot. It is the sound of a batter who has decided he will neither leave the ball nor hit it.

The innings ended in 39.3 overs. 113 runs. 2.86 an over. Five ducks. Only four batters reached double figures. By the afternoon New Zealand A had put on 132 without losing a wicket.

I watched all of this live from Melbourne. My editor in Delhi slept through it — New Zealand's first session begins at three in the morning Indian time, and India A's entire innings finished inside a window when most subcontinental cricket readers were in the sleep before their alarms. When the first message landed in my inbox at six, it was from a reader in Ghaziabad: Sir, all we saw was 113. What was the pitch like?

I started typing a reply and deleted it. Because the honest answer was that I knew exactly as much about the pitch as he did — and the thing neither of us knew was the most important part of the story.

The real news from this innings is not the pitch. It is the strike rate that froze at 7.7, and the one datum the match report never carried.

The pitch gave its own evidence

The cheap way to read this match is to say the pitch was green, the ball moved, and Indian batters were always going to get stuck. That story sells and it contains a truth. The ball seamed and swung early, and the strongest evidence isn't the score but the mode of dismissal. Four of the top five fell between keeper and slip. That is not a spin pattern, not a bounce pattern — it is the signature of lateral movement. When the ball seams, the blade takes the edge, and when four of five take the edge, the story is about timing rather than technique.

But on the same surface, in the afternoon, New Zealand A's openers put on 132 without loss. That single number removes India A's innings from the category we call an unplayable surface. The pitch delivered its own testimony, and what it said was not that it belonged to the bowlers. It said it was a morning guest and an afternoon host.

This is the oldest arrangement in New Zealand cricket, the one every subcontinental batter knows and almost no tour report properly records: the first hour's green is not a permanent enemy, it is a time limit. The side that survives that window finds a workable batting surface on the other side. India A were bowled out inside the window. New Zealand A crossed it with two openers in a hurry and are 135 for 3, seven wickets in hand.

Put the two facts side by side — 113 in 39.3 overs, and 132 without loss — and the picture is not a bad pitch. It is bad timing. India A's innings was a session's tax, not a match's defeat. It was an extremely expensive tax, because in red-ball cricket the first-innings score sets the terms of everything that follows.

What this match actually is

This needs saying clearly, because it is where most of the misreading starts. This was not a Test. It was the opening red-ball fixture of India A's New Zealand tour — an unofficial Test, a first-class match played with Test-format logic.

Look at the squad. KL Rahul. Yashasvi Jaiswal. Devdutt Padikkal. Sai Sudharsan. Washington Sundar. Dhruv Jurel, captaining. Mukesh Kumar, Akash Deep, Anshul Kamboj, Nabi with the ball. Simon Keene on the other side.

That list tells you what the fixture was for. This is not really an A-team match. It is the senior team's rehearsal room. When your senior side is about to play in a country and its opener and its wicketkeeper-captain are already there in an A shirt, the match is being played for conditions, not for results.

Which is why 113 is not just a score. It is the first data point of an experience Indian cricket buys in New Zealand every few years and pays for every time.

Open the ledger. India have played 25 Tests in New Zealand: five wins, ten losses, ten draws. A twenty per cent win rate. India's last away Test win in New Zealand came in 2026, the same year as their last series win there. Since 2026, India have won one Test in New Zealand. One. On the 2026 tour, none of India's four innings passed 250.

I remember watching that 2026 tour from Melbourne, checking every morning whether India would get near 200. That wasn't stat-appetite. It was a forecast that went four for four.

The beat arrives before the teams do. When the news came through that India A had been bowled out for 113 on day one, I did not need an analyst to tell me what the surface would be like. I needed to know how the top order had got out.

The strike-rate ledger

This is the table I wrote into my notebook at nine in the morning, and it changed the shape of my entire report.

• KL Rahul — 0
• Sai Sudharsan — 0
• Washington Sundar — 0
• Dhruv Jurel — 1 off 13, strike rate 7.7
• Yashasvi Jaiswal — 17 off 45, strike rate 37.8
• Devdutt Padikkal — 32 off 77, strike rate 41.6
• Yash Rathod — 44 not out off 49, strike rate 89.8
• Anshul Kamboj — 10

Five ducks, four double-figure scores, a team run rate of 2.86.

The story is in the last column. Padikkal made 32 off 77 and was out. Jaiswal made 17 off 45. Jurel made one off 13.

Jurel's 7.7 strike rate was not an accident. It is the single most revealing technical fact of the innings.

One run off 13 balls means he spent the whole time trying to understand the ball rather than play it. A captain, standing at 113 in his side's first innings, making one off 13, tells you there was no intent. And when the captain has no intent, nobody in the dressing room has any either.

Cricket usually measures scoring and survival on the same scale. In red-ball cricket that scale normally works: get set, then expand. On a New Zealand green top the scale inverts. Getting set becomes a state that no amount of aggression can reach. Being set there means you have accepted the ball's diminishing threat once more, ball after ball.

That is why Padikkal's 32, which looks like the most solid innings on the card, was actually the most defensive. Thirty-two off 77 is not preparation to win. It is preparation not to drown.

Then look at Yash Rathod. 44 not out off 49, a strike rate of 89.8. Three fours and three sixes — thirty of his forty-four runs in boundaries, about 68 per cent. That number says he stopped waiting for the ball on which there was a safe option.

I didn't see any of that innings live. I saw the 44 not out on the scorecard and then worked through the ball count. Building a star out of one innings is bad practice and it is the disease of my trade — but it has to be said that in 24 hours the thing that caught my eye was that the same squad flowing at 2.86 contained one man flowing at 89.8.

This is not a technical observation. It is a collective one. When one dressing room produces two intentions that far apart, the difference was not ability. It means nobody issued a plan and one man wrote his own.

Keene's 5 for 24: front end and back end

If the batting story was strike rate, the bowling story was Simon Keene — 5 for 24.

The spell needs splitting. First: Sudharsan and Jurel, the top and middle. Second: Nabi, Akash Deep and Mukesh Kumar, the tail.

The first block came with the new ball, when the surface offered the most. The second came later.

Spells like that tell you that a bowler's identity is not the five wickets but the shape of the five wickets. What Keene did was the intersection of a new ball, a tired set of lower-order batters, and conditions built for seam — morning air, a live layer of grass, and a batting order that had not arrived with a script for any of it.

The inverse inference matters just as much. A seam bowler taking front-end and tail wickets on a green top is, by definition, a condition-dependent threat. If he were equally lethal on flat decks he would already be in New Zealand's senior set-up. All that 5 for 24 can support right now is this: the conditions made Keene large, and Keene took full payment. Which of those two facts is the bigger one will be answered on a flat pitch in May.

Rathod's 44 not out: plan or improvisation

Was 89.8 a coaching plan or a cricketer's emergency?

The answer is not in the numbers. It is in what the other four batters were doing. If the team plan had been to take the game to the moving ball, Jurel would not have made one off 13. He would have hit or been out.

There is no great moral conclusion here. It is an audit. A team's thinking is visible when wickets fall and five batters react the same way — all attacking or all blocking. The dangerous state is when three men keep leaving, one keeps swinging, and one can do neither.

Later India A did the thing they should have done in the first innings. They took three wickets in seven deliveries. They did not stop New Zealand A reaching 135 for 3, but they made a dent.

Pause here and stay honest. Three wickets in seven balls is not proof that Indian seamers have solved New Zealand. It was either the benefit of a new-ball situation or the benefit of a tired end of day. Those are different events and the available information cannot separate them.

The datum that wasn't in the report

Now the professional flaw that nags at me daily and resurfaced here.

I read the full match report and could not find who won the toss.

That looks small. It is not. It is the datum on which this entire story turns.

If New Zealand A won the toss and sent India in, then 113 is evidence about Indian technique. If India A won the toss and chose to bat, the story becomes a decision — a management call that pushed the weakest link of Indian batting into the hardest ninety minutes of the day.

Absence has a beat too; you hear it in the gaps. Here the gap is in the toss reporting, and it has changed the direction of the whole assessment. I am not alleging an error. I am saying that the absence of that number is itself part of the story, because that absence is what allowed a reader to conclude that the pitch lost this match.

Three misreadings from outside

The pitch was unplayable

It wasn't. 132 without loss kills the claim. The surface governed the first session and was workable after that. Teams that learn to defer the surface stay in the match. Teams that settle into it end there.

The A-team result is a senior-team prophecy

As wrong as the first, and just as tempting. A-team and senior-side datasets stay separate in my book. But dismissing the read-across entirely is lazy too.

What transfers to the senior level from this match is not the score. What transfers is a habit — the habit of killing your own run rate while trying to leave the ball.

When the senior side's first innings arrives on this tour, I will watch two things, not the score: the top five's strike rate, and the mode of dismissal. Are the wickets falling between keeper and slip again? If that pattern repeats over two Tests, it is structure rather than a bad day.

Rathod's 44 not out is the good news

I disagree, and this is the most sideways opinion in this piece.

What Rathod did was good cricket. Treating it as the story is reading it in an unhelpful register. If a side is bowled out for 113 and one batter plays at 89.8 and stays not out, the least romantic reading is: the team had no plan and one man improvised to save himself.

The better news is elsewhere — the three wickets in seven balls. Indian seamers can take wickets in these conditions. That is a small, solid, useful fact. A 44 not out can be a beautiful, large, useless fact if we get friendly with it.

A defeat that arrives like weather

In 2026 I watched four Indian innings in New Zealand and none crossed 250. At the time I thought it was a bad series. My meter was wrong. It wasn't a bad series. It was a section of a long graph we keep ignoring, because at home we measure batting quality on turning tracks and call a green pitch abroad bad luck.

India's batting problem in New Zealand is adaptation, not talent — and adaptation is not solved in three days of training. It is solved by sessions of habit.

Which is why the ominous framing sits slightly wrong with me. Ominous is what departs from plan. 113 in New Zealand is not a departure. A 350 in New Zealand would have been the ominous thing.

What to watch in the next few days

The story was not the score; it was the pulse around it. And the pulse has not stopped at 113 — it will be settled by this tour's first senior innings.

Four things are in my notebook, tracked the way I tracked the Impact Player rule through a whole season.

One — the senior top order's first-innings strike rate. If it goes under 40 again with three or four wickets to the slips, that is architecture, not accident.

Two — Rathod's next red-ball match. Calling a player class after one innings is unfair to him and to readers. If the same attacking intent shows across the next two innings, the conversation changes.

Three — seam selection for the senior Tests. India A's quicks took three wickets in seven balls. If selectors read that signal, the first Test attack will lean seam-heavy, and that would be the right direction.

Four — the toss. Not because it identifies the pitch, but because it reveals how the management is reading New Zealand. A side that wins the toss on a green top and bats believes in its batters. A side that bowls is being honest about its conditions.

I follow the people who make the stadium breathe — the keeper, the slip fielder, the curator on the morning. All three told the truth in this match. We just didn't choose to listen properly.

113 is a question, not an answer. The answer arrives when the senior side bats on the same kind of green top and we find out whether 7.7 was an A-team mistake or an Indian red-ball habit.