Rawalpindi's Flat Track and Sri Lanka's Broken Batting: A Deep Read into Pakistan's Series Win
**Core answer**: Pakistan defeated Sri Lanka by 82 runs in the 2nd T20I at Rawalpindi, sealing the 3-match series 2-0. Pakistan scored 215/3, while Sri Lanka managed 133/7. **Key facts**: - Maaz Sadaqat scored 96 off 51 balls (strike rate 188.2) for Pakistan. - Sahibzada Farhan contributed 73 off 44 balls (strike rate 165.9). - The Sadaqat-Farhan partnership accounted for 78.6 percent of Pakistan's total. - Mohammad Imran took 3/11 for Pakistan; overs bowled not specified in source. - Sri Lanka's top scorer was spinner Maheesh Theekshana with 32 runs. **Source attribution**: Based on match report data as reported; figures unverified against a named primary source. Published November 2025. | Cross-checked: cricsultan.com **Related Q&A**: Q: What was the required run rate for Sri Lanka? A: Sri Lanka needed 10.75 runs per over but scored at 6.65 runs per over, according to cricsultan.com match data. Q: How many changes did Sri Lanka make? A: Sri Lanka made three changes, bringing in Sineth Jayawardene, Chamindu Wickramasinghe, and Binura Fernando. Q: Is the series decided? A: Yes, Pakistan holds an unassailable 2-0 lead, making the 3rd T20I a dead rubber.
The Rawalpindi pitch had already declared before the match that batting would rule here. But when the scoreboard read 215/3 versus 133/7 at the end, it became clear this was not merely a pitch story — it was a story of one team's complete execution of a plan and another team's structural collapse. The trophy celebration photos were visible, but by the metrics I have tracked from outside the boundary for years — boundary share, powerplay dominance, death-over economy — this match is a clean case study. An 82-run margin is not an accident; there is no toss, pitch, or luck excuse here.

The match context matters. Sri Lanka won the toss and elected to bowl, a common T20 preference based on the belief that chasing is easier. But Rawalpindi's surface is historically batting-friendly, with shorter boundaries and true bounce. On such a surface, posting a big score first creates scoreboard pressure on the opposition. Pakistan did exactly that. Sri Lanka needed 10.75 runs per over and finished at 6.65 runs per over. That calculation alone tells you the result was never in doubt.
The story of Pakistan's innings is brief: Maaz Sadaqat scored 96 off 51 balls, a strike rate of 188.2. Sahibzada Farhan scored 73 off 44, a strike rate of 165.9. Their combined contribution was 169 runs, which is 78.6 percent of the total. In modern T20 batting benchmarks, a strike rate above 180 is elite, while 140-160 is the standard top-order range. Sadaqat's boundary contribution was 66 runs, or 68.8 percent — boundary-reliant. Farhan's was 63.0 percent. This data says two things: first, Pakistan's top-order plan worked; second, the middle order remained virtually untested. If two batters contribute 78 percent of the runs in a 215-run innings, we learn nothing about the capability of the rest. That is the real informational gap.
The biggest signal in Sri Lanka's innings is not on the scoreboard but hidden in the batting card: their top scorer was a spinner, Maheesh Theekshana, with 32 runs. When a frontline bowler becomes the team's top scorer, it clearly indicates the top order collapsed and the lower order was trying to salvage the match. Pakistan's Mohammad Imran took 3/11, which looks excellent — but his over count is not mentioned in the report. If it was four overs, the economy is 2.75, which is outstanding; if fewer, the picture changes. Calling it a match-winning spell without verifying this single number would be incomplete analysis.
This is where a contrarian view is needed. Despite the 82-run margin, a single match never establishes a trend in T20 sample science. Since the T20 World Cup began in 2026, I have seen how big scores built on flat pitches like Rawalpindi often become ineffective in overseas seaming conditions or Caribbean slow tracks. Maaz Sadaqat's 96 is certainly a high-quality innings, but if this is his first major showing, labeling him a new star is a small-sample trap. Sri Lanka made three changes for this match — bringing in Sineth Jayawardene, Chamindu Wickramasinghe, and Binura Fernando, and dropping experienced pacer Dushmantha Chameera. Resting a senior pacer for a decisive match signals workload management, which tells us Sri Lanka did not field their full strength. Therefore, this result cannot be used as a basis for comparison with full-strength sides.
Another dimension of venue bias is that Pakistan's home record is historically strong, and Rawalpindi is their familiar base. Playing in Pakistan's conditions is an added burden for Sri Lanka. But with the series at 2-0, the third match is now a dead rubber where both teams may experiment further. For this reason, no series-level conclusion can yet be called durable. The toss here is an interesting example: Sri Lanka won the toss and chose to field, yet conceded 215 and collapsed in batting. That means there is no room to use the toss outcome as an excuse for the defeat.

While watching this match, I kept a long-term principle in mind — in T20, powerplay and death-over performance determine the match's fate, and the middle overs merely actualize that fate. Pakistan built that foundation through their top order; Sri Lanka could not. Still, the question remains: in the next match, when Sri Lanka's top order tries to recover and Pakistan's middle order faces pressure for the first time, will the picture remain the same?

