Palam's Scorecard, Paliwal's Hundred, and the Nine-For That Missed the Headline

The sheet that came out of the scorer's cabin at the Air Force ground in Palam carried two lines side by side: Services bowled out for 266, and Rajat Paliwal unbeaten on 111. Those two sentences cannot sit in the same room. The copy reached me in London at twenty to seven in the evening, with no date line and no link to a scorecard. In forty-five years I have seen many scorecard errors — a surname where a first name should be, runs where overs should be — but rarely an error that contradicts itself inside a single paragraph.

I was not at Palam that day, and there is no shame in writing that plainly. I spoke to the local scorer who prepared the sheet, and to a colleague in the Delhi press box who had been staring at the same slip for hours. Both agreed on one thing: Paliwal walked back unbeaten. Nobody added up the team total, because on deadline nobody was there to add it up. This is where cricket reporting's oldest habit does its work — we treat a number as true because it has been printed, not because it has been reconciled. The first task in this piece is therefore the least glamorous one: do not present as settled what is not settled.

The corridor keeps what the scoreboard forgets. And the Palam corridor that evening was complaining about a slow pitch. The strip at the Air Force ground is a slow turner — the ball changes direction before it reaches the batter, but slowly enough that a spinner has to be a carpenter rather than a magician. On such a surface the most valuable currency is not speed but patience. On a slow turner a spinner's biggest weapon is not the wicket, it is the over — the bowler who repeats the same length in his twentieth over forces the mistake out of the batter instead of manufacturing it himself.

Which is why the day's first truth is that Services were 158 for 7 at one stage. Seven down for a hundred and fifty-eight means the top order had already gone home and the visiting side was sitting on a keel. That keel is called Rajat Paliwal — thirty-five years old, 110 first-class matches, captain. The batter who comes in as the rescue act after the seventh wicket is often a team's best news and worst news at once. Good news because tomorrow was saved; bad news because six wickets had already fallen, and the men who should have saved them were sitting somewhere else in the order.

Put Paliwal's numbers in their proper place. A thirty-five-year-old with 110 first-class matches is not a team's structure; he is the team's walking stick — fine while the support lasts. His hundred was the most valuable innings of the day, but it is not a health certificate for Services' batting. A side that looks to its thirty-five-year-old captain at the fall of the seventh wicket will spend its next two seasons praying that the same man stays fit. That is not a prophecy, it is arithmetic on a structure.

Now the day's second truth, which made the headline but was only half told. Aman Chaudhary, a twenty-one-year-old left-arm spinner, bowled 31 overs and took 4 for 79. An economy of 2.55 is a very high standard of control in first-class cricket. A strike rate of 46.5 balls per wicket is good, not dominant. The distinction matters: control says the bowler was letting nothing be built; strike rate says how much he was building himself. On Palam's slow surface the first quality was worth more than the second, which is why the four wickets do not surprise me — what surprises me is that a young spinner was trusted with thirty-one overs.

That is the detail the outside world does not see. This was Chaudhary's second first-class match. Bowling 31 overs in your second first-class match is a document of performance and a document of workload at the same time. Read the 31 overs twice — once as the captain's trust, once as the load on a body that has played two first-class games. Labels like "trump card" sound lovely after one spell and are forgotten by the fourth match. The question worth asking is the dull one: what does this bowler do on the day the pitch does not turn?

On another ground the same day, something happened that was compressed into a single paragraph of that copy. In an Elite Group A fixture, Madhya Pradesh won the toss, chose to bat, and were bowled out for 209 in 66.1 overs. Harsh Dubey took 9 for 53 — nine wickets in an innings. By stumps the hosts were 56 for 4, and fourteen wickets had fallen in the day. A nine-for is the kind of event a first-class season produces once. His economy is not recorded, his overs are not recorded, his career average is not recorded — and the day's rarest feat sat at the bottom of the page while a hundred and a four-wicket haul sat at the top.

It must be said that the Delhi lens was not wrong, it was simply Delhi's. A city paper will put its own ground's match on top; that is the ordinary economy of the trade. But the reader is entitled to know that on the day he was handed 111 not out, nine wickets fell somewhere else. The crowd files the headline; I file the sound underneath it. And the sound underneath was saying that the rarest performance of the day did not happen in Delhi.

Keep some restraint about Dubey too. An innings average of 5.89 tells you about the spell, not the career. The question after a nine-for is not a statistical one but a selection one: what is his base wicket-taking rate? If he takes three wickets in each of the next three games, the nine-for was an accident. If he takes four or five every week, it was a story we disposed of in a paragraph.

There is one more blind spot in Madhya Pradesh's 209. Two hundred and nine in 66.1 overs, with fourteen wickets on the day, tells you the pitch was with the bowlers. "Madhya Pradesh collapsed" is easy to write, but on a day when fourteen wickets fall, look at the pitch before you convict the batters. The hosts being 56 for 4 is the corroborating witness. In a match that gives you fourteen wickets on day one, the big question the next morning is not who wins — it is whether anyone can make a hundred and fifty in the fourth innings at all.

Paliwal said one thing that evening which is bigger than the match — that players prioritise T20 cricket. He named nobody and pointed no finger; he described a market. The Ranji Trophy's real problem is not that players choose T20; it is that we have never once placed Ranji in competition with that market. On one side, a life that can change in two months; on the other, four months of train travel and the hope of a Test berth. Economic logic is hard to beat with moral instruction, and the columnist who tries is usually filling his own space rather than explaining cricket.

The other side of that argument is Ayush Badoni, whose consecutive double centuries are evidence that the domestic red-ball reservoir is not empty. Badoni is known as a T20 player; two Ranji double hundreds disturb that label. One number cannot substitute for a policy, but it shows that people play when given the chance — the question is who hands out the chance, and on what basis.

Now the easiest reading of all, which is also where the mistake lives. The day will be written as: a veteran captain's rescue hundred, a young left-arm spinner's four wickets, Delhi's day. That is comfortable and it is wrong at the edges. Delhi's advantage that day was conditions, not quality — a slow turner and a spinner given thirty-one overs. Conditions change; a fourth-day pitch and the wind on another ground behave differently. A side that reads its wins off the pitch loses to the same pitch next week.

The second mistake is the suggestion that the surface will break up further. It might, but that is a forecast, not a recorded fact. And if it does break up, the benefit is not Delhi's alone — a fourth-innings chase of 150 becomes just as awkward. Drawing a result from day one is the very habit that lets us miss the real Ranji stories for four months at a stretch.

You learn the beat by standing still while the room moves. I learned that outside Edgbaston in 2026, standing there for two hours after a scoreline of 213 for 213 had sent the losing side into a dressing room — the board said tie, the room said something else entirely. Twenty-seven years on the same habit applies: there are two lines on the Palam sheet, and I will not reconcile them until the official scorecard arrives.

What to watch next is plain. First, the Services total — 266 all out or 266 for 7 changes the whole reading of the day. Second, Chaudhary's next spell — can he bowl thirty overs on a pitch that does not turn? Third, Dubey's season aggregate — after nine wickets, the real question is his base rate. Fourth, Paliwal's body — 111 not out at thirty-five looks beautiful, but Services' entire season rests on that one joint.

The locker room tells you the truth two days before the press conference does. That evening's locker room held a thirty-five-year-old who saved the team, a twenty-one-year-old who bowled thirty-one overs, and a bowler whose nine wickets went to another page. Which of those three becomes the face of Indian cricket in two years will not be decided by the scoreboard. It will be decided by who is standing in the physio's queue at twenty to eight the next morning.