187/9 at Lincoln: When Bad Light Wrote the Scorecard and Padikkal's 199 Was Left Behind

Final session, Day Four. The Lincoln scoreboard read New Zealand A 187 for 9, chasing 313, and India A needed one wicket. Curtis Heaphy was unbeaten on 90 off 187 balls, and at the other end was Cameron Lennox — a No. 11, six runs, the kind of batter you send in for the last wicket and pray survives two overs. The umpires looked at the light, took their reading, and stopped play. Five Indian bowlers, four sessions, a 313-run cushion — all of it waiting for a ball that never came. The match was drawn.

I have been reading this scorecard again and again for the last forty-eight hours, because it took me time to understand whose draw this is. On 13 March 2026 I was in the Eden Gardens press box when India slid to 120 for 8 against Sri Lanka, the stands burned, and the match was awarded to Sri Lanka. I filed the colour piece in forty minutes, and that night I learned the lesson I have carried since: the result is sometimes decided not on the field but on another piece of paper. At Lincoln that piece of paper was the Law on bad light, which quietly became the match's third umpire.

Padikkal made 199 off 248 balls, and the match was drawn. That is the sentence in every wire report. The sentence that is missing is this: in the same match's first innings, the same batter made 32 and the team was bowled out for 113. I built a rule over my career — no name in print without two independent documents. Here the documents are two scorecards from one match, and they contradict each other. That contradiction is the story.

Context: What an unofficial Test is, and what the frame of this match actually was

This was not an ICC-recognised Test. It was an "unofficial Test" between two A sides — first-class status, no Test caps, no World Test Championship points, no ranking effect. The report states plainly that play was suspended for bad light on Day Four, conditions never improved, and the match was declared drawn. A five-day match would simply have resumed the following morning. The fixture was therefore almost certainly a four-day game — and that is a structural detail, not trivia, because a four-day format mathematically raises the draw probability in exactly this scenario.

An A tour never sits in a board's calendar as pure cricket. It is the cheapest verification mechanism both the Indian and New Zealand systems possess, a way of testing second-tier players in genuinely foreign conditions. The report also notes that the second unofficial Test begins the following Saturday — four days between fixtures. A side that has just bowled a full first innings and 65 overs on the fourth day will have to rotate. That matters because the second match's data will not be directly comparable to the first's.

The scoreboard reads like this. New Zealand A made 317 in the first innings — Matt Mariu 76, Dean Foxcroft 51 and 42 — and took a 204-run first-innings lead. India A replied with 516. Devdutt Padikkal was out for 199, sharing a 215-run stand with Sai Sudharsan, and set a target of 313. New Zealand A's second innings was 187 for 9 in 65 overs, roughly 2.88 an over. That rate is not a chase. It is survival, and it means India A were not defending a target — they were trying to take ten wickets. That single distinction changes the shape of the entire match.

Core: First that 113, then that 199 — and the number in between nobody is reading

When I read a scorecard I look for the stamp and the date, not the quote. Here the date does not matter; two numbers do — 113 and 516. The same batting order, in the same match, against the same attack, produced a 403-run difference. Four hundred and three. In cricket that is not normal variance. In fifty years of notebooks I can recall very few occasions where a side made 113 and then 516 in the same match, and every time it happened, two explanations surfaced: either the pitch changed character, or the first-innings technique collapsed against seam movement. There is no pitch report in this file, so both remain open. But for a selector, one number matters more, and it is not 199. It is 32.

The real signature of Padikkal's 199 is its strike rate — 80.2. That is unusually aggressive for a top-order batter in first-class cricket. Of his 199, 114 runs — 57.3 per cent — came from just 27 scoring shots: 24 fours and 3 sixes. The other 85 came off 221 balls at roughly 0.38 runs per ball. This is a high-ceiling innings; it does not show a high floor. A batter whose scoring engine fires a boundary every nine balls makes 199 when the pitch is placid and 32 when the ball is moving. Both numbers come from the same method.

I want to be precise here, because everything downstream collides with it. The report does not say which ball he was out to, who bowled it, or whether DRS was in operation. It says only that he was "given out caught behind" — on 199, one run short of a double century. That one run is where cricket journalism builds its biggest story, and where a selection committee makes its worst decision. Being one short of 200 is statistically meaningless and narratively explosive.

The 215-run stand is this match's most under-priced tactical fact. Sudharsan (91) and Padikkal, both left-handers. Letting two left-handers bat a long partnership is a specific problem for any attack: it forces bowlers off their natural angle and commits a footmark pattern outside the left-hander's off stump that is hard to fill. The report does not say how New Zealand A responded — how many overs over the wicket, how many round, what angles the spinners used. Without that, the technical read is incomplete. What is visible is that this partnership is a repeatable asset, not a one-off.

Padikkal's two wickets — Sheat and Gibson — should not be over-read. Both were No. 8 and No. 9, with the game seven or eight wickets gone. That is tail-cleaning within a part-timer's brief, not a fifth-bowling option. I have watched twenty years of good innings and two tail wickets manufacture an "all-rounder," and I am saying plainly: this is not one.

Auqib Nabi: the name that should be at the top of the scorecard

The strongest selection signal in this match is Auqib Nabi — 6 wickets across two innings (3+3) plus 38 runs. He out-bowled better-known names and kept his side in the game through the second innings. The report does not say how many overs he bowled, in what situations he took wickets, or off which deliveries. That information should come from the full scorecard and should be in the selectors' hands before the next match. What is available is enough to say there is a working member in the attack.

This is where the registrar principle applies, the one I built after 2026. The press release says India A's bowling is strong. The scorecard says that after bowling a side out for 113, it could not prevent 317, and in the fourth innings it took nine wickets in 65 overs without the tenth. The gap between those two paper statements is the team's real picture. The press release does not win; the registrar does.

Washington Sundar's return: 52 runs and one wicket — a soft negative

Sundar made 52 with the bat, which is about par for his ability. But he took only one wicket in the fourth innings — on a surface that had already produced 516 and 317 in the match. The report does not state how many overs he bowled. If he bowled a significant share of the 65 and took one wicket, that is an underperformance in precisely the role he is selected for. This is a directional observation, not a verdict, because the overs are unreported. I log it because the question should be asked before the second match, and because the spin all-rounder's slot is the least scrutinised place in Indian cricket.

Heaphy's 187 balls: the biggest innings of the match is the one without a headline

Heaphy finished 90 not out off 187 balls, a strike rate around 48. That is a textbook fourth-innings blocking innings. It is roughly 48 per cent of New Zealand A's 187 for 9, compiled with a No. 11 at the other end. India A had 65 overs, five bowlers, a 313-run cushion and nine wickets. They could not get the tenth. If you ask me which innings mattered most in this match, I will not say 199. I will say the 90 not out, played by a side that was losing, with a partner who is not a batter, against an attack that needed one ball. Since the night of 13 March 2026 I have known that a result is sometimes settled not by the biggest score but by the longest stretch of time.

And the question nobody is asking: when was the declaration

India A had only 65 overs in the fourth innings before the light came. For any Test-standard attack, on a surface that had already yielded 833 runs, 65 overs is thin for taking ten wickets. That number is itself a signal that the declaration was either later than optimal or that the second innings consumed more time than expected. The report does not state the declaration timing — a gap that leaves the match's tactical reading incomplete. But the arithmetic available says: nine wickets in 65 overs, and no time for the tenth. When a captain has a 313-run cushion and cannot finish the game in 65 overs, the argument is about the declaration, not the weather.

Contrarian: the "199 in vain" frame is wrong, and it is the biggest deception in this story

Now to the part where I have to fight the framing that has spread furthest. "199 in vain." The phrase is factually loose, and I am saying that by reference to the document. That innings turned a 204-run deficit into a 313-run target. It put India A into a genuine winning position. It saved the match; it did not lose it. What did not happen was a result — and the light stopped the result, not the batting. Saying "199 in vain" is the same error an accountant makes when he looks at a profit-and-loss statement and declares the company worthless, when the company has paid every liability and only the bank's closing hours stopped the cheque clearing.

But the real contrarian point is sharper. If you want to send one number from this match to the selectors, it is not 199 — it is 32. Because 199 came on a pitch that had gone placid, where 516 was made, where a 215-run stand happened. And 32 came in an innings where the ball was moving, where Simon Keene took five and Zak Gibson three, where the whole side was bowled out for 113. India's senior tours go to New Zealand and England, where the ball moves in the first innings and not the second. Selection on 199 produces a batter who scores hundreds on friendly pitches. Selection informed by the gap between 32 and 199 produces a batter who knows what to fix.

I also have to say that the least-priced performance in this match is not the one being written about most. Heaphy's 187-ball 90 not out, with a No. 11 at the other end, is the product of a cricket culture that keeps producing Test-standard players from a small domestic market. The Plunket Shield is built on exactly this temperature — patience first, power later. India's system runs in the opposite order: power first, patience if there is time. Lincoln showed what happens when the two meet on one ground: the patient system survives the session in which the powerful one cannot close.

And one last point, the one that stings most: this match may be entirely the product of an administrative lapse. The report says play stopped for bad light on Day Four and conditions never improved. It does not say whether the ground had floodlights, and it does not say whether switching them on was attempted. If Lincoln had no usable lights, this draw was not a weather event — it was the direct consequence of the host board's venue selection. Four-day match, unlit ground, New Zealand's late-summer light: add those three and the draw is decided before a ball is bowled. The cricket did not write the result; the calendar and the electricity supply did. I am not alleging intent. I am saying that when you schedule a four-day match where daylight is uncertain and artificial light is not provisioned, your scheduling choice is choosing your result. I went to the registrar, and what is there is all the preparation that precedes a result — with one hole in it.

Takeaway: three questions the scorecard must answer before next Saturday

With the second unofficial Test starting next Saturday, four days away, three things are worth watching — and they will decide whether Lincoln's draw was an ordinary weather event or the first link in a pattern. First: how Padikkal bats in the first innings. If he makes 40 or 50 in seam movement and takes the team to 250 or 300, then the 32 was about the pitch, not the technique. Second: how long India A take to get the last wicket. If the last pair survives twenty-plus overs again, that is attack composition, not a one-day wonder. Third: the second-innings figures for Keene and Gibson. If their workload explains the 516, that is the ordinary outcome of a small squad. If not, it is a story about surface or technique.

One thing is clear to me across all of this. A-team cricket is played for its convenience, not for its information — and convenience means deciding who writes the result. At Lincoln, the umpires wrote it. If the same story repeats from next Saturday, we will have to accept that an unofficial Test does not mean an unfinished match; it means nobody owns the job of finishing it. And I have been asking for thirty-five years: if the result is nobody's responsibility, whose testimony is it?