Rawalpindi's 82 Runs, Sadaqat's 96 and Imran's 2.75

On the flat Rawalpindi track, two teams together produced 348 runs and 15 sixes — 12 from Pakistan, three from Sri Lanka. Maaz Sadaqat alone took 66 runs from boundaries. And still the most abnormal number of the night did not sit next to any batter's name; it sat next to a fast bowler's: three wickets in four overs for 11 runs, an economy of 2.75. On a pitch where 215 is raised in 20 overs, on a pitch where a spinner is hit for back-to-back sixes in the death overs, an economy of 2.75 is not a normal event. It is an anomaly. And my old habit is this — when an anomaly shows up, do not leap to a verdict; open the ledger first. I charted 46 matches by hand before I trusted a model, and the condition was always the same: the numbers had to match the ledger. I began charting shots in football with a nine-pound notebook at eighteen. Since then the rule has not changed — before I write any number, I need answers to three questions: where it came from, who collected it, and what it left out. One more thing worth keeping in mind. The first time someone asked whether the girl actually watches the games, I did not answer with feelings; I opened the workbook and showed 1,214 logged shots, not one of them a guess. The same rule applies here. In the second T20I at Rawalpindi, Pakistan have gone 2-0 up, and the scorecard shows an 82-run margin. My job is not to shrink that margin for effect. My job is to break it open and see where it actually came from. The context needs settling, because reading numbers without understanding the match breeds bad conclusions. This is the second T20I of the series — a 20-over international, where the powerplay lasts six overs, the death phase five (16 to 20), and the middle overs load the most pressure on bowlers. In this format, powerplay tempo and death-overs skill decide an innings. The match was played in Rawalpindi, Pakistan's home ground. The pitch was described in a single line: flat, with the odd bit of variable bounce. A batting-friendly surface, where the faint variation in bounce can grip one or two deliveries. It was played under lights; dew was possible, though that was not explicitly confirmed. Look at Sri Lanka. They made three changes and rested their frontline seamer, Dushmantha Chameera. They batted first in game one; here they chose to chase. Whether that decision was reactive or planned is open to question — because the result of the first match shaped the strategy of the second. Pakistan carry a structural change of their own. Sahibzada Farhan is the new captain, and a 21-year-old batter has come in — Maaz Sadaqat. When a side fields a new captain and a new young player at once, it is more than a single-match calculation; it is a signal of generational turnover. Now the numbers. Pakistan 215/3 in 20 overs. Sri Lanka 133/7 in 20 overs. The margin: 82 runs. Pakistan's powerplay brought 24/0 in three overs — they took no early risk. Sri Lanka's powerplay brought 35/2 after six — two wickets down inside six overs, already staring at a 216-run mountain. Wasting a chase's powerplay like that means needing more than eight an over across the remaining fourteen — near-impossible pressure in T20 cricket. Look at Sadaqat's innings. 96 runs, four short of a century, dismissed off the final ball. The split matters: six fours and seven sixes, meaning 66 runs came from boundaries — roughly 69 percent of his total. That is exactly what a modern aggressive top-order T20 profile looks like: a large share of runs from boundaries, with the strike rate climbing in stages. Track his tempo and it becomes clearer. He made 51 off 30, then reached 76 off 40. The longer the innings went, the harder he ran — accelerating into the death overs, the instinct of a modern finisher. He is 21, still pre-peak. That is where the upside lies. But a caution is needed here. His exact balls faced are not in the source material. A precise strike rate needs balls faced, and without it I file that number under 'pending verification'. Building a player's permanent profile from a single innings is not part of my method. Ninety-six in one match means potential, not certainty. Farhan's innings was a different type. 73 runs, with his fifty coming off 31 balls — a strike rate of about 161 in reaching it. The normal T20I top-order benchmark sits around 130 to 150; 161 is above it. Leading by performance as a new captain — the signal is small, but clear. And then comes the number I began with. Mohammad Imran: 3/11 in four overs. Eleven runs in four overs means an economy of 2.75, exceptional on a flat track. His method is notable too — a natural angle into the right-hander's body, the right length without losing his line, and two wickets in two balls. In the middle overs he did not let the tourists breathe. In the same match, the other seamer, Mirza, took 2/28. That is five of Pakistan's seven wickets from two pace bowlers. Turn to the spinners and the story flips. Maheesh Theekshana returned the most expensive figures of his T20I career, conceding three sixes off four balls in the 16th over. That is not a failure of talent; it is the punishment for wrong lengths to a set batter. There is one number on Sri Lanka's fielding, and it is uncomfortable. They dropped at least three catches. Farhan also got a life — a top-edged slower ball spilled. Dropped catches do not just save runs; they buy a set batter more balls, and in T20 cricket those extra balls are what shift the tempo of an innings. This is where my biggest disagreement sits. Reading an 82-run margin, one assumes Pakistan's bowling was unplayable. Break the numbers open and that story weakens. On a flat pitch, 215/3 is not a bowling-friendly environment; it is a batting-friendly one where Pakistan's two batters took the chance. And a slice of the 82 runs was a direct gift from the fielding. The second point is structural. Look at the 215/3 card — almost the entire total came from two batters. The middle and lower order were barely tested. That is comfortable for a good side, but fragile. On a flat track this model works; on a slightly seaming or spinning pitch, if the top two go early, the same card suddenly looks thin. The third point is contextual. Sri Lanka rested their frontline seamer here, brought in three changes, and chose to chase off the back of the previous result. In other words, the opponent was a rotating side, at Pakistan's home. Strip those conditions away and the 2-0 lead cannot be read as a vast talent gap. A match result and a series result are not the same thing; the second always owes a debt to context. The last point is data quality. Every fact from this match reached me through one source, and that source's provenance field is blank. How many balls Sadaqat faced, what his career averages are — no answers. So the 'new star' or 'young sensation' tag is yellow in my ledger, not green. This is where my own profession — transfer market administration — teaches humility. One innings is a row; the market decides by reading the whole table. Having been born in Bangladesh and writing about cricket from Britain, one thing keeps surfacing — the unequal distribution of resource and analysis. Pakistan can risk playing a youngster at home because a domestic pipeline stands behind him. For many other cricket economies, creating that opportunity is far harder. That is what makes Sri Lanka's decision more telling: resting their frontline seamer means this match was not their top priority. Who prioritises what is, in the end, the story of resources. So what do I watch next? First, Sadaqat's consistency. Across the next five matches, especially away, if he holds the same tempo, the 'young sensation' tag goes green. Second, Pakistan's middle order — count how often a total rests on one or two batters. Third, Sri Lanka's drop rate; if two or more drops per match continue, that is a habit, not an accident. And the most important number is Imran's economy. On a flat track, 2.75 is not luck if length and angle hold. If his economy stays under seven across the next three to five matches, then Rawalpindi's night will be remembered not as a batting exhibition but as a story of bowling control. The spreadsheet did not lie; it waited for me to catch up. Rawalpindi's ledger is still incomplete. The 82 runs are written there, but the question mark beside them has not been placed yet — that comes over the next five matches, when the excuses of a home flat track and a rested opponent no longer exist.