113 All Out in 39.3 Overs: India A's Collapse Is Real, the 'Unplayable Pitch' Story Isn't

The sound that came off the fourth ball of the third over was not the sound of a wicket. It was the sound of the outside edge — thin, quick, and immediately behind it the slap of a keeper's gloves. I was in a commentary box in Sydney that morning, scorefeed open, an audio feed from New Zealand in my ears. I have a habit: after every match I log ninety seconds of ambient audio into a sound notebook. That morning it caught only two sounds — the edge, and a bat that was speaking a completely different language.

The scoreboard said 113. The ground said everything else.

Thirty-nine point three overs. Fewer than half a day's play in a format where a day is ninety overs. Five batters returned on zero, KL Rahul and Sai Sudharsan and Washington Sundar among them. Captain Dhruv Jurel faced thirteen balls for one run. And in the middle of all of it was a batter who was hitting sixes — Yash Rathod, 44 not out off 49.

Two opposite sounds inside one innings. When you hear both at once, it means neither the bowling nor the batting has broken. What has broken is the negotiation between them. That is the real story of this innings, and it is far more interesting than 113.

What this match actually was

Fact first, without wrapping. This was the opening fixture of a New Zealand tour — India A against New Zealand A, a first-class match of the kind that gets called an unofficial Test. Red ball, four innings, sessions that matter more than overs. It is not a full international Test, and the difference is not just semantic. Every conclusion you draw about the senior side has to be flagged as extrapolation. I will flag mine.

The names India A put on the field were not an ordinary bench: KL Rahul, Yashasvi Jaiswal, Devdutt Padikkal, Sai Sudharsan, Washington Sundar, Dhruv Jurel captaining, Anshul Kamboj, and a seam group of Mukesh Kumar, Akash Deep and Nabi. On the other side, Simon Keene took 5 for 24 — five wickets for twenty-four runs, an excellent return at any level.

At stumps New Zealand A were 135 for 3, with a 132-run opening stand already banked. In pure count terms India A trail by twenty-two. That count will mislead you, and I will explain why.

Now the part that gets the least space in most reviews. India's Test record in New Zealand is not merely poor; it is a structural anomaly. Five wins in twenty-five Tests — a twenty percent win rate. Ten defeats, ten draws. No away Test win there since 2026, and the last series win also 2026. Since 2026, India have won exactly one Test in New Zealand. I am not writing that number as decoration. It is the key to reading this innings.

And remember the 2026 tour: across four innings, not one passed 250. The last time the collapse was this large, nobody called it a bad day. They called it a pattern. The same word is correct now.

39.3 overs: watch the wicket interval, not the run rate

113 runs, 39.3 overs, ten wickets. Most people will compute the run rate first: 113 over 39.3, roughly 2.86 an over. That figure sounds like batters digging in, playing slowly, surviving. That is exactly the misreading that corrupts the whole analysis.

A run rate of 2.86 is not, by itself, a disaster. Red-ball teams choose that tempo deliberately. The disaster is that ten wickets fell at that tempo — 237 balls for ten wickets, one wicket every 23.7 deliveries. That is a wicket every four overs. Blocking and falling, at the same time.

Here is a basic thing I learned by sitting in grounds rather than reading scorecards. When a side collapses, it usually takes one of two shapes. The first is the aggressive collapse: run rate above six, wickets tumbling quickly, because batters chose to counter-punch. The second is the frozen collapse: run rate around one and a half to two, batters shrinking to survive until one ball ends them.

India A's innings belongs to the second category, in its worse form: no runs, no survival, and wickets falling continuously. Ten wickets in 39.3 overs means not one partnership lasted long enough to force a bowler to change his line. The bowler did what he wanted, throughout.

The strike-rate map: batters who froze

This is the part I consider most revealing, and it sits in four numbers.

Dhruv Jurel: 13 balls, 1 run. Strike rate 7.7. Yashasvi Jaiswal: 45 balls, 17 runs. Strike rate 37.8. Devdutt Padikkal: 77 balls, 32 runs. Strike rate 41.6. Yash Rathod: 49 balls, 44 not out. Strike rate 89.8.

Put them side by side. Three batters spent 135 balls between them for fifty runs. Rathod made forty-four off forty-nine. The gap is not only skill. It is intent.

Defence never works on a green top. The only way to survive a green top is to score. Because on a surface where the ball is seaming, a bowler changes his length only when he believes you are hitting him. Defend a whole over and he repeats the same length, the same line, and on the eighth or ninth ball the edge arrives. Jurel's 7.7 was not caution. It was indecision. Jaiswal's 37.8 and Padikkal's 41.6 say the same thing — a batter operating at forty percent pace applies no pressure at all.

Rathod did the opposite. Forty-four off forty-nine, including three fours and three sixes — thirty of his forty-four runs from boundaries, roughly sixty-eight percent. That is not a rescue innings. That is a counter-attack. And note when it happened: while wickets fell continuously at the other end. He tried, alone, to break the bowler's rhythm, and partly succeeded.

But I want to brake here, because this is where the easiest trap sits. One 44 not out does not settle anyone's future. It is a signal of form, not of class. From ten years of watching, I can tell you that A-tours produce these counter-attacking innings regularly, and very few of them convert at international level. Rathod's next two or three red-ball matches will answer that question. This match will not.

Keene's 5 for 24 and the lie of the pitch

Simon Keene's five wickets split into two halves, and the split is itself a story. The top order gave him Sudharsan and Jurel; the bottom gave him Nabi, Akash Deep and Mukesh Kumar. He took wickets with the new ball and with the old one. That is the portrait of a bowler whose edge depends on conditions — dangerous when there is moisture and movement, unknown on a flat deck. That matters, because anyone warning about Keene in the Tests to come also has to say that his threat fluctuates with the weather.

The mode of dismissal confirms the ball was moving laterally in the first session. Most of the top five were caught between keeper and slips — the plainest evidence of seam movement, the pitch's own testimony. When you go for a cover drive and the ball takes the edge to the keeper, whether the fault is technique or surface is a question answered by sound, not by statistics.

Now the fact that dismantles the unplayable-pitch argument entirely. New Zealand A's openers put on 132 for the first wicket. If the surface had been unplayable, that stand does not exist. The implication is clean: the pitch offered help early, then dried and settled as the day wore on. A large part of India A's failure is the cost of first-session timing — they batted precisely in the window when the ball was doing the most.

And look at the other end of the same argument. India A's seamers took three wickets in seven deliveries late in the day. Small event, large point: Indian fast bowlers can be lethal in these conditions too. India A's bowling was not outclassed. Their batting was.

The twenty-two-run gap is arithmetic, not reality

135 for 3 at stumps. Twenty-two ahead of India A's 113. In newspaper maths that reads as a close contest. The ground reads differently.

Seven wickets in hand. A pitch drying out, meaning batting is getting easier. When you have seven wickets and improving conditions, a twenty-two-run lead is an opening figure, not a threat. The real question is how large New Zealand A's lead becomes — and if it crosses 150, India A will bat again on the same green surface that has already broken them twice. Chasing in the fourth innings of a red-ball game is the hardest job in the format, and it will fall to a top order that has just been shredded inside 39.3 overs.

113 is a very low first-innings total. I say that from the sessions, not from the averages. A first-innings score in red-ball cricket exists to set the terms of the match. 113 never sets terms; it only postpones. And a team postponing does not win matches. It delays defeats.

The question nobody asked: who won the toss?

Now the weakest joint in this whole report — and it is not a reporter's error so much as the limit of what was recorded. Nowhere in the account is it stated who won the toss or what they chose.

That small piece of information changes the shape of the story. If New Zealand A won the toss and bowled, the green top was their strategy and India A batted under duress — in which case putting the ominous framing on India A's account is unfair. If India A won the toss and chose to bat, it was a decision-making error and the story is entirely different. Two different situations, two different questions, two different answers. And we are writing verdicts without knowing which one we are in.

This is where I have a complaint against my own trade. We chase the noise and drop a fact that was available for free. For me it belongs to an old habit I call verdict-first: the result first, the scene later. My method runs the other way — sound first, scene second, argument third. Here the sound arrived, the scene arrived, and the argument is incomplete for want of one fact.

The second illusion: an A-team score, a senior-team fate

The bigger illusion is that we read an A-team innings as a prophecy about the senior side. I do not dismiss it outright — India's batting fragility in New Zealand conditions is four decades old and it applies to the senior team too. But these are two squads, two intentions, two schedules.

There is a detail few notice. The presence of players like KL Rahul and Yashasvi Jaiswal in an A-side tells you this fixture is not purely a development platform. It is also a workload-management and red-ball rhythm window for senior players. When a senior batter turns up in that mode, a duck is often a question of priority rather than form. We file it as a form crisis and move on.

This brings back an old morning. In January 2026 I sat in a near-empty Sydney ground — twenty-five percent capacity, roughly nine thousand people. That day Hanuma Vihari batted 161 balls on a torn hamstring for 23 not out, and R Ashwin survived 128 balls. Nobody cheered. Nobody left. What I learned was that a match is held together by endurance rather than noise.

The other half of that lesson is this: folding for 113 is a failure of endurance, not of talent. If five batters return on zero and three others spend 135 balls for fifty runs, the problem is not that they cannot bat. The problem is that they did not know what the surface required. That is coaching and preparation. Not talent.

The number that justifies the word ominous — and the one that exposes it

I want to measure this innings from both ends, because I can see the evidence on both sides.

On one side: five wins in twenty-five Tests, no away win since 2026, one win since 2026, and a 2026 tour where four innings never reached 250. Those four facts together say 113 is not an accident. It is the base rate. This is what tends to happen.

On the other side: New Zealand A's openers put on 132, and India A's seamers took three wickets in seven balls. Those two facts together say the pitch was not unplayable and the bowling was not weak. Which means this is not a hopeless-tour story. It is the loss of one session, and the price was enormous.

Both truths can stand at once: India's record in New Zealand is bad, and this innings is worse than that record. The first truth describes structure. The second describes intensity. If forced to choose one, I would choose intensity — because the structure is familiar and the intensity is new. Five ducks is a lot, even inside a known pattern.

The moment nobody recorded

I go back to the sound notebook, because that is where this began.

The strangest thing in my headphones that morning was not the wickets. It was the silence between them. There was a long gap between the fifth and sixth wickets in which nothing happened. No boundary, no dramatic swing, no appeal that lasted. Only defence, defence, defence. Thirty-two nights of radio taught me that silence is also a crowd — and this crowd was India A's own. A team present on the field and absent from the contest.

That is why I refuse to read this innings off the number 113. I read it off the interval in which batters watched the ball, left it, and did nothing. There is one law of playing on green: the ball will hit you if you do not try to hit it. Rathod understood. The rest did not.

What to watch next

I treat this as a signal, not a verdict. Three things will tell me whether the signal holds when the senior Tests begin.

First, the top order's first-innings strike rate. If three of the top five bat below forty, the structure is intact and 113 was no accident. If one batter counter-attacks the way Rathod did, the script changes.

Second, the proportion of dismissals caught behind. Three or more of the top five taken between keeper and slips means the ball is still moving and India still have no answer.

Third, whether India can bat 120 overs. Winning is a later question. With one win since 2026 on the ledger, asking whether India will win is the wrong question. Whether this team can spend a day and a half at the crease is the right one.

And for Rathod a separate clock is running. His next two or three red-ball innings will tell us whether 44 not out was form or a beginning. I will not put him on any list yet. I will just keep listening to his bat.

The next time the feed opens from New Zealand, do not listen for the wicket. Listen for the bat. If the bat is talking in the first hour, the pitch is not at fault. And if only the edge keeps talking, then the problem is not the surface. It is the preparation — and that preparation should have been finished before this tour began.