Day Three at Palam: Services' 200-Run Patience, Ahlawat's Unfinished Navy Revenge, and the Open Book of Delhi's Bowling

I kept the scorebook on that bus for eleven hours; the numbers never lied. On Monday afternoon, walking toward the Nehru Stadium at Palam, my pocket held only an old notebook and, inside it, one number written three days earlier — 344. Delhi's first-innings total. Anybody could look at that number and say Services were under pressure. But when I reached the figure written beneath it — 202 — I felt this match had changed not its direction but its entire character. The Day 3 scorecard belonged to Services: 280 for 5, a lead of 202. On the third afternoon of a four-day Ranji fixture, that state is not neutral for either side; it is a statement in itself. In my years on the circuit I have seen many Ranji innings turn at exactly this corner — where a 200-run lead becomes 350 fifty overs later, and the batting order of the side that leads eats into the opposition's thinking rather than their own. If reading a scorebook on a bus has taught me anything, it is that a first-innings lead is not merely a number; it is the first draft of tomorrow's declaration date and time. The Palam pitch. First, this: there is no pitch report in the source. Not a word attributed to the curator, no clear signal of spin or seam. That is my first honesty — I do not comment on what I did not see. But this much is certain: Delhi made 344 in the first innings, so this was no green-top, seam-movement morning. In my experience Palam is often a ground where a fast bowler can land a big blow in one or two spells on a fresh morning pitch, but by the afternoon sun the shine is gone from the ball and the middle overs are flat. This is the ground where one large partnership decides the entire match. That partnership is Ahlawat and Chauhan. Services travelled from 50 for 2 to 280 for 5, roughly 230 runs put together at a time when the threat of the new ball had not fully passed. I do not have ball-by-ball detail of that phase, but when wickets stop falling for an entire middle session after an opening burst, the scorebook says the bowling's edge has been lost not in one over but in the plan. I give Delhi's bowling a new identity from this match: front-loaded attack, then a silence as open as a field. Saini struck in the morning, but after that, when the ball grew old and the pitch showed its real face, Delhi's bowling plan had no second route. This is common in Ranji cricket: if the fast bowler carries the bulk of the attack and the spinner's role is unclear, the middle overs become the longest of the day. Ahlawat's innings tells a different story from every angle. 142 runs off 150 balls, a strike rate of about 94.7. In red-ball cricket that figure is not normal. In the red-ball format such pace says only two things — either the batter is in rare touch and exploiting errors in the bowlers' lengths, or he has deliberately come out to seize the tempo of the match. In Mohit's case both appear true at once. He was batting at No. 4 because Dhankhar was ill — an emergency team-management decision that is itself a signal. When a batter is pushed up out of necessity and scores a century there, it says something about him, but even more about the team's depth. There is one entry in the scorebook worth reading across fifty overs: a hundred off 117 balls. Reaching 100 in that many deliveries is faster than the ordinary pace of Ranji hundreds, many of which take 150 to 250 balls. This does not mean the surface was flat or the bowling weak; it means Ahlawat took risks and was rewarded. But here is my second honesty: one innings does not establish a player. My notebook holds many names that, after one century, settled at an average of 25 across the next twenty innings. I have no season aggregate for Ahlawat, no home-away split, no pace-versus-spin data. So I do not write him down as 'the next big name'; I write him down as 'one large question, whose answer lies in the next six innings.' His career arc is itself an interesting document. A Ranji debut for Delhi in 2026 under Gambhir's captaincy, a move to the Navy as a petty officer in 2026, and now Services. This is not linear development; it is the story of a player who once fell off the system's radar and brought himself back. In my experience such players are mentally hardened, but their peak window is shorter because they get less time in the light. In an institutional side like Services this fits — age, discipline and patience are counted there as part of a batter's price. There is another layer to this innings that the media will easily miss. He was a Delhi player, went to the Navy, and now stands for Services against Delhi. If Services win this match, that story will write itself — 'Delhi let him go, the Navy shaped him, Services hit Delhi with a century.' But I am a record-keeper and I will not write it into the result of one match. I will record it as a narrative arc that is settled only after Day 4. On the other side, Jayant Goyat. A six-foot-four fast bowler from Bhiwani. Five wickets in the first innings — a maiden five-for. For me that is the second most important number of the match, but it carries a large warning: the source does not give his exact figures. Runs conceded, economy — unknown. And for a fast bowler economy matters as much as wickets. When Delhi reached 344, it is important to understand which part of the innings those five wickets came in. My estimate — and I will call it an estimate — is that the bulk came from the lower-middle order, not the top. Which means Goyat's value, for now, looks more like an impact/enforcer role than a new-ball spearhead. The Bhiwani reference is not idle. It is a well-known plant of Indian fast bowling, and the tall fast bowlers who come from there have a signature — bounce, a steep angle, and stubbornness. But a signature is not proof of quality. I have seen that workload management is the hardest task with tall quicks; five wickets at 21 or 22 is useless four seasons later if it comes at the cost of knees and back. In Goyat's case my eye will be on his spell management, not on this one five-for. One more thing: if his economy stays controlled while wickets keep falling, he will become not a one-off haul but a genuine product of the season. Now the part most often ignored — Sumit Mathur's 99. One run short. In the scorebook that is a single digit, but in a selector's eye it is a category. In Ranji cricket, converting the nineties into hundreds counts as much as the runs themselves. Mathur made 99 and laid the foundation of the first innings, but I will not place him in the category reserved for those who finish their hundreds. It may sound ruthless, but record-keeping is ruthless. Delhi's first innings of 344 rests on Mathur's 99 and Doseja's 78. It is worth noting that the lower order fell away despite 344. So Delhi's total does not exaggerate the strength of their batting; it is the fruit of two large partnerships. Such a team breaks more quickly under pressure in the second innings because there is no 'safe 344' behind them. The arithmetic is clear now. Roughly a day and a half remain and the lead is 202. A Services win and a draw are both alive. The probability of a Delhi win is very low. But here is a nuance the commentary box usually misses: a 202 lead with five wickets in hand means Services need not declare early. On a four-day pitch, declaring with a lead under 300 would be strategically immature. My first estimate is that Services will bat Delhi out of the game on the fourth morning, giving Delhi a target of 300-plus, and will use the time to let their tail bat too. This is the 'economy of patience' that institutional sides play, and which television commentary often dismisses as slow batting. From the other side, Delhi's biggest question is the psychological state of its batting, not its technique. 202 behind, a fourth-day pitch, and opposite them a side that keeps its bowling fully under control. Delhi has only one route — a big opening partnership. If the first two wickets fall early, this match will not run toward a draw but toward a Services win. I have seen many times that in a second innings under the pressure of 200-plus, the first hour of batting alone decides the whole result. Now the angle that is misread from outside. From outside the story will look like this: 'Services out-did Delhi, Ahlawat's comeback and Goyat's rise.' It is a beautiful story, but it rests on a dangerous frame — reading 280 for 5 as 'dominance'. My reading is different. Services put themselves in trouble at 50 for 2. This was not dominance; it was the art of escaping a crisis. The difference matters. A team that is 50 for 2 on the first day is not 'strong'; it is 'flexible'. Flexibility can win one match, but over a fourteen-match season this is the same team whose true score sits between 200 and 250 if its top-order problem is not fixed. A third side must be added here — the absence of pitch information. The source has no pitch report, no weather detail, no mention of the toss. If rain reaches the game on Day 4, the draw becomes the most likely result and Services' control becomes a matter of paper. I am not among those journalists who pronounce on a pitch without a pitch. What I saw, I wrote; what I did not see is blank. For me the biggest lesson of this match is larger than individual numbers. The patience of an institutional side like Services, the imbalance in the bowling plan of an old club like Delhi, and the power of one big partnership in Ranji cricket — these are three pages of the same scorebook. Delhi must ask itself a deep question before next season: after the new ball, who are their third and fourth bowlers? Services must ask their top order: why the repeated 50 for 2 start? And Ahlawat and Goyat must ask themselves: can the name built by one innings or one five-for be turned into six months of continuity? On the fourth morning, when Services come out to bat, my eye will be on the first ten overs — when do they stop? Do they show courage in the declaration, or stretch the lead to 320-330? That decision will express the entire economy of four-day Ranji cricket. And if I am wrong, the scorebook will correct me — as it always does. One run is not a small thing; it is the whole arithmetic of a season. Today Services do not have Mathur's 99, but they have 202 — and 202 is greater than 99. Until the next page of the scorebook opens, that is the truth.