Yash Dhull's 104*: How Delhi's First-Innings Lead, Not the Fourth-Day Chase, Decided a Ranji Draw Against Services

Last weekend, when the Ranji Trophy Elite Group match between Delhi and Services entered its final hour just before tea, there was an odd quiet on the field. Services had declared their second innings at 397/9, Delhi needed 320, roughly 38 overs remained, and the wire headline had already been written: "Yash Dhull's ton earns Delhi a draw." I did what I have done for forty-seven years — I read the scorecard before the headline. Delhi finished at 168/4 in 38 overs, never threatening from 119/4, and the real story was which innings had secured Delhi's three points — and it was not the fourth-day chase.

To understand this, one must remember the Ranji points mechanism, because in domestic first-class cricket the logic of a Test match becomes an administrative rule. In Elite group league fixtures, a side that takes a first-innings lead is awarded three points even if the match ends in a draw — and that is the mechanism that had already decided this match's material outcome before the fourth-day chase was even proposed. Services entered with one point; Delhi's three points were banked well before the last ball; and declaring at 397/9 to set 320 meant Services put their second-innings platform at risk while nominally opening a "theoretical" win path, but in practice drawing a wall of draw around themselves.

The technical side of Services' strategy is not uninteresting. Rajat Paliwal made twin centuries in this match — a commanding first-innings contribution that laid the foundation, and then 116 in the second innings when the declaration clock demanded a big innings, repeating that foundation. Mohit Ahlawat's 142 carried the second innings to 397/9, the largest contribution to the declared total. Scoring two centuries in a single first-class match is an elite marker, because it requires both a first-innings platform and the temperament to repeat under the psychological pressure of a declaration. Under Paliwal, Services played patience cricket; they built a big score, but on the final day chose defensive bowling rather than aggression. That is the moment the fourth-day chase became a cosmetic exercise — the target was large for the result, but everything for the points had already been settled.

Yash Dhull's innings must be placed in the correct context. He made 104 not out off 104 balls, with 11 fours and 2 sixes, meaning 56 of his 104 runs came in boundaries. Any old reporter knows that a century at a strike rate of 100 in first-class cricket is not slow but brisk — a ton in roughly 102 balls, and that too when Delhi had collapsed to 119/4. That was the moment a young batter demonstrated not only technique but mental stability: staying at the crease, holding one end, and remaining unbeaten until the handshake. For me this is not a fraud but an honest rearguard. In patriarchal structures, when a young player comes under pressure, we often measure him only in numbers; but the journey from 119/4 to 168/4, where not a single wicket fell in 38 overs until the final handshake, shows that Dhull understood the rhythm of the match. His innings saved Delhi from defeat, but it is also true that Delhi never moved toward victory.

Now comes the part the headline hid. Sumit Mathur's 99 — the true foundation of Delhi's first-innings lead — was one of the most important contributions of this match, yet it was buried beneath Dhull's 104*. This is not merely a flaw in cricket reporting but a larger structural habit: we often headline the player with the bigger brand, even if his contribution is smaller than the match's decisive turn. Dhull is a former India U-19 World Cup-winning captain, and the media has a natural incentive to amplify him. But when I remember those days twenty years ago when I wrote about Hansie Cronje and Azharuddin, I recall that the winter they handcuffed the heroes, the stadium kept its mouth shut — and so did the press. Today too, when a young star plays a good innings, the narrative frame is ready-made. This is the same page of my notebook where I record the moments the cameras cut away from — the bench, the lobby, the empty chair. In this match, that empty chair belongs to Sumit Mathur's 99.

The second big fact of this match, which appeared in the report in only one line, is the season's calendar. Ranji Trophy now pauses, teams head to the Syed Mushtaq Ali Trophy — the domestic T20 tournament — and Ranji resumes in January. This calendar architecture gives this match's points a "deferred" significance: the group table will be re-read after the T20 interlude, and only then will the cost of this draw become clear. For me this is the same old thing I have written about for years — every transfer window is a confessional; the numbers say what the heart will not. Ranji has no transfer window, but the calendar swap does the same work: it tells the farmer when to sow and when to reap. For a young player like Dhull, this switch is both risk and opportunity — the red-ball rhythm can break, but the white-ball stage can also open.

The bitter truth about Delhi's team construction is that their batting rests mainly on limited-overs power hitters — Priyansh Arya, Ayush Badoni, and Dhull himself from a T20 background. This is the structural tension that troubles Delhi every season: a T20-nurtured batting unit is tested in the red-ball points race, where patience and first-innings lead matter more than explosiveness. In this match, Delhi's "explosive" batters made 168/4 in 38 overs, showing they were playing to avoid defeat, not to win. This is not a talent deficit but a format-fit question. Services, on the other hand, adopted a strategy of veteran accumulation, with Paliwal anchoring both innings. This is the classic first-class strategy of taking a first-innings lead and then heading for a draw — what I call the "half-baked cake": golden on top, raw inside.

But here I want to take a contrarian view. We often treat a draw as a "negative result," especially when a young star scores a century and the team does not win. But in this match Delhi's three points came from the first-innings lead, and that lead was built by Mathur's 99 and Dhull's first-innings contribution — not by the fourth-day chase. If you look at the match through its points mechanism, Delhi got what it wanted: the first-innings lead and three points. The 320 chase on the fourth day was a drama that neither Services nor Delhi truly wanted. Services were on one point and needed a win, yet they did not risk declaring earlier than 397/9 — a "have your cake and eat it" mentality. This is not an administrative failure but its logical outcome: when the rule rewards the first innings, teams play for the first innings, not for the result. I remembered that day eleven years ago when Andrew Symonds was bought for $1.35 million at the IPL auction and my city's franchise finished eighth of eight — even then the numbers said what the heart would not. Ranji's points system is the same: it tells the farmer when to sow, even if the spectator wants something else.

Now that Ranji is paused until January, this century leaves a question for Dhull. It was his first century of the season, which means several of his earlier fifties may not have converted. Is this innings a sign of "return to form," or merely a rearguard played under pressure? The answer will come in February-March, when Ranji resumes and players return after the T20 interlude. A line was added to my notebook today — the moment Dhull changed the score off the 104th ball and only one sound echoed in the stadium, because no one knew whether this was the start of a win or the pause of a draw. Services and Delhi both got what they asked for — three and one points — but the truth is that if this fourth day had to be described in one word, it is "settlement," not "struggle." And the best cricket stories always live in the pause before the whistle — this time that pause was 38 overs long.