The 98-Run Line: India A's Rearguard at Lincoln, and a Scoreboard That Is Not Yet a Verdict

In the final session of Day 2, when India A's score read 10 for 2, one number on the board was speaking louder than the rest: 98. That is the line below which an innings defeat is recorded. The first innings had folded for 113; New Zealand A made 317 in 89.3 overs, a lead of 204. To force New Zealand A to bat again, India A needed at least 204 in the third innings. At stumps they were 106 for 2, still 98 behind, eight wickets in hand.

At Lincoln I watched the day ball by ball on the feed and filled the scorecard columns — runs, balls, fours, movement, mode of dismissal. The habit dates to 2026-89, when I logged 1,986 deliveries of Gujarat's Ranji campaign in a hardbound ledger and nobody asked for the book. The method did not change: count first, opine later.

Day 2 at Lincoln is an argument, not a result.

Context: what an "unofficial Test" actually is

This is an A-team multi-day first-class fixture. Unofficial Test means exactly that — no Test caps, no Test averages, no ICC ranking points. What accrues is a first-class record, and what is being measured is three things: avoiding an innings defeat, managing the first-innings deficit, and time. The operative currency of this format is survival, not scoring rate.

Seam dominated at Lincoln. Nine of the ten New Zealand A wickets fell to pace — Anshul Kamboj three, Auqib Nabi three, Akash Deep two, Mukesh Choudhary one; Washington Sundar took one. That distribution is not a bowling statistic; it is a pitch report. New Zealand A scored 317 in 89.3 overs at roughly 3.54 an over, which points to a surface that is awkward but playable. India A's 113 in reply is the second half of the same signal.

One piece of arithmetic the original report leaves on the floor: the innings-defeat line is never written on a scoreboard, so readers misread it. A 204-run lead against 106 for 2 gives 98. If India A are bowled out for 98, New Zealand A do not bat again. An innings defeat is not a greater humiliation than a match defeat, but it is a different kind of entry in the ledger and should be filed as one.

The third variable is rain. Day 3 carries a rain forecast. Multi-day cricket does not recalculate under DLS; lost time simply removes the overs available to force a result. Rain therefore helps the side that wants a draw and costs the side that needs time to win. India A, at this moment, is the side that wants a draw — which makes the rain a one-way gift only if you stop reading the sentence halfway.

I let the archive speak first, then I checked its receipts. This archive says: across roughly 48 overs, 430 runs and 12 wickets — a fast, eventful, bowler-controlled day.

Core analysis: reading a 96-run stand correctly

The unbroken third-wicket stand from 10 for 2 to 106 for 2 — 96 runs — was the day's dominant event. The headline writes itself: "India A hit back after Rahul and Jaiswal failures." The numbers support the claim. They also say the recovery was a rearguard, not dominance.

Devdutt Padikkal finished 56 not out off 89 balls, strike rate 62.9, nine fours. Sai Sudharsan finished 39 not out off 104, strike rate 37.5. In the last ten overs the pair added 25, about 2.5 an over. Put those three figures side by side and they tell one story: the pair's explicit priority was wicket preservation, not scoring.

Now the detail, because that is where the information lives.

Thirty-six of Padikkal's 56 came in fours — roughly 64 percent. On seaming first-class surfaces a top-order boundary share usually sits between 45 and 60 percent. Sixty-four means most of his scoring ran through the boundary, which means strike rotation was thin. This is not a technical flaw; a 62.9 strike rate reads as fluency above mere survival. But if the same batter meets a slower surface in the coming innings, boundary-dependence becomes a liability, because fours get scarcer and singles carry the load. That is a single-innings reading, so I file it with a medium confidence band, not a verdict.

Sudharsan's 39 off 104 is slow even by first-class standards. Slow scoring in a rearguard is expected; the news is elsewhere. The reported technical note is that he was troubled flicking to the leg side and troubled by balls moving away. That combination — a leg-side flick set-up that breaks down against away movement — is one of the most legible vulnerability patterns at Test level. The mechanism is simple: the flick drops the head and pushes the bat ahead of the pad, and if the ball is leaving off stump and seaming, that same body position feeds the outside edge. This is the kind of flag a bowling plan counts.

Yashasvi Jaiswal's second innings ended on five — a Simon Keene short ball into the body, gloved through to Mitchell Hay while evading. That is not a dismissal mode; it is a template. Evading the short ball and dropping the gloves out of the line is core Test skill. If it recurs, expect a bumper-heavy plan in the next fixture. I am not predicting it. I am noting that a bowler who has found a recipe repeats it.

KL Rahul is the more serious file, and the reason is arithmetic: two innings, 0 and 4. Two different dismissal mechanisms — a duck, then dragging a Fraser Sheat delivery onto his own stumps while playing away from off stump. Two different mechanisms are a bigger signal than one low score, because the second dismissal is a footwork and decision error, not a good ball. Hands away from the body, no control of the off-stump channel. For a senior batter in an A-team fixture, that is a double cost.

Open the other ledger now. The nine-of-ten pace split says three things. The surface had seam and bounce. India A's attack — Kamboj and Nabi with three each — used it. And most importantly: these batting returns cannot be discounted for spin-playing ability and must be weighted heavily for seam-and-movement competence.

One detail the report leaves as a hint: the phrase "lucky to get another chance" implies at least one dropped catch off Padikkal. The stand was therefore not chance-free; New Zealand A's attack beat the bat. When a rearguard includes a drop, call it risk management, not resilience.

Contrarian angle: three places where the story is being misread

First, the senior-versus-junior frame. The easy conclusion is that two seniors failed and two juniors survived, so the hierarchy has inverted. The count does not testify to that. 113 in 208 balls and 317 in 89.3 overs is a statement about pitch and ball, not about batting order. If the surface is yielding 3.5 an over and nine of ten wickets are falling to seam, the operative variable is the surface. Any conclusion that ranks batters while holding the pitch constant is narrative, not sampling.

Second, the convenient reading of rain as relief for India A. In multi-day cricket, rain saves whoever does not want to lose — and right now that is India A, so it looks like relief. The arithmetic runs both ways. India A need 98 runs to avoid an innings defeat; after that they need time to build a winning position, and rain takes exactly that time away. The match sliding toward a draw is also the match sliding out of reach. What is a gift for survival is a curse for a bid — and India A are currently in survival mode, so the gift is temporary.

Third, my strongest objection: treating one innings of 96 runs as evidence of Test readiness. This is a reserve-level fixture, a single-innings sample, and runs here do not enter a Test average. My audit of 214 one-day internationals taught me that a good innings and a good batter are two different things, and collapsing them into one column is the most common accounting error in this trade. I went looking for outliers and found a culture in the decimals; here the decimals say: not enough.

One technical caveat, because it is my habit. I import metrics from football — PPDA, xG, a Press Intensity Index — and have run them on Ranji fielding. No such import survives here. Baseball's leverage index breaks in cricket because eleven players, bowling limits and wicket preservation fracture its assumption. In multi-day cricket, pressure is not a continuous variable; it is a function of time. I have assumed the innings-defeat line of 98 is a hard threshold. If Day 3 loses overs to rain, that threshold loses its meaning and my read changes.

Takeaway: what to watch on Day 3

The first hour of Day 3 will carry the highest information density of this match, and I will log three things.

One, the 98-run line. If India A pass it, the fixture shifts from "avoiding an innings defeat" to "a draw negotiation." If they do not, the 113 cannot be read out of context.

Two, bumper frequency. Jaiswal's dismissal mode is on record; whether New Zealand A's attack repeats it will signal whether they read data or bowl from habit.

Three, Sudharsan's feet. If he adjusts his body position for the flick, the 37.5 strike rate rises; if not, the away-moving ball will knock on the same door.

I file this day with an explicit confidence band: New Zealand A hold the driving seat (high confidence), India A have arrested the slide (high confidence), and whether they have built a winning position is not yet answerable (low confidence). I will reopen this read at stumps on Day 3, same ledger, same font. The auction had a cap; the spreadsheet had a conscience — here the pitch has set the cap, and the batters must spend against the 98-run account.

The question is not whether India A defended. The question is whether, having saved 96, they have the appetite to make 98 — or whether the rain answers for them.