Rawalpindi's Unfinished Page: The Hidden Collapse Inside 168/8

I keep returning to the fourth over at Rawalpindi. Thirty-four runs in three overs, no wickets down. Up in the top tier, the ticket-boy is still holding his folded scorecard, and the man beside him is passing him a cup of tea. Then two wickets fall in a single over. The roar turns into a long exhale, the way wind suddenly dies just before rain. Cricket's cruellest moment is not losing a trophy, and it is not being hit for six off the last ball. The cruellest moment is those few seconds when you realise the fast start was never a foundation; it was only a good spell. Four overs in, Pakistan's scoreboard read 34/0. Ten overs later it read 102/6. The gap between those two numbers is the real match, not the scoreline. I have watched this game for thirty-eight years, from tea stalls in Rajshahi to World Cup finals, from radio static to high-definition screens. That long habit taught me one thing: when a side starts fast and then collapses in the middle, the problem is rarely technique and rarely luck. The problem is structure. Today's 168/8 is exactly that structure drawn in numbers. The context needs stating plainly. This was the third and final T20I of a three-match series, played on Pakistan's home soil at Rawalpindi Cricket Stadium. A decider. One evening would settle the series. The pressure sits on both sides, but it doubles on the hosts, because every person in that ground knows a defeat means losing the series, and a win means closing a whole story. The toss is not stated outright, but the phrase that Pakistan were put into bat tells us Sri Lanka won it and chose to field. Their captain presumably reasoned that bowling first offered an edge here, either some swing with the new ball or the benefit of dew later. In T20 cricket the toss is often the first tactical move of the match. Rawalpindi has long been a batting-friendly ground. The ball comes onto the bat, the boundaries are close, and the seamers get little help. Even 200 is chaseable here. So the central question becomes: how good is 168/8 at this venue? That question is harder than it first appears. I have never watched a match at this ground in person, but from years of following scorecards and radio, Rawalpindi's par score tends to sit somewhere around 170 to 180. By that measure, 168/8 is just below the line, right at the edge. It sits between defensible and winnable. That small gap would decide everything in the hours that followed. Split this innings into three chapters and the picture sharpens: powerplay, middle overs, death overs. Each chapter has its own drama, its own explanation, and its own mistake. Chapter one, the powerplay. Pakistan made 34 in three overs, a rate of roughly 11.3 an over. In T20 cricket that is excellent speed. Fakhar Zaman and Sahibzada Farhan used the fielding restrictions perfectly. With only two fielders allowed outside the circle, gaps are easy to find, and Pakistan found them. But in the fourth over, Sri Lanka's seamer Malinga took two wickets in the same over. A fast start never got the chance to settle into an innings. There is a lesson here. In T20 cricket, a fast start and a solid platform are not the same thing. A solid platform means the ability to hold the run rate even after a wicket falls, the patience to buy time for a new batter. Pakistan did not have that. The middle overs were worse. From 34/0 they slid to 102/6. This was not one error but a steady fall: Nafay 3, Imran 6, Sadaqat 0, Razaullah 0, and Hasan Nawaz 16 off 17. Read that list and a pattern appears. No batter built a score; no batter stopped the slide. Hasan Nawaz's 16 off 17 is the loudest signal. A strike rate of 94 in T20 means almost one run per ball. With the side gasping at 102/6, a middle-order batter faces two paths: soak up balls and protect the wicket, or score quickly and push the pressure back. A strike rate of 94 does neither. It is the slow death that hurts most in T20, because time drains away while runs do not accumulate. Sri Lanka's bowling makes the picture clearer. Dasun Shanaka took 3/21 in four overs at an economy of just 5.25, in a match where Pakistan scored at 8.4 an over. That economy is outstanding. Shanaka, the experienced all-rounder, controlled the middle overs and took wickets at the same time, one of the hardest jobs in the format. Malinga and Thushara took two wickets each, Viyaskanth one. Sri Lanka's plan was clear: pace to break the top with the new ball, Shanaka's control through the middle, Thushara's pace at the death. Yet the plan broke in one place. Sri Lanka could not break the seventh-wicket stand. That was their only real failure. They had dragged Pakistan down to 102/6, but in the final five overs they could not separate two batters. In T20 cricket a match often turns on exactly that one partnership, and it did here. The death overs were the real drama. From 102/6, Pakistan reached 168/8. A 66-run seventh-wicket stand, with captain Sahibzada Farhan at one end and Arafat Minhas at the other, carried Pakistan from a humiliating score to a respectable one. Look at Farhan's innings: 76 off 47, a strike rate near 161.7, with seven fours and three sixes, meaning 46 of his 76 runs came in boundaries, about 61 per cent. Boundary reliance is normal for top T20 scorers on small grounds. But Farhan's case is different. He played anchor and accelerator at once. Wickets fell around him while he held his strike rate. This is not just a good innings; it is a captain's innings. Arafat Minhas is less discussed but no less important: 34 not out off 20, a strike rate near 170. At the death, that is superb. As an emerging all-rounder, his innings sends a signal. Pakistan's finisher depth may sit at seven and eight rather than in the specialist middle order, which raises a balance question for team management. Now to where I disagree with the standard telling. Everyone frames this match as a captain's fighting fifty rescuing Pakistan. That is true, but only half true. The real question is why Pakistan needed rescuing at all. When a side collapses from 34/0 to 102/6, the story is not the rescuer; the story is the collapse. If a captain must save his team every match, that is not heroism. That is dependency, and dependency is a weakness in T20 cricket. There is another point. The total has been described as competitive. On a batting-friendly ground like Rawalpindi, whether 168/8 is actually enough is questionable. Over the years I have noticed home-team media often dress a low score as a challenging one. This is not deliberate deception; it is the language of sympathy. But the analyst's job is not the language of sympathy; it is the language of numbers. There is also a gap in the telling: the result is missing. Pakistan made 168/8, but what Sri Lanka did, and who won, is not recorded. So the word rescue is hard to use, because whether a rescue succeeded depends on the chase. If Sri Lanka chased this down comfortably, Farhan's innings becomes a beautiful but losing one, and the whole story turns. I want to add something usually absent from such reports. A T20 innings's true value is set in the light of the next innings. How good 168/8 is depends on the pitch, the dew, the wind, and the depth of the opposition batting. Judging 168/8 without those facts means reaching a conclusion from half a picture. One more thing. The way the finishing came from numbers seven and eight actually signals Pakistan's batting structure. The reliance on the top three is so heavy that when the middle collapses, the whole innings rests on two pairs of shoulders. That is dangerous in tournament cricket, because over a long series an opponent identifies the weakness, and the same pressure returns every match. Sri Lanka deserve a note too. Shanaka's 3/21 was the product of experience. When an experienced all-rounder bowls in the middle overs, he does not just stem runs; he breaks a batter's concentration. That role is often undervalued in T20 because people watch the sixes, not the control. But read the match carefully and Shanaka's four overs are what kept Pakistan at 168. Sitting over a scorecard at a tea stall in Rajshahi, one thought stayed with me. Cricket teaches us more than the arithmetic of winning and losing; it teaches us how to read a team's character. Pakistan's innings showed how a side rises fast, falls suddenly, and then stands again on one man's shoulders. The question now is this: in the matches that follow, will Pakistan see the gap in its middle order, or will it wait each time for a captain's fighting fifty? A team that hides a structural weakness behind individual flashes never becomes truly strong. It becomes dazzling but brittle. And a question for Farhan. When a captain is both his side's top scorer and its leader, he carries two loads. How long can he carry them alone? If the answer is a long time, that is good news for Pakistan. If the answer is alone, that is Pakistan's real worry. I want to remember Arafat Minhas's name. An innings like 34 not out off 20 is often the first page of a larger story. Perhaps months from now we will look back and see that this match began his rise. That is cricket's finest quality: today's scorecard is tomorrow's history, and none of us know which number will survive. A pitch is a page, and every delivery is a sentence we did not know we needed. Today's page is unfinished. It stops at 168/8, and perhaps the next innings will write the rest. I will be waiting, because cricket's greatest beauty is this: the story never ends before the match does.