President's Trophy Final: Markhor IT bowled out for 112, SBP 136/8 — the day's sharpest spell belonged to Aamir Jamal

The stumps came out at Bagh-e-Jinnah in Lahore on Tuesday evening with two numbers on the board — Markhor IT Solutions 112, State Bank of Pakistan 136 for 8. Eighteen wickets in a day, 65.5 overs, 248 runs in all. A day of eighteen wickets in domestic first-class cricket is a statement in itself, but the report settled on Sirajuddin's six. So I did what I have done for twenty-two years: read the wickets column first, then rebuilt the over-by-over fragment. Six of SBP's wickets belonged to one bowler — Aamir Jamal, ten overs, fourteen runs, six wickets. Economy 1.40. A strike rate of ten balls per wicket. That figure was not built against a loose line-up; it was built against the table-topping batting side, by a man who has played Test cricket.

The final of a first-class season is structurally different from every other game in it. The President's Trophy Grade-I is Pakistan's oldest and heaviest domestic competition, where departmental sides — State Bank, WAPDA, K-Electric and their kind — have been the spine of the system for decades. This year they are up against Markhor IT Solutions, a private-company team. That is why this is not only a contest for a trophy but a contest over who is buying space inside the system. The ground belongs to the same old league: Bagh-e-Jinnah, Lahore's heritage venue with a small capacity, an ageing pavilion, and a pitch report that usually gets one line in the papers.

Khalid Usman won the toss and Markhor IT chose to bat. What followed was 112 all out in 29.5 overs. State Bank replied with 136 for 8 in 36 overs; Rameez Aziz was unbeaten on 14 and Sirajuddin on 8. One thing needs clearing up, because the report left it foggy — Aamir Jamal does not bowl for State Bank. He bowls for Markhor IT. The wicket arithmetic says so: Markhor's ten wickets went to Sirajuddin (6) and Shahid Aziz (4), and State Bank's eight went to Jamal (6), Ismail (1) and Salman Aslam (1). The numbers close perfectly on both sides.

Now to the part that sits beyond the scorecard. All ten of Markhor's wickets fell to two seamers. Sirajuddin and Shahid Aziz bowled 16.5 overs between them for 78 runs; they were expensive at better than six an over, but they took the wickets. The other thirteen overs cost 34. The direct implication is that on that surface a third and fourth bowler was barely required — the ball was moving enough that a seamer could ask the same question again and again while the batter kept giving the wrong answer. But the same figure is the seed of the bank's problem. When two bowlers take ten wickets in 16.5 overs, the captain's third seamer sits cold until day two. If State Bank have to ask on the second morning who bowls the fiftieth over, the answer will take time.

The second innings runs the other way. Thirty-six overs, eight wickets, 136 runs — and a highest score of only 36. The top order found starts and did not convert them; and when nine batters fail to pass 36, the problem is read as the pitch rather than any one bowler. That is precisely why Jamal's spell was the sharpest of the day. Ten overs for fourteen runs means he left the batter no route to score; six wickets means he left no branch of that route either. Sirajuddin's six are bigger numbers, but they came at an economy of 4.7 — the batter tried to score against him and failed. Against Jamal, the attempt never formed.

A third number nobody has joined up: 65.5 overs were bowled. A normal first day of a first-class match is about ninety. Who ate the twenty-four overs — rain, light, or a slow over-rate? The source is silent. That silence is not small. If weather ate the time, the pitch will behave differently on day two and so will both captains' arithmetic. If a slow over-rate ate it, that is also a statement about how long bowlers are taking before releasing the ball.

It is too early to throw a stone at Khalid Usman's toss. On a surface helping the ball, batting first is always the defensive play — you are shielding your batters from a fourth-innings surface. My reading is that the error lay in execution, not in the decision. Being bowled out for 112 is not the toss's punishment; it is a technical report. On a Bagh-e-Jinnah pitch, when two seamers hit the same line for six overs at a stretch, surviving eighteen to twenty overs is the entire job. Markhor IT did not do it, and the price was paid to State Bank in the form of a 24-run lead.

Here the inverted reading arrives, the one the scorecard hides. The trophy currently looks like it is in State Bank's pocket, but the order of innings points elsewhere. State Bank are batting second, which means if the match reaches a fourth innings, State Bank will be the side batting on a surface already showing uneven bounce. A 24-run lead is an advance against a debt that gets collected in the fourth innings. Two wickets remain and the realistic lead sits between fifty and seventy. A lead of ninety or a hundred turns the game; a lead of fifty to seventy only postpones it. Markhor IT, despite folding for 112, are alive in this match — on the condition that they hold State Bank inside 160. In that case a fourth-innings target of 100 to 110 becomes a mountain, because the same two seamers will be standing there with the ball in hand.

This is where an old notebook comes back to me. On the square at Pune's Nehru Stadium, at twenty-eight, I hand-coded 1,412 deliveries in one season — length, line, footwork, scoring zone. That was when I learned that an opposition left-hander was making 78 percent of his runs square of the wicket, and we set a 7-2 off-side field and held him to 41 off 96 balls. The coach called it a fluke. I charted the next eleven games anyway, because the chart rarely shows the pass that changes the room. The same thing has happened here. The chart will say Sirajuddin took six. The room knows the heaviest spell of the day was Jamal's — ten overs, fourteen runs, six wickets, and no option left for the batter.

There is one more layer that domestic reporting usually skips. The man taking 6 for 14 for State Bank is a Test all-rounder. A national-team player is turning out for a departmental side in a final, and across from him stands an IT company's team that got here on its own steam. That picture has always existed in Pakistan's domestic structure — departments provide the money and the facilities, private teams arrive with stubbornness and hunger for space. I think back to my 2026 franchise beat, when every team behaved like a selection committee. The truth is that selection never happens only in a boardroom; it happens in every match where someone takes 6 for 14 and quietly asks for his name back.

And now the question with no available answer: has State Bank's capital already been spent? How Sirajuddin and Shahid Aziz return on day two after ten wickets in 16.5 overs is recorded nowhere. I have always read the game in the gaps between what a coach says and what the bench does, and the gap is here too — no workload figure from the board, no pitch report, no weather detail. The tactical wizard waits for the pattern to confess itself, then names it quietly. The pattern here is this: the match has been built out of 248 runs and eighteen wickets, and its true face will open in the first hour of the next morning.

Three things are worth watching on day two. First, Jamal's opening spell — whether he can pin State Bank's tail with the new ball and keep the lead under 40. Second, Rameez Aziz: a batter unbeaten on 14 is the man with the time to stretch a lead of sixty or seventy towards ninety, and on this pitch a difference of thirty runs can decide the thing. Third, the account of those twenty-four missing overs — if the light held late, the ball will do more, and then a lead of thirty, not fifty, may be enough. Promotion is a season-long argument, not a six-minute highlight, and so is a final. The headline belongs to Sirajuddin. The question belongs to Jamal.