Two Hundreds, One Draw, and the Scorecard Nobody Filed

Four hours after the match ended I still did not have a scorecard. The wire copy carried one line: the second unofficial Test between India A and New Zealand A ended in a draw. That was it. No toss, no innings totals, no bowler's spell, not even which country the thing was played in. Underneath that line hung two names — Yashasvi Jaiswal, century; Yash Rathod, century.

The file said draw. The ground said two hundreds.

That gap is not new to me. At sixteen, at Azad Maidan, a groundsman told me the boy I had been watching in the nets at eight in the morning slept in a tent forty metres from the pitch and sold pani puri outside the ground. No paper had his name then. A year later, when he made 319 in the Harris Shield, every outlet suddenly remembered the tent. I pasted a line into my notebook that day: the file writes one thing, the mud on the boots says another, and the job is to measure the distance between them, not to close it.

This time the distance runs the other way. The mud has almost all the answers and the file has almost none. This piece is about that incomplete file — and about what a cricket writer can honestly say when the scorecard itself has gone missing.

Unofficial Test: Test in name, not in status

Start with the thing that gets muddled every single time. This is an unofficial Test. It carries no ICC Test status. In the language of the game it is a first-class fixture staged by two boards for their A squads. Which means the hundreds Jaiswal and Rathod made are first-class hundreds, not Test hundreds. Within a day those numbers will dissolve on social feeds into 'Test century', and nobody will remember the correction was there to be made.

The whole A-team ecosystem runs like this. No ranking, no points table, no official record. The scorecard sits on a tour page for a few days and often vanishes the moment the series ends. Pitch photographs, toss details, daily weather — none of it reaches an archive. I have kept a folder for India A tours for years precisely because nobody else keeps the paper trail. Every academy is a dig site and the press release is topsoil. Here, though, the topsoil came off and there was no city underneath — only three things. A draw. A hundred by Jaiswal. A hundred by Rathod.

I learned that limit in Potchefstroom. February 2026, the Under-19 World Cup final, a thirty-seat press box and me the only woman in it. I was asked to collect the emotional quotes while the men handled tactics. I filed the tactics piece anyway. Six weeks later India locked down, age-group cricket stopped for eighteen months, and my beat simply ceased to exist. In that silence I built 'The Lost Batch' — 240 players traced through every scorecard I could dig up. Silence, it turns out, is also a source, provided you have the nerve to write down what you could not find.

This piece is written that way. What exists is stated plainly. What does not exist I will not fill with inference.

Jaiswal's hundred: confirmation, not discovery

Background note, flagged clearly — this is not from the stage-1 data, it is public record: Yashasvi Jaiswal is India's Test opener. 171 on debut in Dominica in July 2026, 209 against England in Visakhapatnam in February 2026, 712 runs across that five-match series. Those numbers sit in his file already and they are larger than any A-team hundred.

So calling this a comeback or a return to form is wrong in both directions. If he was in poor form, I would need ball-by-ball evidence from his last twelve months, and I do not have it. If he was in good form, this innings proves nothing new. Either way it is the smallest data point in his file. The question is not how many he made. The question is why he was there at all.

I am genuinely asking, and I do not have the answer. There are four possibilities, all of them guesses, and I will not dress them as fact: red-ball rhythm after a break; workload planning that wanted bowlers watched through long spells; top-order preparation ahead of a series; or a selection conversation whose minutes are never published. Any of those could be the story. Without confirmation, any of them is just an attractive guess, and an attractive guess is the cheapest commodity in this trade.

One more layer, from my other degree. My MS is in kinesiology and I started writing about workload during the shutdown because there was nothing else to write about. That training gave me a habit: I ask how many balls and how many hours in the sun a body absorbed this month, not how many runs came out of it. A red-ball hundred means three to five hours of continuous load — repeated twos, squats, stops and restarts — spent across lower back, hamstring and calf. The real accounting comes from ball counts, not scorelines. I have no ball counts here, so I cannot tell you whether this innings was cheap or expensive for his body.

What I can say is that for a batter his age, a hundred at this level is a calendar question more than a physical one. Which month, before which series, on what surface. I have none of those three.

Rathod's hundred: a claim, not a confirmation

This one carries a different weight, and the difference matters. For Jaiswal the hundred confirms a name. For Rathod it is a claim — a document saying send me upward.

My notes place Yash Rathod in that sedimentary layer of domestic cricket where the names are large and the cameras are few. That is background, not stage-1, so I am flagging it at medium confidence. Domestic cricket is where careers are actually formed, and the problem for batters who come out of it is that their hundreds land in the third paragraph of a match report, if they land at all. I found him where I always find them — in the third paragraph of a report nobody kept, at the point where the list of 'other scorers' runs out.

I am not going to convert the hundred into a narrative. One hundred in one A match is a claim. To call it a trend I need three things and I have none of them.

First, repetition. The real signal for an emerging batter is the second hundred, not the first. The list of players who made one and stalled is long every single season. Second, environment. Runs at home and runs away are not the same number, and I do not even know where this match was played. Third, the type of bowling. A cover drive against seam and a sweep against spin both land in the same 'hundred' column. Without knowing which was which, I cannot write a word about technique.

What I can write is his age. In my under-23 spreadsheet the first column is never an average; it is age at first-class debut. In 2026 my editor called that habit a gimmick. I said it was a variable. Eight years later it is still the first column I fill, because age does not decide a career but it tells you how much time is left in one.

Read the draw as data and you get nothing

Here is where the real story of this match sits — and the story is that we do not know why it was drawn.

Four possibilities. One, the pitch was so good for batting that neither side could take twenty wickets. Two, rain or light ate enough time that a result was never on the table. Three, one side batted for three days and a declaration never became relevant. Four, both attacks were so toothless that even on that surface they could not manufacture seventeen wickets. Confirming any one of those needs the scorecard, and the scorecard is not with me. So my conclusion is that my conclusion is zero — and I am printing that rather than deleting it.

This is exactly where my objection to the data invasion of dressing rooms sharpens. A number that arrives without the conditions that produced it is not information, it is noise. In football I spent years watching teams hold sixty per cent of the ball with three touches in the box, and the commentary box praising the sixty. Cricket's red-ball version of that disease is the draw. A draw is not a performance. A draw is an empty box into which anyone can place their preferred story — the pitch was flat, the weather stole the game, our bowling is weak. None of the three is provable. All three sell.

Team level, the same caution applies. India A produced two centuries and that is real. It does not follow that the batting depth is healthy, because I do not know how many batters batted, in what order, or what the rest were doing. Nor can New Zealand A be blamed for failing to force a result — forcing one requires a declaration and enough time, and I have neither detail. Home advantage is a fair general assumption in A-team series, but stage-1 does not even identify the host. Comparing two national pipelines off one drawn game is reviewing an entire film from a single frame.

What a hundred is actually worth

The Jeddah night keeps pulling me back to this question. November 2026, an eleven-hour live desk, Rishabh Pant at 27 crore, Shreyas Iyer at 26.75 crore, and me arguing my editor into a piece on a thirteen-year-old left-handed opener from Bihar who went to Rajasthan Royals for 1.1 crore. My argument was that in the IPL, age is the cheapest part of a player's price. That night I built a small value-per-crore table.

In A-team cricket the logic inverts. Value here is not counted in crores but in innings. Rathod's hundred is worth whatever his next three hundreds make it worth. Jaiswal's is worth close to nothing, because his file is already heavy — one innings neither added to it nor lightened it. The two hundreds look identical in the same wire copy and are not identical at all. That is precisely where readers get cheated, because the headline puts them on the same line.

What I could not check is also the report

Better to declare terms up front. I have three certain things about this match and I stated them at the top: the draw, Jaiswal's hundred, Rathod's hundred. Everything beyond that is either flagged background or explicitly labelled guesswork.

What I could not verify, I will also list. The nature of the pitch. Weather and time lost. The toss. Both playing elevens. Bowling figures. The reason is structural: unofficial Test data does not live in a central archive. It travels with the tour and leaves with the tour. I am not going to claim this was hidden deliberately. It is an administrative gap and it should be called an administrative gap. Calling a clerical failure a conspiracy is the easiest and shabbiest move available to a reporter.

But one observation is a pattern rather than an accident, and patterns cost something. Our public cricket memory is built around the senior men's team. The day a senior player tweaks a finger, every camera is there. The day two young batters make hundreds for the A side, we get a wire line. That is not prejudice, it is economy — the camera goes where the advertising is. The consequence is that we keep our worst records for our most important cricket, the cricket where careers are actually made.

The counter-intuitive read

Now the part where I have to walk back my own framing. The two easiest stories here are that Jaiswal is back in form and that Rathod is the next big thing. Both strike me as wrong for the same reason: neither has a denominator.

To claim Jaiswal has returned to form you first have to show he had left it. Twelve months of innings-by-innings data, the type of bowling he faced, home-away splits, dismissal patterns — none of it is in this file. When you do not have the earlier number, you cannot measure a return. You can measure one hundred, and one hundred is a very small thing.

The more interesting inversion is this: an established Test opener turning out for the A side tells you less about the player and more about the system. Who built the calendar, who wanted red-ball minutes and why, who set the workload — that story is larger than the hundred. When a player's biggest question is his presence rather than his performance, you do not write three thousand words about the performance.

And the third point, the one that nags most: A-team hundreds are the most-read and least-understood numbers in Indian cricket. They look exciting because they have three digits and they are hollow because they travel without conditions, opposition strength, or the state of the innings. That is my actual conclusion, and it is a negative one. From this match I cannot say anything reliable about either batter's future beyond the fact that each played one substantial innings, and that innings means different things in each man's file.

I publish null results. On the day the official version holds up, I publish that too. Here the official version — a draw, two hundreds — held up. My excavation found no cover-up, only an incomplete file. Turning that into a scandal would be the real lie.

What to watch next

The third match of the series, whenever it comes, will bring three questions and all three run straight back to this one.

First, does Rathod repeat it. If he does, I will have a trend for the first time and I will write the big piece, even if it means cold-calling my way to a corner of a board tour page. If he does not, this stays a good innings, which is not a bad thing — not every good innings is a story, and assuming every good innings is one is the oldest disease in our cricket writing.

Second, does Jaiswal play the next game. If he does, this is not about performance but about planning, and I will ask about the planning. If he does not, this hundred belongs in a different file than the one labelled consecutive hundreds.

Third, will I get a scorecard this time. It is the smallest question and probably the most important, because until we start keeping A-team cricket's books, everything we say about young players will fall into two categories: myth and guesswork. Both are expensive.

In my notebook, the page for this match has three lines on it. Three lines, two hundreds, one draw. I left the rest of the page deliberately blank. That blank space is, for now, the most honest report on this match that exists.