Two Balls, Two Wickets, and the 117-Run Silence That Speaks Past the Scorecard

It was the third hour of the night in Delhi. The tea on my desk had gone cold — a thin film had set along the rim of the cup, like dew on an old pitch at first light. The laptop screen held a scorecard and I was staring at it the way a man in a desert stares at a map of water. That is the truth about A-team cricket: there is no crowd to tell you that something has happened. You have to find it yourself.

Then the line came through. Auqib Nabi — two balls, two wickets. Jayden Lennox and Tim Robinson, off successive deliveries. I read that moment twice, three times, and what stung most was not the wickets. It was that there was nobody in the room to jump up with. Two wickets in two balls — the moment that stops twenty thousand breaths in a full ground — had been reduced here to a green dot on a refreshed web page.

The roar leaves first; the quiet stays behind to explain it. I learned that at The Oval in 2026, when Pakistan beat India by 180 runs and I was one of two women in a cramped press box. Since that night I have had one method: write the sound first, then the numbers. Tonight there was no sound. So I had to timestamp the silence instead — New Zealand A 228/7 in 69.2 overs, leading by 117. And inside that silence sat a second story the source never printed but the arithmetic cracked open.

'Unofficial Test' is itself a fact

Start with the thing we call an unofficial Test and the reader usually skips. The Times of India's live report itself carries the framing: India A vs New Zealand A, first unofficial Test, Day 2. The match holds first-class status. It does not hold Test status. That distinction is concrete and I keep repeating it because plenty of people — educated people, loud people — do not know it: not one number from this match will enter the ICC World Test Championship, an official Test record, or any ranking table.

That matters, because this is where cricket's actual factory floor is. India A and New Zealand A are the bench-building proxies of two boards. Nobody lifts a trophy here. What is decided is whose name moves up a list that is never announced after the meeting.

I have an old habit — I treat an A tour as cricket's transfer window. Every spell is a trial, every scorecard a first draft of a negotiation. And exactly as in football's July, where rumour drowns the real story, the noise of 'who is the next star' hides what actually happened in the middle. My job tonight is to take the noise out.

The 117-run gap, and the innings nobody wrote down

The source says it plainly: New Zealand A reached 228/7 in 69.2 overs and extended their lead over India A to 117. I read those two sentences three times and then did the thing that reading a scorecard actually requires. I subtracted.

228 minus 117 leaves 111.

India A's first innings was around 111 — that is not information, it is arithmetic. The report never prints it. The reader has to derive it, and I think it is the single most important fact in this story. Because a 228/7 lead is one thing; the implication that the other side was bowled out for 111 is something else entirely.

Now notice what kind of 111 it is. 228 in 69.2 overs is 3.29 an over. This was no fast outfield, no T20 pageant. This was the cricket where a batter has to bargain for every run and a bowler has to repeat one question every over — will you make the mistake of trying something? Patience tested from both ends.

The report gives no toss, no venue, no weather. That is a real gap and I will not hide it. If India A made 111, it follows that India A batted first — the very existence of a lead proves it. But what the pitch was doing, I cannot claim to know. What I can say is that a match running under three and a third an over had something in it for the bowlers. Seam movement, uneven bounce, or a slow surface gripping. One of those. This much is certain: the pitch was not laying out a bed for batters, and the two innings are two separate witnesses to that one fact.

Slow scoring is a story, not a statistic

I have to stop here, because I know what the data-loving friends will do. They will look at Rhys Mariu's 76 off 137 and Curtis Heaphy's 44 off 134, compute strike rates — roughly 55 and roughly 33 — and post that this was slow batting. This is where I repeat my oldest piece of advice, the one I give the young reporters who take my calls: judging red-ball strike rates on a white-ball scale is the most common and most costly mistake in cricket writing.

A strike rate of 33 in a Test is not a weakness. Sometimes it is the bravest thing a batter can do — stay alive while the ball keeps leaving the seam and taking an extra inch to reach the keeper's gloves. Heaphy's 44 off 134 does not mean he was slow. It means he survived 134 balls, and every ball a batter wins is one more run of opportunity for the man at the other end and one more over of fatigue for the bowler.

And look — when two different batters, a captain and a lower-order man, are scoring at the same slow tempo, the story is not theirs. The story belongs to the man bowling at the other end. When both ends are batting at the same pace, you are reading a bowling story and mistaking it for a batting story.

Mariu's 137 balls — not a hundred, but the most valuable innings

Rhys Mariu. The name empties an Indian fan's head, and I am not surprised. He is not an auction face. No advertisement runs on him. He is the sort of cricketer New Zealand builds very quietly and the world meets only once he is finished.

Tonight he made 76 off 137 balls. As captain. The biggest thing in that innings was not the runs — it was the condition in which he made them. The source says New Zealand A recovered through the middle order. That means early wickets fell. When early wickets fall and the captain walks in, he has two roads: attack and change the mood, or become the wall.

Mariu chose the wall. 137 balls. In an unofficial Test, in front of an unfamiliar audience, on a day when the ball was doing something. That is the work the scorecard never reports, because the scorecard writes 76 and does not write how many other runs those 76 prepared the ground for. Dean Foxcroft is 33 not out, Mitchell Hay made 24 — those numbers are incomplete without Mariu's 137 balls.

Here my oldest enemy returns: the cult of the hundred. In fifty-over cricket we have trained ourselves to score an innings inside the batter's head rather than the team's. The crowd sits waiting for the hundred. Whether Mariu fell on 76 or stayed not out matters less than the fact that he carried his side to a 117-run lead. An innings that gives the team a lead is worth more than any innings that gives the batter a milestone. The 2026 Ahmedabad final taught me this — we were reading the score there too, not the match situation.

Kamboj's 3/32 — the figure that rises above the innings

Now the side the Indian reader will look at. Anshul Kamboj — three wickets for 32.

Put the figure in its frame. The whole innings is running at 228 in 69.2 overs, a little over three an over. In an innings where nobody is moving easily, three wickets for 32 is not merely a good day — it is the most economical and most consequential spell of the innings, and set against the rest of the day's bowling it is clear that Kamboj was taking wickets with his own ball, not someone else's.

I have watched Kamboj for a while — from the empty steps of domestic cricket where there is no camera, only tea and two men who know the game. His quality is not pace. It is repetition. He lands the same length over after over without tiring of it. In red-ball cricket that length is the biggest weapon there is, because the batter keeps telling himself the next ball will be the same one and he can play it — and then one ball climbs an inch higher, or leaves an inch later, and that one ball turns the innings.

The report does not tell me which wickets he took, on which deliveries, at which stage. So I will not claim he bent the innings at a particular turn. What I can say: three for 32 means he settled his account fully, and among four seamers he was the only one whose runs-per-wicket did not even approach double figures.

Akash Deep took one, Mukesh Choudhary one. That distribution says something by itself: India A's pace attack was functioning collectively rather than resting on one shoulder. Five of the wickets are shared across four bowlers with two still to fall. That is the picture that lets a coach sleep — the opposing batter gets a new question at every end and never the leisure to build a plan against one man.

Nabi's two balls — and why momentum is never an event

Here is the moment that kept me awake. Auqib Nabi. Jayden Lennox and Tim Robinson, off consecutive deliveries.

First understand the man who was dismissed. Lennox — the night-watchman. That word always gives me the feeling of a railway platform late at night. The night-watchman is the soldier sent out for two or three overs of sentry duty. His job is not to make runs; it is to be alive by morning. He is there to absorb the sacrifice, so that if somebody must fall, it will not be the main man.

And Nabi hit exactly that soldier — then took Robinson off the next ball. That two-ball sequence is the most dangerous moment an innings can hold, because it is not a wicket, it is a delivered message: the batter yet to walk out arrives already beaten. Every batter knows the hat-trick ball is coming for him. The air in the dressing room changes inside that one over.

I once wrote that every final leaves a fingerprint on the pitch, not the trophy. Tonight that came back slightly altered. This two-ball burst was not momentum; it was a door swinging open, and the question was whether New Zealand A could walk through it. The answer came from Foxcroft and Hay — 33 not out and 24. That is what a middle order means, and it is the quietest strength New Zealand cricket has always had.

This is also where I must be careful about Nabi. The source gives two wickets, off successive balls. It does not give his figures, his overs, the stage of the innings. I will not print a poster for a new fast bowler on that. A spell is an anecdote; a series is an argument. I want the argument, not the anecdote.

Three wickets left — the real nerve of the match

228/7. Three wickets in hand. A lead of 117.

This is where most reporting stops. The scorecard says New Zealand A are strong, and the copy ends there. But anyone who has actually watched the game knows this is the most leveraged position on the board.

Three wickets means three men who have so far done nothing and who now have work on both sides of the ledger. If they add eighty more, the lead passes 200 and India A face a fourth-innings sentence. If they fall inside two overs, the lead freezes at 117 and a side that was bowled out for 111 suddenly sees a route.

The big fact is not how far ahead New Zealand A are; it is how slowly they got there. Seven wickets in 69.2 overs is slow, patient, ground-out cricket. New Zealand A have taken the match in hand, but they have not closed their fist around it. And a match not closed in the fist is a match where one innings can arrive and turn everything over.

The tail has always been cricket's least-shot character. Television never cuts to it, newspapers finish it in a paragraph, commentary remembers it only once three wickets have already gone. In truth the tail is where red-ball matches are settled. My largest uncertainty tonight is exactly this, and it is not comforting that I cannot resolve it.

India A's ~111 — the new-ball lesson

Now the innings nobody wrote, which teaches the most. India A, approximately 111.

Again: this is not in the report. It is my subtraction — 228 minus 117. I repeat it because I do not want a reader later asking where it came from. The source did not state India A's total; it stated the lead and left the arithmetic to the reader. That is a reporting weakness and I record it before moving on.

Why 111?

Being bowled out for 111 in the first innings of an unofficial Test paints one clear picture — a top order collapsing against the new ball. It is A-team cricket's most common and least-discussed illness. At home you can be the batter who makes beautiful runs in the middle order, where the ball is old, the seam is tired and the spinner is still finding his line. Then you go away and meet a fresh, quick, climbing ball that moves in the air, and your feet are not where they needed to be.

I have seen this from the half-empty stand at Chepauk, where the Ranji knockout ball at nine in the morning moves as if someone has pulled a sheet across the pitch. And there you get the sight television never shows — a good batter who made four hundreds last season walks back off the third ball, and nobody blames him. Everyone in that ground is going through the same difficulty that morning.

This is why I keep one eye on weather and session time whenever I read an A-tour scorecard. Tonight I have no weather. I have one calculation and one inference. When an entire innings stops near a hundred while the bowling side makes 228 in 69 overs, the most rational reading is that the first-morning ball asked the batters a question they had no answer for.

And this is where my real concern begins, well beyond this score.

The bench-strength argument rests on a myth

I have watched something over the last few years that disturbs me. In Indian cricket, 'bench strength' has become a phrase we repeat without thinking. Each time a senior player rests and a newcomer plays well, we say — look how deep we are.

Bench strength is not measured by one innings. It is measured by who stands when the situation is bad, when the pitch is helping, when the lead belongs to the other side. And tonight, on that test, New Zealand A stood and India A fell. That is not a catastrophe; it is a fact, and I must write it as calmly as I write Kamboj's three wickets.

An A-team scorecard is no proof of any nation's senior strength; it only tells you who had better answers that week. This week, the better answers belonged to New Zealand A — a captain's 137 balls, a middle-order recovery, and a bowling group that held India A to 111.

The story nobody filed: New Zealand A's patience

One thing astonishes me. New Zealand cricket has played the smartest cricket in the world for a decade — few resources, little noise, plenty of results. And still, when they win we call it an upset, and when they lose we call it expected. The bias sits so deep in our coverage that we never credit the work.

That happened tonight. New Zealand A took a 117-run lead on Day 2 of an unofficial Test, and the biggest question in Indian media is when Anshul Kamboj will play for the senior side. That question is not wrong. It is incomplete, and incomplete questions produce false answers.

A side that makes 228 for seven wickets in 69 overs is not waiting for someone to accelerate — it is deliberately going slow. And going slow is the hardest job in red-ball batting, because you have to suppress the instinct to hit on every ball. Mariu faced 137 deliveries. Nobody will count on how many of them his hands wanted to go through with the shot. That is where the value of the innings actually lives.

The honest gaps

I do not know where this match is being played. The source does not say. I do not know who won the toss, what the weather was, what the light was, what the outfield was. I do not know which batters Kamboj dismissed, in which overs, off what shots.

That absence must be visible in what I write. I will not cover it with a beautiful sentence, because that is my most reliable failure mode — the fastest line I write is the least checked. I have held one rule since 2026: no poetic line survives a contested fact. So tonight I say only what can be said.

On the pitch I can say this much: a run rate of 3.29 and an innings near 111 together indicate that bowlers were troubling batters. Whether this is a New Zealand surface or an Indian one, I will not guess. Whether it was seam or spin, I will not guess. What I will say is that in this match the ball was ahead of the bat, and that applies equally to both sides — New Zealand A's 228 is slow too.

The biggest risk: making a star out of one innings

Here is the part I write in every piece and the part people listen to least.

One innings does not settle a player's future. Not a good one, not a bad one. And the risk is highest in A-team cricket, because every good performance there drops into a machine that instantly turns it into a 'next star'.

Anshul Kamboj took three for 32. That is a very good day. I will not call it more. Auqib Nabi took two wickets off successive balls. That is a superb moment. I will not call it more. I do not have their ages, career averages, domestic records, fitness status. Without those, any conclusion carries no weight.

A fast bowler's greatest enemy is not the opposing batter; it is a brilliant four-over spell followed by a winter injury. Four seamers sharing a 69-over innings — the report does not say how many overs each bowled — is the central workload question of red-ball cricket, and I have no fitness data. I log it as a monitoring item and move on.

A contrarian question: is India A's 111 actually the valuable part?

Now the section that may cost me readers.

I will not say being bowled out for 111 is good. That would be absurd. I will say that the most valuable thing to happen to India A in this match may be that 111, if it is read correctly.

The entire purpose of an A tour is not to discover who can play well — domestic scorecards already tell you that. The purpose is to discover who can stand in conditions that never occur at home: a foreign pitch, an unfamiliar ball, a hard wind, and the loneliness that only an away player understands.

If India A's top order fell for 111 against the new ball, this match did its job — it exposed a wound that eight hundreds in a domestic season had been covering. That is not good news. It is useful news. And if the selectors go home reading only Kamboj's 3/32, half the lesson goes in the bin.

This connects to an old worry I call the Ranji inheritance. Since 2026 we have built a system in which franchise scouting does the work zonal selectors once did. Franchise scouting is looking for the cricketer who turns a match in three overs. It is not looking for the cricketer who takes a side from 111 to 280 across five hours. As long as the A tour lives, that second cricketer lives too.

The empty stand at Chepauk

I remember something.

Some years ago, on the second day of a Ranji knockout in Chennai, I sat alone in a stand that held eleven people — four groundstaff, two scorers, one cameraman, and me. That day a spell was bowled that nobody saw. A fast bowler sent down eight straight overs for three wickets and then walked back to his mark wiping sweat from his collar. No applause. No name called out. And I felt I was witnessing something enormous that wanted no witness.

I wrote in my notebook that day: Dubai taught me that empty seats can echo louder than full stands. Tonight, in my own room in Delhi, the feeling returns. Auqib Nabi took two wickets in two balls and I am reading it off a refreshed page.

This is cricket's oldest injustice — the work happens where nobody is looking, and the noise happens where nothing happened.

Four bowlers, five wickets, one team's character

One technical point before I close, because it says more about this match than anything else.

Kamboj three, Nabi two, Akash Deep one, Mukesh Choudhary one. Five of seven wickets across four seamers. The report does not mention spin. That does not mean no spinner bowled — it means the spinner's role was small enough in this report to go unmentioned.

When five of seven wickets fall to seam and no spinner finds a place in the figures, you learn a great deal about the nature of the surface — even if you are not told where the surface is.

It also says something about the depth of Indian fast bowling. Four names, four different methods, all taking wickets. This is what I call collective pace: not a man, a structure. And in red-ball cricket a structure is always bigger than a man.

With that comes a warning. Spreading four seamers across 69 overs is fine until one breaks, and then the next match has a hole in it. This report contains not one word on fitness. I record that, and I record that I do not have it.

The captaincy detail the scorecard hides

Rhys Mariu is captain and he made 76. The best thing I have learned about captaincy is that it has two halves — what you do with the bat, and what you make others do. The first half is on the scorecard. The second half usually is not.

When your side has lost early wickets and you come from a country where the noise is low and the patience is high, you have one route: turn your innings into a template the rest can copy. Mariu playing 137 balls was saying, 'I will stay.' And when the captain stays, the man below him stays too. Captaincy's biggest job is making yourself the example eleven others can imitate, and Mariu wrote that example in balls rather than runs.

I dwell on this because Indian coverage measures captaincy in aggression. Move a fielder in, remove slip, and you are bold. Leave him there and you are weak. We do not count patience as captaincy; we count it as passivity. Tonight's entire New Zealand A innings is evidence of a patience we do not count.

Three questions for tomorrow

Let me look forward, and put these down here rather than on social media, so nobody can say later I did not call it.

First: how much does New Zealand A's tail add? They sit at 117. If that swells to 170 or 180, India A's fourth-innings task becomes two hard jobs in sequence. If it stops at 120, the match is open.

Second: how does India A's top order look in the second innings against a fresh ball? If the 111 pattern repeats, the question stops being 'are they talented' and becomes 'do they have a technique for the new ball.' That is the question that makes or breaks a career.

Third: consistency from Kamboj and Nabi. Three wickets in one innings can be a good morning. Repeating it across the series is an argument. I want the argument, not the anecdote.

Last word — what the scorecard will not say

At the end of the day, this scorecard will tell you New Zealand A made 228/7 and led by 117. That is true, and it is the truth that will sit in a record twelve hours from now.

The scorecard will not hold the man wiping sweat in the 69th over. It will not hold the night-watchman dismissed off two balls — and if you have ever gone out as the sentry of the night, you know what a lonely place that is. It will not hold the batter who faced 134 balls for 44, whose 44 built the road for someone else's 76.

The quiet comes first and it is the quiet that explains everything. Tonight, two balls took two wickets, and nobody clapped. Tomorrow, when India A walk out for the second innings, we will learn how large those two balls were. And people like me, who hear the sound before they read the scorecard, will be waiting for that answer — with a fresh live score, with cold tea, and with the knowledge that somewhere far away something is happening that nobody is watching, and that it is the biggest day of somebody's career.

The question is not who wins this match. The question is who will remember it — and why.