Lincoln, Day 2: India A's 96-Run Stand Averted the Innings Defeat, but the Ledger Recorded 2.5 an Over
**मुख्य उत्तर (58 शब्द):** लिंकन में दूसरे दिन भारत A ने 106/2 पर स्टंप्स होते हुए 98 रन की कमी बाक़ी छोड़ी, जबकि पहली पारी 113 पर सिमटी थी और न्यूज़ीलैंड A ने 317 बनाकर 204 की बढ़त ली। तीसरे विकेट के लिए देवदत्त पडिक्कल (56*) और साई सुदर्शन (39*) की 96 रन की अटूट साझेदारी ने पारी की हार टाली; अंतिम दस ओवरों में 25 रन बने। **मुख्य तथ्य:** - भारत A पहली पारी 113; न्यूज़ीलैंड A 317 (89.3 ओवर; मारिउ 76, फ़ॉक्सक्रॉफ़्ट 51), बढ़त 204। - पडिक्कल 56* (89 गेंद, 9 चौके, 64% रन सीमाओं से); सुदर्शन 39* (104 गेंद, स्ट्राइक रेट 37.5)। - अंतिम दस ओवरों में भारत A ने केवल 25 रन बनाए, यानी लगभग 2.5 रन प्रति ओवर। - दस में से नौ विकेट तेज़ गेंदबाज़ों के: कंबोज 3, नबी 3, आकाश दीप 2, मुकेश चौधरी 1। - तीसरे दिन बारिश का पूर्वानुमान; बहु-दिवसीय क्रिकेट में DLS लागू नहीं होता। **स्रोत:** IND A बनाम NZ A प्रथम अनऑफ़िशियल टेस्ट, लिंकन — दिन-2 स्कोरकार्ड एवं बॉल-बाय-बॉल लॉग; मूल प्रकाशन तिथि उपलब्ध नहीं। **संबंधित प्रश्न-उत्तर:** प्रश्न: क्या भारत A पारी की हार से बच गया? उत्तर: नहीं, भारत A अभी 98 रन पीछे है और उसे पारी की हार टालने के लिए कम से कम 204 तक पहुँचना है। प्रश्न: लिंकन की पिच कैसी रही? उत्तर: न्यूज़ीलैंड A के 3.54 रन प्रति ओवर और दस में नौ तेज़ विकेट बताते हैं कि सतह मुश्किल थी, असंभव नहीं। प्रश्न: तीसरे दिन की बारिश का क्या असर होगा? उत्तर: ड्रॉ की संभावना बढ़ेगी, पर भारत A के पास जीत की स्थिति बनाने का समय भी घटेगा।
The board at stumps in Lincoln read 106 for 2. Read quickly, that number is a rescue: a hundred on the board with eight wickets standing, the third wicket unbroken on 96, a first innings of 113 already half erased. My ledger for the same final session carries a second line — 25 runs in the last ten overs, roughly 2.5 an over; Sai Sudharsan on 39 off 104 balls, a strike rate of 37.5; Devdutt Padikkal on 56 off 89, nine fours, 36 of his runs arriving in four-run lumps, about 64 per cent of his output. The scorecard says India A held. The ledger says India A held and nothing more. That gap is the story of the day, because what India A need from here is not a chase but a floor: they are 98 short of simply making New Zealand A bat again, and the arithmetic of time, wickets and scoring rate changes once the target is a floor rather than a chase.

Format separation first, because the easiest error available here is to blend formats. This is an A-team multi-day fixture, an unofficial Test: no Test caps accrue, no official Test averages move, no ICC event is involved. Everything that happens in Lincoln can be read as Test-level preparation and cannot be recorded as Test performance. My method is ball-by-ball logic and phase splits, and one non-negotiable condition: this match's data stays inside this format and gets no borrowed authority from anything played in whites at a higher level or in coloured clothing at any level.
The shape of the match is simple. India A were bowled out for 113. New Zealand A replied with 317 in 89.3 overs — Mariu 76, Foxcroft 51, Clarke 42 — at about 3.54 an over, which tells you the surface was awkward rather than unplayable. India A then lost two wickets with 10 on the board before reaching 106 for 2. The lead sits at 204. India A trail by 98 with eight wickets in hand.
The bowling split is the cleanest signal in the file. Anshul Kamboj took 3, Auqib Nabi 3, Akash Deep 2, Mukesh Choudhary 1, Washington Sundar 1. Nine of ten wickets went to pace. One spinner played, he took one wicket, and everything else came through seam. That single line does two jobs: it reads the pitch, and it sets the weight that any batting judgement from this match can carry for spin-playing ability, which for now is close to zero.
Three caveats sit above everything that follows, because without them every sentence turns into an opinion. One: the sample is a single innings, 89.3 overs and ten wickets of it. Two: I do not have the pitch report or the toss result, so any claim that conditions favoured one side lacks a comparison group. An empty stadium is not a quiet stadium; it is an uncontrolled experiment, and a pitch with no report attached is the same kind of uncontrolled experiment. Three: whether this fixture is scheduled for four days or five is not stated anywhere in the material I have, and that single unknown moves both the follow-on threshold and the time left to force a result.
Now the arithmetic the scoreboard does not show. The lead is 204, the score is 106 for 2, so India A need at least 204 from this innings to make New Zealand A bat again. Below that, an innings defeat. This is not a target, it is a floor, and the floor has to be reached on a surface where the new ball is doing something, where the first innings stopped at 113, and where the tail begins to be exposed from seven down. The real question is not how many runs but how many overs, and the rate at which the partnership scores is what answers it.
Break the 96 stand open. The last ten overs produced 25 runs, about 2.5 an over. That is a rate that walks towards a draw and never towards a win. Sudharsan's 39 came off 104 balls, a strike rate of 37.5, which is below par even by first-class standards for a top-order batter. Calling it patience is generous; technically it is occupation without dominance, and the report itself supplies the reason. Sudharsan was troubled flicking to the leg side, and troubled by balls moving away. When a batter's leg-side flick set-up breaks down and the ball is also leaving him, his scoring zones shrink from both directions — the bowler can go straight at the stumps, stack the off side, and leave no route out for singles. The 37.5 strike rate supports that reading. The caveat travels with it: one innings, one surface, and a technical note built on a handful of deliveries.
Padikkal's innings has a different and possibly more revealing profile. 56 off 89 with nine fours, 36 runs from boundaries, roughly 64 per cent of his output. A first-class top-order boundary share usually sits in the 45 to 60 per cent band. At 64 per cent, runs were coming but strike was not rotating: balls were left, dots accumulated, and the score moved in four-run jumps. That is the profile of a driver, not an engine. On slower surfaces that profile is the first to stall, because when the fours stop, the board stops. The sample is one innings, so it is a directional signal and not yet a trend, and I am recording it as exactly that.
Two failures in this file say more about technique than about scores. Yashasvi Jaiswal was out for 5 in the second innings, gloving a short ball from Simon Keene to the keeper Mitchell Hay while trying to evade it. That is a dismissal mode, and modes repeat. Short-ball evasion is a core multi-day skill; if the same shot recurs in the next innings, a bumper-heavy plan in the following fixture should be treated as the default expectation rather than a surprise — it is the cheapest strategy available to the opposition, not a prediction.
KL Rahul's file is more expensive. Zero and four, two failures built on two different mechanisms. In the second innings he played away from off stump at a Fraser Sheat delivery, dragged it back, and lost his stumps. That is not a good ball beating a batter; it is a footwork and decision error, and that is why it is a heavier signal than a low score. When the hands go away from the body and the bat cannot cover the off-stump channel, the bowler does not have to invent anything; he repeats the line. For a senior batter it is also the fastest thing to fix and the fastest thing to be exposed again.
The luck column has one entry and hiding it would be dishonest. The report implies Padikkal was given another chance, which means a catch went down. If a drop is inside the 96, the stand cannot be described as purely earned against the bowling; New Zealand A's seamers kept beating the bat and created at least one chance. I keep one column for the things I cannot measure yet, and that is the entry: I cannot tell you how hard the chance was, so it stays as an unknown share of the partnership rather than being filed under fate.

The bowling numbers carry a visible gap of their own. Kamboj and Nabi with three wickets each are India A's biggest relief of the day, but overs, economy and spell length are not in my material, so saying the pace depth has been proven would be the exact error I try to avoid. Wicket counts are an outcome; spell loads are a cause. Advancing the outcome without the cause is how a ledger stops being a ledger.
Return to New Zealand A's 3.54. Three hundred and seventeen in 89.3 overs on a surface where India A were bowled out for 113 says the pitch was not a minefield; it was difficult and playable, a surface that rewards application and punishes a lapse. That reading removes the pitch as an alibi for 113. The home middle order made 76, 51 and 42 on the same surface. For a touring side that is discomfort, not excuse.

One honesty note I repeat in every multi-day piece: I borrowed xG for one season and spent two years returning it, and the lesson was that in cricket an expected-runs model without wicket risk is incomplete. I do not have a calibrated expected-runs figure for this innings, because a single innings of ball-by-ball data cannot calibrate anything. So I will write only what the ledger carries: 96 runs, 25 in the last ten overs, strike rates of 37.5 and 62.9, and a 64 per cent boundary share. Everything past that is an estimate, and it will be labelled as one.
Here the commentary and the ledger part company. The aggregate of the day belongs to New Zealand A. The journey from 113 to 317, a lead of 204, is the largest event of this match. India A's 106 for 2 arrests that event; it does not reverse it. What the broadcast is calling India A's day is, more precisely, India A's final session. The ledger disagreed with the broadcast, so I stayed up to find out why, and the reason is a habit in this market: a session-ending rate of 2.5 an over gets described as resilience when it is the rate that walks towards a draw.
The second gap is the senior-versus-junior frame. Rahul and Jaiswal failing while Padikkal and Sudharsan survive is being read as a generational handover. That is correlation drawn from one innings. Career rankings do not move on two innings, and I have written my threshold down before the fact: if Padikkal's boundary share stays above 60 per cent across the next three innings on slower surfaces with no improvement in strike rotation, the concern becomes a finding; if it falls to around 50, this innings was noise and I will call it noise.
The third gap is the weather. Rain is forecast for Day 3, there is no DLS recalculation in multi-day cricket, and lost time simply removes the overs available to force a result. That cuts both ways. Rain raises the probability of a draw, which helps India A avoid defeat, and it also truncates the time India A would need to build a winning position. Anyone reporting rain as straightforwardly good news for India A has run one branch of the calculation and skipped the other.
Three pre-registered conditions for Day 3. First: if India A erase the 98 at better than three an over inside the first thirty overs with six or more wickets standing, the match turns into a fourth-innings setup of roughly 120 to 180 in about fifty overs. Second: if they bat sixty overs at 2.5, the deficit goes and so does the clock, and a draw becomes the only honest outcome left. Third: watch the bumper plan to Jaiswal and the off-stump channel against Rahul. And the thing I cannot measure yet stays where it is — that dropped chance. If it turns out to be the hinge, then the next time I quote 96, I will subtract one life before quoting it.
