Rizwan's 200*: Not a Quaid-e-Azam Trophy Century, But a Question for the Selection Process

Hook: 200* on the Scorecard, Questions in the File

Mohammad Rizwan's unbeaten 200 off 252 balls (35 fours, 1 six) is the standout figure of the opening round of the Quaid-e-Azam Trophy. Peshawar declared at 503-4; Faisalabad reached 118-2 at stumps. The headlines read "Rizwan's double century puts Peshawar in command." But I have a habit from 2026: whenever a domestic double century appears, I first ask for the paper—the scorecard—and then for the pitch report. This time, both are incomplete. And when the paper is incomplete, you read its limits more carefully than its shine.

Rizwan's century is beyond doubt—a substantial innings that lifted his team from 127-3 to 503. But the question is not whether he scored runs. The question is whether this innings is proof of a Test recall, or merely a score on a pitch where bowlers had nothing to work with. The register listed him. The nets never did—here, the register is the scorecard, and the nets are Test-level bowling.

Context: The Opening Round of the Quaid-e-Azam Trophy, and a Batting-Dominated Round

The Quaid-e-Azam Trophy (QeAT) is Pakistan's premier domestic first-class competition—the primary funnel for Test selection. It is a multi-day, two-innings format where declaration is a live tactical tool. Peshawar declared at 503-4 in 115.2 overs—a strategy to bat the opposition out of the game.

Four big scores were recorded this round: Rizwan 200*, Najab Khan 133 (226 balls, 20 fours), Mohammad Hurraira (Sialkot) 117 (143 balls, 13 fours), and Ghazi Ghori (Karachi Blues, wicketkeeper-batter) 88 (124 balls, 14 fours). So many big scores—and such high boundary counts—in a single round points to batting-friendly pitches and attacks lacking pace. This is the context the headlines omit.

Karachi Blues, the defending champions, secured a 39-run first-innings lead over Sialkot (280 vs 241)—a tight contest that shows the champion side knows how to extract an advantage under pressure. Meanwhile, the Peshawar-Faisalabad match looks one-sided, but Faisalabad batted stubbornly to reach 118-2 in 35.2 overs.

Core: Beneath the Numbers—Rizwan's 200*, Najab's Support, and the Missing Bowlers

*First: The anatomy of 200.** Rizwan scored 200 off 252 balls, a strike rate of roughly 79.4. In first-class cricket, strike rate is not a quality metric—bowling average and wickets per match are what matter. But 35 fours, roughly one every seven balls, is unusual. It suggests either a very fast outfield, very loose bowling, or an aggressive intent atypical of red-ball accumulation. The 73% boundary share of runs is high for first-class cricket. This is not proof of technical mastery; it is a signal of conditions.

Second: The value of the partnership. Rizwan came in at 127-3 and added 179 for the fourth wicket with Najab Khan (133). This is the role most valued in Test cricket—surviving a crisis and anchoring the innings. In that sense, Rizwan's red-ball "anchor" credentials are reinforced. But it is one innings, against one attack, and no bowler dominated—Faisalabad's Asad Raza and Mudassar Zunair took two wickets each. There was no bowler who truly tested Rizwan.

Third: The bowling dilemma. Declaring at 503-4 meant Peshawar believed their bowlers could dismiss Faisalabad twice. But Faisalabad stood at 118-2 at stumps. If the pitch is flat—as the flood of boundaries suggests—Peshawar's path to victory is difficult. The declaration timing (115.2 overs, Day 2) looks aggressive on paper, but if the pitch favors a draw, it could prove premature.

Fourth: Wicketkeeping depth. Ghazi Ghori's 88 as a wicketkeeper-batter is a quiet but meaningful signal. Rizwan is Pakistan's incumbent keeper-batter. Another keeper scoring runs domestically creates pressure—even if it is just one innings. The register lists Rizwan, but Ghori is also standing at the nets.

Fifth: Karachi's bowling feat. Karachi Blues' Umar took 4-19 in 4.3 overs—the most striking bowling performance of the round. In a batting-dominated round, such a spell could signal an emerging fast bowler. But again, it is one innings; without season-long consistency, it is just a flash.

Contrarian: What Critics Calling for Rizwan's Test Recall Are Missing

The easiest conclusion is that 200* has sealed Rizwan's Test selection. But selectors do not look only at scores—they look at bowling quality, pitch nature, and performance in overseas conditions. Large scores on flat domestic pitches have historically been weak predictors of Test success.

Second: no bowler dominated this round (best figures in the Peshawar-Faisalabad match were two wickets). This indicates pitches were not bowler-friendly. So Rizwan's 200* does not prove he played a tough innings. Those calling it a "return to form" are ignoring the pitch.

Third: Rizwan's dual workload—keeping, captaincy, and batting—raises fatigue and injury risk over a long season. This report makes no mention of injury or workload management. Selectors must look at the body, not just the runs.

Another point: all 43 information points in this report are marked "Source: None." That means no independent verification. The figures are internally consistent, but until cross-checked against the official PCB/QeAT scorecard, they cannot be treated as final truth. I have been reporting from the scorer's box for 35 years—no claim is complete without the paper.

Takeaway: Next Time, Open the Scorecard, Not the Headline

Rizwan's 200* is a big innings, no doubt. But the question is whether it opens the door to the Test team, or is just another link in the domestic record chain. The answer lies in the pitch report, the quality of bowling, and the next round's performance.

Until the official scorecard is verified and the pitch nature is clear, do not treat this as proof of a "Test return." *The paper says 200, but the story behind the paper is still unwritten.**

(The author has covered cricket for 42 years and treats the domestic scorecard as the least reliable document—until it is cross-checked.)