From 113 to 106/2 in Lincoln: The Top-Order Audit India A Has Not Yet Passed

The number glowing on the Lincoln scoreboard at the close of Day 2 was 106/2. Devdutt Padikkal unbeaten on 56 off 89 balls with nine fours; Sai Sudharsan unbeaten on 39 off 104 with a handful. Their unbroken stand was worth 96. And right there, on the second line of the same card, sat the contradiction: India A still trailed by 98.

In the first innings of the same match, this same side was bowled out for 113. Across two innings, roughly twelve top-order wickets fell for about 123 runs, set against one partnership of 96. That contrast is the real story here — not 317 versus 113, but two different faces of the same structural weakness.

Data provenance box

• Sample: one first-class fixture, through Day 2; one innings per batter
• Model version: Rolling-Window Audit v3.2 (10/20/50-innings blocks pre-committed)
• Source: Times of India match report; single source, not independently corroborated; publication date not stated in the source material
• Blind spots: overs per bowler, pitch map, attendance, field placements, DRS decisions
• Confidence: scores and names high; pitch character and follow-on medium; technical causation low-to-medium

I logged 1,842 shots before I trusted the pattern. Before that, every innings was a separate story, and a story is something that lives outside verification. This Lincoln scorecard arrives as two separate questions: is the 96-run stand a repair job on the top order, or a curtain drawn over a collapse? And are KL Rahul's 0 and 4, and Yashasvi Jaiswal's 5, a form crisis or simply what happens to anyone against the new ball on this surface?

The questions look separate; the answers converge in one place — whether we are about to write a career verdict off a single innings.

Context: the match that is not a Test

First, a format caveat, because without it every subsequent calculation runs in the wrong direction. This is an unofficial Test between two A teams — a multi-day first-class fixture, typically four days. No Test caps, no World Test Championship points, no ICC ranking impact. Conclusions here cannot be transferred to the senior India Test side, and certainly not to T20 or ODI contexts.

The venue is Lincoln, New Zealand, early in the season, when the ball generally seams and swings, especially in the morning. For a subcontinental top order this is historically the hardest overseas assignment. A first-innings 113 alongside New Zealand A's 317 supports a reading of a helpful pitch, though it remains a reading.

New Zealand A's innings was built by three men: Mariu 76, Foxcroft 51, Clarke 42. The notable figure is not the runs but the balls — all three occupied the crease, absorbed the new ball, and made the pitch behave. Exactly the work India A's top order did not do in innings one.

India A's wickets were spread across the attack: Kamboj 3, Nabi 3, Akash Deep 2, Sundar 1, Choudhary 1. Two readings follow. No single bowler could break New Zealand A's top order; and the pressure was collective, which is a good sign at team level. But a side that concedes 317 has no grounds for extra enthusiasm about its bowling unit. The source does not disclose overs per bowler, so I have no workload number — only a concern.

I am deliberately keeping the follow-on as an inference. New Zealand A led by 204, and the standard first-class threshold for enforcing the follow-on sits at 200. The innings sequence — India A bat, New Zealand A bat once, India A bat again — is structurally consistent with the follow-on having been enforced. The report does not say so, so this stays a medium-confidence inference, not established fact.

Crowd absence turns out to be unexpectedly relevant. An A-team fixture means a near-empty ground, and at a small venue like Lincoln that is especially visible. In May 2026, analysing the first empty-stadium Revierderby, I learned that the empty stadium does not erase home advantage; it exposes its skeleton. The same applies: dismissals, umpiring decisions and a bowler's rhythm all sound cleaner without a crowd. But I never trust that inference alone. Attendance, noise, umpiring patterns and bowler load have to be triangulated — otherwise the empty-ground explanation covers half the story, and half an explanation cannot measure a top-order failure.

There is also a concrete weather threat: rain is forecast for Day 3. In a multi-day first-class match, rain is governed by playing conditions and ground regulations, not the DLS method, which belongs to limited-overs cricket. Practically, rain raises the draw probability — and a draw would strip the fixture of its assessment value, burying the first-innings collapse without extracting any lesson from it.

Core: the arithmetic of two innings

Take Padikkal's innings. 56 off 89, a strike rate near 62.9. Nine fours means 36 runs from boundaries — roughly 64 per cent of his total. A first-class top-order strike rate usually sits between 45 and 55, so 62.9 is a positive tempo signal on this surface. It also means boundary dependence, which is a method that can fracture quickly on a seaming pitch. And the report explicitly notes he was fortunate to get another chance. That is not a measured data point but a reporter's eye-test signal, so I file it as a low-confidence tag, not a verdict.

Sudharsan's innings is the mirror image. 39 off 104, a strike rate near 37.5, below the first-class benchmark. But calling the innings small because it was slow would be a mistake. The report notes he was troubled by balls moving away and struggled to flick to leg. That is a specific, addressable weakness — a technique question, not a strike-rate question.

This is where rolling-window discipline matters. I pre-committed to evaluating batters in 10-, 20- and 50-innings blocks, and I do not choose the window after the match. Why? Because a single innings cannot separate 62.9 from 37.5. If the gap holds across a 10-innings block, Padikkal is the more assertive accumulator in these conditions; if the two converge over 20 innings, the gap belonged to the innings, not the batters. Without that constraint I could prove any conclusion by picking a friendly window — which is the biggest trap of all.

Now the heavier data, weighted by seniority. KL Rahul made 0 and 4, dismissed second time dragging a Fraser Sheat delivery onto his own stumps while playing away from his body. That is not misfortune; it points to an alignment and outside-off problem. Two single-digit scores matter more for a senior player because the opponent here is his own balance, not an unfamiliar attack.

Jaiswal fell for 5, gloving a short ball that followed him to wicketkeeper Mitchell Hay. The bouncer tracked his body line — the kind of dismissal that will recur relentlessly in Test cricket unless front-foot alignment is addressed. One innings is not a pattern, but it is a signal that must be tracked against pace-heavy attacks.

The match arithmetic is clear. A lead of 204 cut to 98 is not a luck-distorted scoreline. India A were bowled out for 113, slipped to 10/2, then produced 96. The top-order failure is the structure of the match; the stand did not break that structure, it only delayed its disclosure.

My pitch reading: 113 versus 317 implies new-ball seam dominance, with the surface settling somewhat — visible in New Zealand A's 76/51/42. Medium confidence. What would falsify it? If both collapses were spin-driven or pace-off, or if India A folded again below 120 in innings two. Neither has happened yet, so the reading survives — not proven, only surviving.

In these conditions the definition of a good innings changes. Success is measured in balls per dismissal, not strike rate. Padikkal's 89 balls for 56 is valuable on that metric. Sudharsan's 104 balls for 39, unbeaten, is time bought, which is not cheap on this pitch. Same job, different method. The question is which method holds when the new ball returns in the morning.

One large data gap deserves acknowledgement: no overs per bowler, no pitch map, no field placements, no attendance. Within that gap I can only say that India A's wickets were shared, that New Zealand A's top order was never broken by one bowler, and that a follow-on scenario adds load to this pace attack. Anything beyond that turns inference into fact.

Contrarian: the easy story is the suspicious one

Now the easy story — seniors fail, youngsters rescue. It is not factually wrong. Rahul 0 and 4, Jaiswal 5, against Padikkal and Sudharsan's 96. But correlation is not causation. The same pitch made Rahul look finished and Padikkal look assertive; the surface and the age of the ball did at least as much work as the hierarchy of talent. Ignore that and we turn two batters into citizens of different eras.

I do not chase narratives; I archive them until they confess. The archive currently says: one innings of senior failure does not prove a form crisis, and one innings of a young half-century does not secure a future Test place. Both conclusions are the fastest announced under media and fan pressure, and both are the least verified.

The word lucky also raises a provenance objection. A reporter's impression of fortune is not a metric; it has no sample size and no definition. I still do not discard it, because the eye sometimes reports truth before the data does. I file it as a low-confidence flag — meaning the 56 should be celebrated only after the next innings.

System-fit scepticism cuts the other way too. Declaring Rahul finished off this match, or hardening Jaiswal's short-ball issue into a permanent flaw, is system-fit fatalism. Solutions exist: a batting-position shift for Rahul, front-foot alignment and short-ball defence sessions for Jaiswal, left-elbow control against the ball leaving him for Sudharsan. Transition costs and growth curves belong in the ledger, otherwise one innings becomes a career seal.

Through a transfer-window lens this fixture has another layer. An A tour is the upstream supply chain for national selection, and domestic returns feed indirectly into future auction valuations. But transfers are ledgers with human weather, not just rumors — and this report contains no market data, no fee, no contract. What it does confirm is a process truth: a batter who scores under pressure here does not raise his price, he raises his chances.

The source's own provenance belongs in the ledger. It is a single-source Times of India match report, carrying an app-promotion line that is a media-monetisation footnote, not cricket-business data. A single source means a single framing; without corroboration we cannot know how much of the lucky tag is editorial colour and how much is ground reality.

Takeaway: what Day 3 must show

With rain forecast, the first question is not about the result but about how many overs reach the screen. If enough play happens, three things matter: whether Padikkal survives a fresh-ball spell, whether Sudharsan opens the leg-side flick, and whether Rahul, given a second innings, can leave the ball outside off stump.

Before the next fixture I am pre-registering the evidence threshold: at least four innings for Rahul, at least three pace-heavy innings for Jaiswal's short-ball tracking, and a 10-innings block before comparing Padikkal with Sudharsan. Below that threshold I will publish data, not verdicts. It will read slowly; for sharp bettors, that is the only method that works.

A bet is a hypothesis with a scoreline attached, and this scoreline has not finished with its hypothesis. A 98-run deficit is bridgeable — if the pitch stays quiet, the rain stays away, and the new ball does not break the top order again. Break one of those three and the story changes.

The closing question is simple, the answer is not: is Lincoln's 96 the first sentence of a new top order, or the last footnote of a 113-run collapse? The spreadsheet is a quiet room where noise finally sits down — the answer is in there, but it will take two more innings to read.