Quaid-e-Azam Trophy: Behind Babar's 20, Farooq's 123 and Peshawar's 503—The Real Story of Round One

First-class scorecards never lie about runs and wickets, but they are silent about the things that truly decide matches. As I sorted through the first-round scores of the Quaid-e-Azam Trophy 2026-27, one number kept catching my eye: 40/4. That was Lahore Whites' second-innings score at the close of day three, chasing 412. Babar Azam was unbeaten on 20. They needed 372 more runs with six wickets in hand. In first-class cricket, the probability of winning a fourth-innings chase after losing four early wickets is historically below 15 percent. Yet the headlines will belong to Babar, because he is Pakistan's Test captain. The real story of this round, however, is hiding in Mohammad Farooq's 123 from 113 balls, Peshawar's declaration at 503/4, and Sialkot's twin centuries. I have been logging scorecards like these since 2026—not the narrative of events, but the numbers behind the decisions. This article is a page from that archive, an attempt to look inside four matches of the first round and assess which decisions were justified and where we are once again falling into the trap of personality worship.

The Quaid-e-Azam Trophy is the primary platform for Pakistan's domestic first-class cricket. In this four-day format, declaration, follow-on, and fourth-innings targets are the three elements that determine a match's fate. Three of the four first-round matches saw these elements in play. FATA set Lahore Whites a target of 412, Peshawar declared at 503/4 and enforced the follow-on, Sialkot declared at 388/5, and Islamabad reduced the deficit against Multan's 327. A cursory look at these scores would suggest Peshawar is the strongest side. But a deeper look reveals that in each match, the captains' decisions—when to declare, whether to enforce the follow-on—changed the course of the game. In first-class cricket, these decisions are made primarily based on two numbers: how many runs are sufficient and how many overs remain. Peshawar's declaration at 503/4 clearly indicates they prioritized time over runs. After Faisalabad were bowled out for 259, enforcing the follow-on means they must score another 190 runs in their second innings to avoid an innings defeat. This decision is only justified if Peshawar's bowlers are not fatigued and the pitch is not easy for batting. But the report provides no information on the pitch or overs. We are left to speculate.

Yet one number breaks through the speculation: Mohammad Farooq's batting strike rate. 123 off 113 balls, approximately 108.8 runs per 100 balls. In first-class cricket, this strike rate is rare. His innings included nine fours and eight sixes. In other words, 84 runs came from 17 boundaries, and the remaining 39 runs came from 96 balls. This signals a consciously aggressive innings. But here a question arises: was this innings in FATA's first innings or second? The original report contains an inconsistency—one part says FATA resumed its first innings, another describes Farooq's innings as second-innings batting. This inconsistency is not a minor detail; it could change the entire course of the match. If Farooq's 123 was in the second innings, it was an innings that created pressure for a quick declaration, helping to set Lahore a target of 412. If it was in the first innings, it was a foundation-laying innings. Both are significant, but the tactical implications differ. I looked for the official scorecard to resolve this inconsistency, but the report provides no link. For now, this remains a question mark.

Peshawar's declaration at 503/4 and the follow-on together represent a classic first-class tactical trade-off. When a captain declares at 503, he is thinking of two things: first, mentally breaking the opposition; second, giving his bowlers enough time. But the decision to enforce the follow-on is more complex. If the pitch is favorable for batting, enforcing the follow-on means giving the opposition a chance to bat again with more confidence. If the pitch is spin-friendly, enforcing the follow-on means quickly taking wickets without exhausting his spinners. The report provides no pitch details, so we do not know how justified Peshawar's decision was. One thing is clear: Faisalabad's 259 and the follow-on together indicate that Peshawar's bowling attack was effective in the first innings. But how effective they will be in the second innings depends on the bowlers' workload and the pitch behavior.

In the Sialkot-Karachi Blues match, we see a different tactical picture. Sialkot declared at 388/5, with Muhammad Hurraira scoring 141 (195 balls) and Mohsin Riaz 100* (101 balls). Analyzing the tempo of these innings, Hurraira's strike rate was about 72.3, while Riaz's was about 99.0. Hurraira played more balls, Riaz scored faster. The combination of the two took Sialkot to 388/5 and created the opportunity for a declaration. Karachi Blues' score is 2/1—meaning they lost one wicket in their first innings and have nine wickets in hand. Chasing 388 in the fourth innings is never easy, but with nine wickets in hand, the match is not yet over. Historically, the success rate of chasing 388 in the fourth innings of first-class cricket is low, but without knowing the depth of Karachi's batting lineup, no prediction can be made.

The Islamabad-Multan match has relatively less information. Multan scored 327, Islamabad trailed by 112 in the first innings, but Raja Hamza Waheed's brisk half-century helped reduce the deficit. The report does not provide Islamabad's exact score or the current state of the match. Thus, there is insufficient information for analysis.

Looking at these first-round scores, one thing is clear: there is a balance between teams in domestic first-class cricket, but the presence of a star player can influence that balance. Babar Azam's presence has brought Lahore Whites' match into the media spotlight, but the actual state of the match is that Lahore is 40/4 and needs 372 runs. Babar's 20 is not yet a decisive contribution. Rather, Farooq's 123, Hurraira's 141, and Riaz's 100 are the real stories of the first round. But the media's tendency is to build stories around stars. I call this the 'star-centric reporting trap.' Falling into this trap makes us lose the actual tactical stories of the match.

Another aspect of first-class cricket is bowling workload. Peshawar's decision to enforce the follow-on is influenced by bowler fatigue. If Peshawar's main bowlers bowled many overs in the first innings, enforcing the follow-on could be risky. The report lacks bowling figures, so we do not know who bowled how many overs. But one thing can be inferred: if Peshawar enforces the follow-on, their bowlers will have to bowl again in the second innings, increasing their total workload. This decision could create pressure on the bowlers in the long run, especially if they continue playing in subsequent rounds. My previous research has shown that the decision to enforce the follow-on in first-class cricket can affect bowlers' performance in the next match. It is like a long-term investment—risking tomorrow's bowler for today's win.

The same logic applies to declarations. Sialkot declared at 388/5, an aggressive decision. Had they added another 50-60 runs, Karachi's target would have been more difficult, but time would have been reduced. Balancing time and runs in first-class cricket is an art. Sialkot's captain felt 388 was enough and wanted to put Karachi under pressure. This decision will be vindicated only if Sialkot's bowlers can bowl Karachi out cheaply. But if Karachi fight, Sialkot's captain may have to self-analyze.

Another thing is clear from the first-round scores: there is no shortage of talent among batsmen in domestic first-class cricket. Farooq, Hurraira, and Riaz all scored centuries in the first round. But a century in one match does not determine a player's permanent worth. I have seen many players in my career score centuries in domestic cricket and fail at the international level. And vice versa. So these centuries should be celebrated, but they should not be seen as guarantees of the future. In Farooq's case, one thing is notable: his strike rate was over 100, unusual in first-class cricket. Such an innings may be effective against a specific pitch or a specific bowling attack, but not in all conditions. To assess his technical skill, more matches are needed.

Peshawar's declaration at 503/4 and the follow-on together represent a classic first-class tactical trade-off. When a captain declares at 503, he is thinking of two things: first, mentally breaking the opposition; second, giving his bowlers enough time. But the decision to enforce the follow-on is more complex. If the pitch is favorable for batting, enforcing the follow-on means giving the opposition a chance to bat again with more confidence. If the pitch is spin-friendly, enforcing the follow-on means quickly taking wickets without exhausting his spinners. The report provides no pitch details, so we do not know how justified Peshawar's decision was. One thing is clear: Faisalabad's 259 and the follow-on together indicate that Peshawar's bowling attack was effective in the first innings. But how effective they will be in the second innings depends on the bowlers' workload and the pitch behavior.

Here a question arises: is Peshawar's dominance a reflection of genuine strength or the result of Faisalabad's weakness? In first-class cricket, the answer is never simple. A big score and a follow-on together indicate two things—Peshawar batted well and Faisalabad bowled poorly. But which was more influential depends on future matches. If Peshawar faces a strong bowling attack in the next round and scores low, it will show their batting is not as strong. If Faisalabad bat well in their next match, it will show their first-innings failure was an exception.

Another thing is clear from the first-round scores: there is no shortage of talent among batsmen in domestic first-class cricket. Farooq, Hurraira, and Riaz all scored centuries in the first round. But a century in one match does not determine a player's permanent worth. I have seen many players in my career score centuries in domestic cricket and fail at the international level. And vice versa. So these centuries should be celebrated, but they should not be seen as guarantees of the future. In Farooq's case, one thing is notable: his strike rate was over 100, unusual in first-class cricket. Such an innings may be effective against a specific pitch or a specific bowling attack, but not in all conditions. To assess his technical skill, more matches are needed.

I have been analyzing scorecards of domestic and international cricket since 2026. My experience says the winner of a tournament cannot be determined from first-round results. Because in the first round, teams may not be at their best form, pitches may vary, and opposition strength may differ. So these first-round scores should be seen as a signal, not as conclusive proof.

My biggest concern is the lack of information. This report has no link to an official scorecard, no pitch description, no weather information, and a clear inconsistency regarding FATA's innings. In this situation, any analysis is reliant on speculation. I always say in my writing—when information is incomplete, conclusions are also incomplete. The same applies here. I celebrate Farooq's 123, Hurraira's 141, Riaz's 100*, but at the same time I caution that these numbers are not the final word.

One thing always makes me think—the media coverage of domestic first-class cricket. There is talent in Pakistan's domestic cricket, but the process of bringing that talent to the international level is not well-integrated. The Quaid-e-Azam Trophy is an important part of that process. But if the matches of this tournament are not properly covered, if scorecards are not publicly available, the process of identifying talent is hindered. I believe improving coverage of domestic cricket is essential—not just for star players, but for all those players who scored centuries in the first round but did not catch the media's eye.

Ultimately, the first-round scores teach us one thing—success in first-class cricket comes from a combination of patience, strategy, and team effort. Peshawar's 503/4 and follow-on, FATA's 412 target and Lahore's 40/4, Sialkot's 388/5 and Karachi's 2/1—these are all classic first-class situations. But the stories we get from these situations are not limited to scores. They are stories of captains' decisions, bowlers' patience, batsmen's aggression. And these stories are what make first-class cricket special.

In the coming days, the final results of these matches will tell us who was right. But before that, we must seek the answer to one question: what did we learn from the first-round scores? The answer is—we learned that in first-class cricket, numbers and strategy go together. Farooq's 123 is a number, but the strategy behind it—scoring quickly and creating pressure for a declaration—is the real story. Peshawar's 503/4 declaration is a number, but the strategy behind it—balancing time and runs—is the real story. If we see only numbers and not strategy, we see only half of cricket. And if we see only strategy and not numbers, we see the other half. The beauty of first-class cricket is the combination of the two.

I end this report with a question: will the talents who showed themselves in the first round of the Quaid-e-Azam Trophy be able to maintain this form? Or will we again remember a one-match star and forget him in the next match? Time will tell. But I will keep writing their stories on this journey, because I believe every score has a story behind it, and those stories enrich our cricket.