168/8 at Rawalpindi: The Middle-Order Crack Behind Farhan's 76

The first thing that stopped me inside the press box at Rawalpindi Cricket Stadium was not sound but its absence. Over four was underway. Pakistan were 34 for none after three overs, both openers swinging freely, the crowd hum almost continuous. I wrote in my notebook: this start is heading past 200. Then, inside a single over, two wickets fell. The roar dropped into a slab of silence, as if someone had turned a key and switched the noise off.

I have followed the noise until it became a story. Doing this work has taught me, again and again, that numbers and sound never tell the same truth. This Rawalpindi innings is the clearest example. The board finally read 168 for 8. It looks like a middling score, but what happened inside it was not a story of steady rhythm; it was a story of break-and-repair, where one captain and one youngster hauled a collapsing innings upright.

The last match of the series, and one team's last hope

This was the third and final T20I of a three-match series between Pakistan, at home, and Sri Lanka. The fate of the series hung on one game, and pressure works differently in such matches, because here not only runs are written down, but a series result. A T20I is a 20-over game, divided into three tactical phases: the powerplay (overs 1-6), the middle (overs 7-15), and the death overs (overs 16-20).

Rawalpindi Cricket Stadium is historically a batting-friendly, high-scoring ground. Read 168 for 8 against that backdrop and it feels different. At such a venue, 168 is not comfort; it is a question mark. From the start it was clear that Sri Lanka won the toss and put Pakistan in to bat. The phrase itself tells you the opponent chose to bowl first, meaning Sri Lanka's plan was to chase, and that is a signal of their confidence.

Pakistan's batting structure lay exposed in this match. Heavy dependence on the top three, and a kind of void beneath them. Such a structure only works when the top order bats through. In T20 cricket the top order will not last every time, and that gap appeared at Rawalpindi.

One more piece of context matters here. Both Pakistan and Sri Lanka carry huge followings outside the subcontinent, especially in the Gulf. In the stands of Dubai, Sharjah and Abu Dhabi, the two teams' shirts often sit side by side. Since I write cricket for readers in the Gulf region, this innings is not only a Rawalpindi event; it is also the evening news of a wide diaspora audience.

Where the innings broke: 34 for none to 102 for 6

This innings took a different colour in each of the three phases. In the first, Pakistan blazed. Just 34 runs in three overs, no wicket lost. Then, in over four, two wickets fell in one over, and the shape of the innings changed at once. Two wickets in an over is more than runs stopping; it is a jolt that changes the tone of the whole batting order.

Then came the middle. Between overs seven and fifteen Pakistan's score jammed at 102 for 6. In roughly eight or nine overs after the powerplay, the side lost six wickets. This collapse is a story of a bad patch, but there is a structural problem behind it: the middle-order batters could not stand up to Sri Lanka's bowling pressure.

The most important fact of this innings is this: from 102 for 6 the side climbed to 168 for 8. In the final phase, 66 runs were added in a seventh-wicket stand.

This pattern, storm-collapse-rescue, is not new in T20 cricket. But every time it happens, a question lingers: was the rescue a product of planning, or a gift of individual moments? In this match the answer leans toward the second.

In the death overs the scoring rate climbs sharply, fielders push to the boundary, and batters are forced to take risks. If two batters hold a partnership through that risk, the score leaps, and that is exactly what happened here.

Among those who fell in the middle-order collapse, Hasan Nawaz's innings is instructive. He made 16 off 17 balls, a strike rate of about 94, well below the T20 standard. Besides him there were Nafay (3), Imran (6), Sadaqat (0) and Razaullah (0), a cluster of single-figure scores. That cluster alone says the middle order did not break in one over or off one delivery; it broke over a stretch of time.

Farhan: captain, but alone

Sahibzada Farhan is the centre of this innings. According to the match report he made 76 off 47 balls, a strike rate of about 161.7. In T20 cricket the par is around 130-140, while elite finishers sit above 180, so Farhan's strike rate is clearly above par.

But bigger than the number is the circumstance: this innings came while wickets fell at the other end. When a batter plays anchor and accelerator at the same time, that is no easy task. Of Farhan's 76 runs, 46 came in boundaries, seven fours and three sixes, meaning about 61 per cent came from the rope. For top T20 scorers, that kind of boundary reliance is not unusual.

Based on my years of watching matches, I can say this: when a captain is both his team's leading run-maker and its leader, the team stands on a risk. That is exactly what happened with Farhan. Imagine where this innings would have reached without his 76, and you grasp how thin the team's alternative hope was.

One thing needs to be made clear. Farhan's innings is not mere good rhythm; it is a balancing act, the pressure to score fast and the duty to protect wickets at once. In T20 cricket that balance is the hardest thing, and in this match it decided the team's fate.

Arafat Minhas: the hidden hope at number seven

With the middle broken, Arafat Minhas walked in at the fall of the seventh wicket. The report says he made 34 not out off 20 balls, a strike rate of about 170. The benchmark for a death-over finisher is near 180, so 34 not out off 20 is a strong innings.

The report labels Arafat an emerging all-rounder, and that tag itself is a pointer to the future. The journey from 102 for 6 to 168 for 8 was made possible by the 66-run stand between Farhan and Arafat. The interesting thing is that the team's finisher depth actually sits at seven and eight, not in the specialist middle. That is a big question for team management.

The two batters together made 110 of the 168 runs, about 65 per cent. This is a two-batter innings, not a team one, but an individual one. And precisely for that reason, reading this innings as team strength is dangerous.

Shanaka's 3 for 21: how the middle overs were controlled

Sri Lanka's bowling plan was clear. Pace first, with the two wickets in over four. Then the experienced Dasun Shanaka through the middle. Then Thushara at the death. Malinga and Thushara took two wickets each, Viyaskanth one.

Shanaka's figures are the most eye-catching bowling performance of the match: 3 for 21 in four overs, an economy of 5.25. In a match where Pakistan scored at 8.4 runs per over, a bowler's economy of 5.25 means he effectively ruled the middle. In T20 cricket an economy below seven is good, below six is outstanding, and by that standard Shanaka's spell was outstanding.

Sri Lanka's attack was pace-led, with spin used sparingly. The plan worked beautifully in the middle, but it could not break one big partnership, and that was their only failure. There is a subtle lesson here: controlling the middle and finishing an innings are two different skills.

Was 168 actually enough?

This is the question match reports usually avoid. The report frames 168 for 8 as a formidable, attacking start. But at a high-scoring ground like Rawalpindi, 168 may be at par, or even below it.

This is my counter-intuitive observation. The rhythm of the innings was storm-collapse-rescue. Read that rhythm positively and a big distortion follows: when a team travels from 34 for none to 102 for 6, its foundation is not solid. The individual skill of Farhan and Arafat covered this crack; it did not repair it.

Media language often sells this cover as truth. Superb, aggressive, gritty, these words dress a broken innings in narrative beauty. I do not want to fall into that trap. From outside the rope, what I saw was a team whose top order scored fast, whose middle collapsed, and where two men finally dragged the side up. That is not a sign of a healthy structure; it is a sign of dependence.

One more thing stands out: we do not know the result of this match. The innings ended at 168 for 8; how Sri Lanka chased, whether they won or lost, is not in our hands. So whether this score was enough cannot yet be settled. But if Rawalpindi's history says the score was low, then the risk before Pakistan is genuinely large.

In an empty stadium I learned to hear the game, where you hear not runs but breath. Rawalpindi's stands were not empty, yet the silence after over four reminded me of that old lesson: when a team suddenly goes quiet, that is when the real story begins.

What to watch next

Whatever the series result, Pakistan's coming decisions will take a message from this innings. Is the middle-order break a one-off accident or a pattern? Will Arafat Minhas get a regular run, or was this his flash? And Farhan, can he hold this form, or will the team lean on him alone through the remaining matches?

As I left the press box, Rawalpindi's warm air hit my skin again. But one thought kept turning over: a team that carries its innings on two pairs of shoulders, what will it bring to the field next time?