A sharp deep catch can be worth far more than a simple wicket—especially when it removes a batter at the exact moment an innings is about to start costing the chasing side. Sarfaraz Khan’s catch to dismiss Naman Dhir did precisely that for Chennai Super Kings, taking Mumbai Indians’ most dangerous set batter out when the match was poised to flip into a high-scoring finish.
Dismissal that arrived at the turning point
Naman Dhir was on 57 off 36 when he was dismissed in the 17th over. Before his departure, MI were sitting at 134/4 with 20 legal balls still remaining. The impact of the wicket went beyond ending a half-century knock; it removed the batter who was best placed to accelerate through the final phase and push CSK’s chase target into a more threatening range.
How the catch carried a “base value” of its own
In the base impact layer, Sarfaraz’s catch was valued at ₹18.28 lakh purely for what the dismissal represented in isolation. That figure reflects the direct fielding contribution—who was removed, how the wicket came at that particular stage, and the match state in which the innings was disrupted.
- Direct fielding value of the dismissal: ₹18.28 lakh
- It accounted for the batter’s removal, the timing of the wicket, and the situation in which MI’s innings was broken
The bigger swing: what the wicket stopped from happening
The catch’s larger value came from what it prevented. Naman was dismissed at a moment when T20 batting value typically accelerates. He had already faced 36 balls, moved past fifty, and settled into the rhythm. With 20 balls left, MI needed him to finish the job.
This distinction matters in T20 cricket. A fresh batter arriving in the 17th over generally has to take risks immediately. In contrast, a set batter can pick and choose—deciding which bowler to target, identifying the scoring areas, and having the confidence to turn a good ball into two. That control is exactly why batters who are set become so expensive at the death.
A base projection from that point—using an exclusive model—suggested Naman Dhir would have ended around 79 off 47 if he had stayed through the final stretch. In other words, CSK could have avoided roughly 22 extra runs from a batter already operating with scoring control.
- Projected finish if Dhir stayed: ~79 off 47
- Estimated avoided damage: roughly 22 runs
Those 22 runs would not have been “ordinary” additions. They would have come in the closing overs, when every boundary changes the structure of the innings—potentially shifting CSK’s chase tempo, increasing pressure on the top order, and reducing the room for recovery if early wickets fell.
Under the same base projection, the value of that avoided damage was estimated at ₹80.48 lakh. When this is added to the catch’s direct base value of ₹18.28 lakh, Sarfaraz’s fielding moment rises to ₹98.76 lakh in expanded base value.
That combined figure is why the catch lands extremely close to the ₹1 crore mark.
Why the timing altered the value so dramatically
The catch was worth so much because of the phase it arrived in. A wicket in the 17th over of a set batter affects both the score in front of you and the projected finish of the innings.
With MI on 134/4, they still had wickets to attack and enough balls for a set batter to reshape the final total. Naman was that batter. His dismissal forced MI to continue without the player most capable of controlling the last few deliveries.
- MI were 134/4 when Dhir was removed
- They still had wickets and 20 legal balls left
- The dismissal denied MI their most effective option for controlling the final phase
For CSK, the catch was therefore more than a fielding effort. It functioned as a run-saver, a pressure-saver, and—within the author’s base impact model—an almost ₹1 crore intervention. Sarfaraz Khan didn’t just complete a dismissal; he cut off MI’s most valuable death-overs option before it could reach its full potential.