Nine Wickets for Two Bowlers, Yet 78 Runs Behind — India A's Real Question Is the Batting

I went looking for the scorecard and found the empty space first.

Then I found a headline — the second unofficial Test of the India A v New Zealand A series. Five wickets for Mukesh Kumar. Four for Mohammed Siraj. And the one clause that turns the whole thing over: New Zealand A took a 78-run lead.

What followed was a repetition of the headline. No ground. No date. No toss. No overs bowled, no runs conceded, no phase in which those nine wickets fell. Thirty-two years of reading and writing match reports has taught me that A-tour cricket always arrives like this — half a door open, half a sound escaping. But the feeling is the same every time: you are standing at the stadium gate trying to hear what is happening inside.

So the entire foundation of this piece rests on four facts: the second unofficial Test of the series, Mukesh's five, Siraj's four, and New Zealand A's 78-run lead. Inventing what is missing is the oldest habit in this trade. I am not going to practise it today.

The phrase "unofficial Test" decides the direction of everything that follows. This is a first-class fixture — two innings, several days, red ball, real work. It is not Test cricket. It is not played under the ICC's Test playing conditions; match duration, DRS availability, ball specification and umpire appointments are bilaterally agreed. Which means one thing: the five-for here will never enter a bowler's Test record. It is a first-class five-for, and that is all.

The distinction is not subtle. It is the first thing that dissolves in downstream reporting. In any selection-pressure season, "five-for in an unofficial Test" becomes "Test form" within a fortnight, and then the argument proceeds on a foundation that does not exist.

The purpose of A-team cricket should also be remembered. It is not an alternative to the senior side; it is its supply line. What is settled here is who plays the next red-ball innings — not how strong the senior team is. These numbers are recruitment reports, not rankings.

And in this recruitment report, the loudest information is not in the wicket column. It is that Mohammed Siraj is playing. In ordinary team management, a senior fast bowler appearing in an A fixture signals one of three things: a return from a rest or injury cycle, being outside the current senior XI and needing match volume, or preparation for an imminent red-ball assignment. The report says none of this. But the fact of the deployment is the signal.

On the other side sits New Zealand A's batting — a generation raised on seam movement. There is perhaps no batting unit in the world less easily destabilised by seam alone. A 78-run lead is consistent with that reading, though it does not prove it.

Now the count. Nine of ten dismissals went to two right-arm seamers — five and four. Which leaves at most one wicket for another bowler, or a run-out. In my experience this pattern forms in only two conditions: either the pitch and the new ball were so potent that everything else looked useless, or the captain was cycling two bowlers because the spin option was neither threatening nor trusted. The available facts cannot choose between them. Both remain open, and they mean different things.

The word "but" in the headline is the entire analytical payload. When two bowlers take nine wickets and the side still trails by 78, the match was lost or loosened in a phase neither of them controlled. The likeliest location is India A's first-innings batting, or a lower-order partnership the fifth and sixth bowlers could not break. That is inference, not proof.

One more thing follows. Nine wickets shared by two bowlers means, in practice, a two-man attack. In modern first-class cricket that is rare enough that it should be read as a limit on bowling depth rather than evidence of it. India's senior fast-bowling stock is the thickest in the world; this match suggests the A-layer of the same conveyor belt may be thinner.

The missing venue is not a small omission. If the series is in India, a surface on which two seamers share nine wickets is an anomaly against the domestic template — and anomalies are the story. If it is in New Zealand, the 78-run lead explains itself and no mystery remains. One absent fact changes the meaning of the result.

The question of duration is the same shape. A-tour fixtures are conventionally four-day, though the source does not say so. In a four-day frame, a 78-run first-innings lead is a considerably advanced position; in a five-day frame it is merely tight. One fact, two conclusions.

On to Mukesh Kumar's five. His profile is clear: a seam-and-swing bowler whose returns cluster where the new ball moves. In a two-pronged seam attack, five wickets matches that profile. But it only becomes skill expansion if we know how many came after the ball softened. We do not. So this is a profile match, not a demonstrated widening of range.

And every Test-readiness conclusion stops here, because three necessary controls are simply unavailable. Opposition strength — an A-level batting line-up is by definition not a Test top order. Pitch character — unknown. Format status — first-class, not Test. Without those, treating this as selection evidence is precisely the small-sample error the data warns against.

One more thing that usually gets dropped. Nine wickets split between two men means this is a partnership story, not an individual breakout. Selectors learn how the pair works together, not how either works alone.

Now the part where the easy reading goes wrong. The surface conclusion is: the bowlers did their job, the batters did not. That may be true, but it is not the most consequential information in this match.

The most consequential information is that a senior fast bowler was deployed in a second-string fixture — and that decision belongs to workload governance, not demotion. Boards use these matches to control a returning quick's overs with a precision a competitive senior Test cannot offer. But the decision has silent cost-bearers: the A-team bowlers whose overs were handed to the returning senior. That loss is recorded nowhere, and the development ground that A cricket is supposed to be erodes quietly.

A second inversion. The narrative temperature around this match is close to zero — A-team multi-day cricket sits at the bottom of the Indian attention hierarchy. That is good news: low noise means low distortion, so the signal is cleaner. But the same silence means nobody will correct anything either. Every IPL performance is watched; a five-for in an unofficial Test concerns no one — which is exactly why the word "unofficial" never gets labelled properly six months later.

A third inversion sits inside the pitch. We derive the surface from the wicket distribution, then explain the wicket distribution with that surface. The circle will not break until a match report or scorecard appears. Analysis that stands on its own inference should not be called analysis too quickly.

The largest risk in all of this is not sporting but informational. A report whose body repeats its headline cannot support any claim beyond the four facts it carries. Before any downstream use — selection argument, series review, statistical table — it must be matched against the scorecard.

So what to watch? Four things. Siraj's next assignment — if he is named in the senior XI for the next red-ball fixture, this was preparation; if not, it was a controlled return. Mukesh's squad status — inclusion would turn those five wickets into a tipping point. India A's second innings — a substantial response reframes the 78-run deficit as a first-innings blip rather than a depth failure. And confirmation of the pitch — a seam-friendly surface validates the whole reading; a dry turner reverses it.

In thirty-two years I have watched this repeatedly: we count wickets because counting wickets is easy. The real story usually sits in the blank space beside that column — where the overs, the runs and the name of the ground should have been written.

That space is still empty. When the full scorecard finally arrives, look at whether the 78 runs behind were caused by the batters, or by the fifth bowler who was never asked to bowl.