Ranji Trophy: Delhi vs Services — The Real Story Isn't the 78, It's the 144

The scoreboard at stumps on Day 2 read 299/6. Ayush Doseja had made 78. Mayank Mathur was unbeaten on 80. The headlines framed it as Doseja's "return to form" — a half-century after six barren innings. I turned the scorecard over three times and found a number nobody had put in a headline: the sixth-wicket stand was worth 144. Which means when Doseja was dropped on 42, the score was 135/5; by the time he fell for 78, it was 279/6. Thirty-six of his runs lived in the shadow of a partnership that never got named in the copy. This piece starts from that gap in the scorecard. Because the real question isn't whether Doseja made 78. It's who bought him the chance to get there, when, and how.

Context: Delhi's innings, Services' squeeze, and the mystery of three points

Services made 266 in their first innings. Delhi began their reply needing 267, and by the close of Day 2 were sitting on 299/6. The first-innings lead had been secured — under Ranji Trophy rules, that lead is worth three points, and once the score crossed 267 those three points were in Delhi's pocket. Doseja later said it himself: "We had already taken three points." But the original report never explained that rule. A reader unfamiliar with Ranji's points system will stall at the phrase. Rewind the tape — the rule gets mentioned once in commentary and then forgotten.

On the pitch, all I can say is that the ball was a touch slower on the second morning — the early-session bounce Jayant Goyat found had disappeared by midday. Pulkit Narang's left-arm spin extracted the most turn in the final session, when both Doseja and Mathur were set. That was the same session in which Delhi lost no wicket until they lost one right before stumps. That phrase "almost went through the final session without further damage" points to that final ball, or that final over, which the report never expanded on.

Core: the 144, the orphaned 80*, and the bowlers' real numbers

*The biggest missing piece is the 144-run sixth-wicket stand — Doseja (78) at one end, Mathur (80) at the other.** At 135/5 Delhi were in trouble: captain Ayush Badoni had gone for 7, Anuj Rawat for a first-ball duck. What the team needed at that moment was not just a lead but a lead large enough to force Services to bat again. A 26-year-old and a relatively unheralded partner put on 144 by doing what never makes the highlight package: keeping the run rate near three-and-a-half, never letting the bowlers settle into two consecutive maidens, and playing two or three shots that were counter-punches, not defences.

A fourth number hides inside that stand. Services' bowling figures: Arjun Sharma 2/48 (left-arm spin), Goyat 2/51. Two frontline bowlers took four wickets for 99 — an average of 24.75. They got wickets, but they rarely got two consecutive overs of dominance. That's the difference between "the bowler bowled well" and "the bowler won the match." The 144-run stand is the answer to which of those it was.

Mathur's 80* is the second truncated story. Eighty not out — and one sentence about him. Ten paragraphs about Doseja's 78. That's the selection bias: the headline subject is the one who makes the tape. But the truth of a Ranji scorecard is that if Mathur had gone at 40, Doseja's 78 would have meant nothing. The second end of a partnership always gets written up less than the first — that's a habit of the copy desk, not the broadcast.

To understand Doseja's 78 you also need the preparation story, and here's a technical detail that attaches to the result. Three months of red-ball training at the National Cricket Academy in Bengaluru (now the Centre of Excellence), under Wasim Jaffer and Hrishikesh Kanitkar. For a batter, three months of red-ball preparation means one thing: recalibrating the art of leaving. Doseja himself said he felt he was batting well and was getting unlucky dismissals — four innings of starts without a half-century. That isn't lost form. It's a conversion crisis: the bridge from start to big score.

Last season's 949 Ranji runs (950 in his own words) is the number that proves his ceiling; a half-century doesn't test it. Four blank innings is statistical noise, not crisis. The real fruit of that Bengaluru training will show not in the 78 but in the shots he left alone — against Bengal last time (Shami, Mukesh Kumar, Akash Deep) he made 45 in the first innings, having been dropped twice. Doseja's problem was never talent. It was conversion — and 78 is the first, incomplete answer.

Contrarian: the "regains touch" headline and the arithmetic of the scorecard

The original report's headline said Doseja had "regained touch." But a sentence in the same piece says he had gone four innings without a half-century "despite getting starts and looking in touch." So where had the form gone? The headline declared a crisis that didn't exist. The real story isn't "return from crisis" — it's "reaching big scores from small ones." That's the difference a copy desk often misses, because "regains touch" has drama and "conversion" only has facts.

Second reversal: he was dropped on 42. Pulkit Narang put down a catch, and he added 36 more. The report wrote "dropped on 42 and went on to score 78" — as if the entire 36-run ledger must be settled against that one miss. That's not arithmetic, it's a rope trick. A dropped catch is not a fixed interest rate. The honest question is: how much of Services' dominance did the miss prevent before that moment? The report goes quiet. If Services had created two chances in that 144-run stand and held both, the drop on 42 would have been one more "almost" — and "almost" belongs to outcomes, not character.

Third reversal: this story isn't about one player's comeback. It's about the completeness of Delhi's first innings — and the original report disposed of its forward half (declaration timing, the chance of an outright win by trapping Services in their second innings) in one dry line. At stumps on Day 2 Delhi are 299/6, leading by 33, three points secure. Day 3's question: how many more will Delhi add before declaring, and can Services' second innings hold? If Services bat four sessions, Doseja's 78 and Mathur's 80* will mean nothing. If Delhi force an outright win, this report becomes a "turning point" piece — but no report before Day 3 knows which day becomes the hinge. The tape taught me this: a stumps score is the future's story, not the past's.

My experience: one lesson from three decades of reels

In the winter of 2026 I was at the Wankhede for the Ranji final — Mumbai vs Bengal. At tea on Day 3 there were 1,847 people in the Garware Pavilion. Wasim Jaffer batted an entire session as if the fielders around the wicket were unnecessary. Amol Muzumdar argued with himself between deliveries. I filed 900 words, mentioning the score twice. My editor ran it on page 22 and said it was the best thing I'd written.

That day I learned: the real story often sits in the space between the big names, the big scores, the big headlines. In this match that space is the 144-run stand, and its second end — Mathur's 80* — which stayed out of the copy. If the original report had centred the partnership instead of Doseja, Ranji's new generation would have got a story that connected to their own game, not to a star's form.

Toward what comes next, not a summary

When the umpires walk out of the dressing room on the third morning, the real question is when Delhi declares — and whether Services' batters can hold under the pressure of those 33 runs in their second innings. If Services bat past 250, Doseja's 78 won't be remembered — and this report will live on with that "return to form" that nobody keeps two days later.

I'll run the tape again — this time only for the first hour of Day 3. Because the real story won't be in ESPN's package. It'll hide in some corner around Mathur's hundredth ball, where the camera never goes, and where the scoreboard hasn't arrived yet.