Dew, a Dropped Catch and 17 Balls to Spare: What Kusal Mendis' 87* at Rawalpindi Actually Proves

At Rawalpindi, the fourteenth over of the first innings ended with the board reading 102/6. A few overs earlier the picture had been the exact opposite: Pakistan 34/0 in three overs, no wicket lost, Fakhar Zaman and Maaz Sadaqat middling the ball. A side that starts a powerplay like that is normally expected to post something past two hundred. Instead, a mesh of slower balls and googlies strangled Pakistan's middle order, the target settled at 169, and the chase was finished with an over to spare.

My long habit is to keep the scorecard beside me before I read a match report's headline, checking which over each wicket fell in, off whose bowling, and under what conditions. The headline tells us this was a consolatory win; it never tells us whose consolation it really was. Was this defeat meaningless for a Pakistan side that had already sealed the series 2-1, or did it hide a signal that will cost them later?

Kusal Mendis' unbeaten 87 off 48 balls, and Sri Lanka's 172/2 inside 17.1 overs, is the story everyone knows. A match result and the true worth of an innings are never written on the same page. Here I want to read twice: how genuine that innings was under the dew, and how meaningless Pakistan's defeat really was.

The fixture was the third and final T20I of a bilateral series already decided. In cricket's language this is a dead rubber, a match whose result cannot change the series. Pakistan had taken the first two games; both sides used the last one to test combinations. The question is who used that opportunity better.

The venue, Rawalpindi, is historically a good batting surface with pace and bounce, friendly to stroke-play. The pattern here is familiar: big first-innings scores, then evening dew that makes second-innings batting far easier. Dew means the ball reaches the bat more slowly, grips less, and skids on.

ICC bilateral playing conditions carry no direct clause on dew, a familiar gap in the rules. Dew creates an asymmetry between the two innings, and the laws offer no clean remedy. The side winning the toss usually prefers to bat first here, hoping to exploit dew later. Pakistan won the toss and chose to bat, so Sri Lanka sent them in. On the surface the coin favoured Pakistan; the result said otherwise.

Pakistan were 34/0 in three overs. That number matters, because teams attack during the fielding restrictions, scoring quickly even while losing wickets. Pakistan were doing both. Then came Eshan Malinga's over, a double-wicket maiden. A maiden means no runs; add two wickets. Fakhar Zaman was caught at cover off the first ball, and Maaz Sadaqat fell for a duck three balls later. A wicket-maiden in a T20 powerplay is a rare event, and it is the match's first turning point, because it does not merely cut the score but shakes the confidence at the base of the batting order.

The match was really decided in the middle overs. Pakistan fell from 34/0 to 102/6, roughly 68 runs for six wickets. At the centre was Dasun Shanaka, who returned 3/21, his weapon the slower ball. Shanaka removed Nafay, Randhawa and Abdul Samad in consecutive overs with disguised off-pace deliveries. Pakistan's middle order can play pace, but its timing tends to break against a change of pace.

Viyaskanth's googly, which dismissed Hasan Nawaz, added another layer. Playing his first game of the series, he gave the spin attack a new dimension. Both sides were rotating names, so these performances carry value beyond a single match. Sri Lanka's plan was clear: use slower balls and googlies to pull Pakistan's middle order outside its natural game. The key was never the powerplay; it was control of the middle overs.

Sahibzada Farhan rescued Pakistan with 76, his third straight fifty, and took the Player of the Series award. His 66-run stand with Arafat Minhas off 37 balls, and 48 runs off overs 17 to 19, carried Pakistan to 168. Three consecutive fifties is a multi-match signal, not a fluke. That consistency is the series' most durable individual story, whatever the headlines say.

Minhas contributed on both fronts: 34* off 20, and 1/26 with the ball. A rescue innings from No. 8 signals squad depth, but a single match is not enough to turn that into an established conclusion.

Pakistan's pace attack, through Mirza and Razaullah, leaked runs at the death; conceding 172/2 in 17.1 overs is close to ten an over. Thushara's yorker to Razaullah was the classic death weapon, pinning the batter at his feet.

In the second innings the target was 169, dew was settling, and Sri Lanka's openers had time. Kusal Mendis made 87* off 48, a strike rate near 181 (derived, pending verification), reaching fifty off 33 balls and finishing unbeaten. His innings was high quality but not flawless: he was dropped on 64 by Sufyan Moqim off his own bowling, so a large share of the final 23 runs came from the opponent's error.

Kamindu Mendis finished 40* in an unbroken 98-run stand off 55 balls, suggesting Sri Lanka built the chase on stability rather than risk. They finished 172/2 in 17.1 overs, 17 balls to spare, a comfortable win with only two wickets lost. I read the innings twice. The first reading was a flawless chase; the second, adding dew and the drop, changed the arithmetic.

Chasing 169 on a dew-affected surface is structurally easier, so Kusal's strike rate cannot be read as final proof of form until it repeats in dry conditions. A scoreboard in T20 never records ball speed, grip or dew, so 172/2 flatters without the context. We package effort metrics as proof of quality, yet a run made under helpful conditions is like a pretty distance-covered number: impressive on the page, incomplete in meaning.

My referee's-eye method checks the incident log, the decision-maker's position and the exact protocol before commenting. This match carried no DRS controversy, no rain and no DLS, so the governance question sits inside the game: is the dew-driven asymmetry part of fair competition, or a scheduling shortfall? All figures here come from preliminary match data whose sourcing remains unverified, and the derived strike rates and economies must be cross-checked against official scorecards.

Read twice, the word consolatory changes meaning. The first reading is Sri Lanka's fight; the second is Pakistan's middle-order leak, with Farhan's three fifties acting as a lid over a collapse to 102/6. The Kusal hype should be tempered: this was a dew-assisted innings, not yet proof of repeatable form. Media framing will be asymmetric, with Sri Lanka amplifying depth and Pakistan calling it meaningless. Rotation on both sides points to a workload-management window, where load management is often a polite name for accommodating a packed calendar.

A single dead rubber cannot fix the series' true balance. Keep tracking five signals: Kusal's strike rate over the next five T20Is, Pakistan's No. 4 to 6 output, Farhan's conversion from fifties to match-winning scores, the toss-versus-dew relationship at Rawalpindi, and the retention of new names like Minhas and Malinga. The match is over; the arithmetic is not. If Kusal repeats this on a dry pitch and Pakistan's middle order collapses again, that night at Rawalpindi was not a consolatory win but an early warning.