Dust of Rawalpindi, Dropped Catches and a Ninety-Six: The Truth Buried Under Pakistan's Record Win

A small scene near the dustbin at Rawalpindi Cricket Stadium stuck in my mind. The match was over, Pakistan had won by 82 runs, but in a corner of the stands, an old man was still sitting, an old scorebook in his hand. He wasn't writing scores—just turning pages. I thought, perhaps this scorebook is the real match report. Because what the TV screen showed—215/3, an 82-run win, a 96-run innings—that is the door of the match. But the real story of the match lives in the hallway, where three dropped catches, a flat pitch, and a young batter dropped on 44 are written down. This was the second T20I of the series between Pakistan and Sri Lanka. Rawalpindi's pitch is historically batting-friendly. The ball comes nicely onto the bat, bounce is low for spinners, and there's virtually no swing for pacers. So a big score is almost inevitable if the team batting first wins the toss. Pakistan posted 215/3—their highest T20I score at this venue. The previous record was 208/3, also achieved at this ground five years ago. Sri Lanka, in reply, stopped at 133/7. An 82-run margin—their biggest defeat in this series. The series is Pakistan's, 2-0. But hidden within this 215 is the story of three dropped catches. Sri Lankan fielders dropped Maaz Sadaqat on 44. They dropped opener-captain Sahibzada Farhan twice—on 2 and 11. Without these three reprieves, it's doubtful whether Pakistan's score would have crossed 200. Because 54 of Sadaqat's 96 runs came from boundaries—seven sixes, six fours. This kind of innings is much like a coin toss: heads you're king, tails you're pauper. Here, heads came up, because catches were dropped. Farhan's 73 off 44—a strike rate of about 166. As a senior batter, he laid the foundation, while also shouldering captaincy. But his innings, too, came after two lives. So the scoreboard shows more than what actually happened. The real tactical signal of the match was Pakistan's death-over batting. In the final five overs, they scored 70 runs. Overs 16 to 20—that's the most crucial phase in T20, because fielding restrictions are off but the pressure to find boundaries is highest. They also built two rapid partnerships in the middle overs—one of 88 runs (off 49 balls), another of 72 (off 31). This kind of momentum can't always be maintained, but teams that can, post big scores. Sri Lanka's only bright spot in bowling was Mohammad Imran—3/11. How many overs he bowled isn't known, but this figure is excellent in T20. New-ball wicket, middle-over pressure—he did both jobs. But based on one match, he can't be considered a permanent fixture. Sri Lanka's batting was a mix of top-order failure and lower-order resistance. Maheesh Theekshana topped the scorecard with 32*—a spinner, primarily in the team to bowl. That alone tells you the top-order batters couldn't fight like Theekshana did. Wickramasinghe 29, Kamindu 23, Jayawardena 22—all small scores. No partnership grew. One thing must be said about this match: Sri Lanka's fielding. Their captain said after the match that fielding is their core weakness, not just in this match, but across the last few tournaments. This admission matters, because it suggests the problem isn't just misfortune—it's become a habit. When I was watching this match—on a TV screen, in a living room in London—I thought once: if this 96-run innings had been completed, that is, if Sadaqat had scored a century, what would the media have written? Perhaps 'the birth of a new star.' But missing by four runs made the story different. To be honest, this four-run gap is statistically no big difference. But it proves how fragile cricket's stories are. One dropped catch, one run-out chance, one missed boundary—these small events change the course of history. My 37 years of watching cricket tell me that giving too much importance to a single innings like this is wrong. One shouldn't forget that Sadaqat was batting quite carefully until he was dropped on 44. After that, he launched his attack, and when Sri Lankan fielders spilled another easy catch, he capitalised. This kind of innings is proof of talent, but not proof of consistency. To prove consistency, he must play more innings away from home, in tougher conditions. A word about Rawalpindi's pitch. Big scores happen here—that's nothing new. From 208/3 to 215/3—in five years, the score rose by just seven runs. This doesn't mean Pakistan's batting has improved dramatically; rather, it's part of the global trend of rising T20 scores. Batting has become easier everywhere, ball quality has improved, boundaries have shrunk. Rawalpindi is no exception. Analysing Sri Lanka's defeat, one thing is clear: they didn't lose due to lack of talent. They stopped at 133 not because they were bowled out, but because no batter could play a big innings. And in the field, they dropped three easy catches. Both are fixable through coaching. The question is, how fast? Because the third match is Tuesday, just two days away. Fixing fielding in that time is impossible. Another aspect: with a 2-0 lead, the series is decided. The third match is therefore a 'dead rubber'—the result won't change the series either way. In such matches, Pakistan often experiments, giving new players opportunities. That's a good thing, but sometimes this experimentation disrupts the batting order. For Sri Lanka, this match is the only opportunity—to return home with at least one win, and to signal a fix to their fielding problems. Another observation of mine: Pakistan's success in this match was driven by their death-over planning. Seventy runs in the last five overs means their batters are aware that from the 16th over, every ball must be attempted to be sent to the boundary. That mindset is invaluable in T20. But the question remains whether this success is sustainable. Because on other grounds, where boundaries are bigger, this strategy may not work. I always believe there's a gap between the scorebook and memory. The scorebook says 215/3, an 82-run win. Memory says a young man dropped on 44, a captain reprieved twice, three dropped catches, and a spinner topping the team's score with the bat. Which of these is more true depends on how you see cricket. If you only look at the result, Pakistan played brilliantly. If you look at the process, you'll understand Sri Lanka lost this match because of fielding, more than batting. If someone asks me tomorrow, 'Bro, how did Sadaqat play?' I'll say, 'We need to see how he was playing before the catch was dropped, and how he played after.' Because real cricket analysis begins where statistics stop. The scoreline is only the door. The story is in the hallway. And I am a tenant of that hallway, who learns anew every match—cricket is never just a game of runs and wickets; it's a story of human error, courage, and second chances.