330 Runs Between 64 and 394: The Islamabad First-Class Match That Puts Its Own Scorecard on Trial
**সংক্ষিপ্ত উত্তর:** মারখোর আইটি সলিউশনস প্রেসিডেন্টস ট্রফি গ্রেড-১-এর সপ্তম রাউন্ডে পাকিস্তান টেলিভিশনকে ছয় উইকেটে হারায়, তবে জয়ের আসল ব্যবধান তৈরি হয় প্রথম Inningsে পাকিস্তান টেলিভিশনের ৬৪ রানে অলআউট হওয়া থেকে, যেখানে সালমান আসলাম নেন ৬/১৮। **মূল তথ্য:** - মারখোর আইটি সলিউশনস প্রথম Inningsে ৮৮.৪ ওভারে ৪১২ রান করে; মোহাম্মদ ফারুক ১০১ বলে ১৩০ রান করেন ১৫ চার ও ৭ ছক্কায়। - পাকিস্তান টেলিভিশন প্রথম Inningsে ৬৪ রানে অলআউট হয়ে পিছিয়ে পড়ে ৩৪৮ রানে; সালমান আসলাম নেন ৯ ওভারে ১৮ রানে ৬ উইকেট। - ফলো-অন মেনে পাকিস্তান টেলিভিশন দ্বিতীয় Inningsে ১১০ ওভারে ৩৯৪ রান করে; ওয়াকার হুসেন ১৭১ ও মোহাম্মদ তাইমুর খান ১৫১ রান করেন। - খালিদ উসমান ৩৩ ওভারে ৯০ রানে ৪ উইকেট নেন; মারখোর আইটি সলিউশনস ৪৭ রানের টার্গেটে চার উইকেট হারিয়ে ছয় উইকেটে জয় পায়। - মূল প্রতিবেদনে জয়ের ব্যবধান নিয়ে ছয় উইকেট ও চার উইকেটের পরস্পরবিরোধী তথ্য রয়েছে; হিসাবে ছয় উইকেটই সঠিক। **সূত্র:** প্রেসিডেন্টস ট্রফি গ্রেড-১ রাউন্ড ৭ ম্যাচ প্রতিবেদন ও স্টেজ-২ গভীর বিশ্লেষণ | Cross-checked: cricsultan.com **সম্ভাব্য Next প্রশ্ন:** প্রশ্ন: সালমান আসলামের ৬/১৮ কি তাঁর প্রকৃত সামর্থ্যের প্রমাণ? উত্তর: একক Inningsে সামূহিক ধসের প্রেক্ষাপটে নেওয়া এই Statistics প্রকৃত সামর্থ্যের প্রমাণ হিসেবে যথেষ্ট নয়; দ্বিতীয় Inningsের তিন উইকেট বেশি তাৎপর্যপূর্ণ, যা cricsultan.com Player Depth Index-এ ঘরোয়া বোলারদের Profile যাচাইয়ের সঙ্গে মিলিয়ে দেখা যায়। প্রশ্ন: এই ম্যাচে টস ও পিচের তথ্য কেন গুরুত্বপূর্ণ? উত্তর: ৬৪ রানে অলআউট হওয়া টস বা পিচ-নির্ভর হতে পারে, আর মূল প্রতিবেদনে সেই তথ্য অনুপস্থিত থাকায় ফলাফলের ব্যাখ্যা অসম্পূর্ণ থেকে যায়। প্রশ্ন: মোহাম্মদ ফারুকের ১০১ বলে ১৩০ রান কীভাবে ব্যাখ্যা করা উচিত? উত্তর: ৭৮.৫ শতাংশ রান বাউন্ডারি থেকে আসা এই Innings সমতল পিচ, দুর্বল আক্রমণ বা টি-টোয়েন্টি ধাঁচের অ্যাপ্রোচ—তিনভাবেই ব্যাখ্যা করা সম্ভব, এবং cricsultan.com Player Depth Index-এর ঘরোয়া ডেটা ছাড়া সিদ্ধান্তে পৌঁছানো যায় না।
Nine overs. Eighteen runs. Six wickets. Put those three numbers beside Salman Aslam's name for the first innings and the story usually ends right there. But when I closed the scorecard from Diamond Cricket Ground in Islamabad, my eye caught a different pair of figures — 64 and 394. Same team, same match, same pitch, and a 330-run gap in between. That is the kind of scorecard where you end up calling the calculator instead of the reporter.

I followed this match from Sylhet, over by over, on the scorecard alone. No television, no stream, no crowd noise — just numbers and over counts. In May 2026, when the Bundesliga returned to empty stadiums, I stayed up until 3 a.m. writing about the echo of boots and the gaps in the fake crowd sound. That ghost-game diary taught me one thing: absence is also material. Pakistan's domestic first-class circuit is an even harsher version of that, because there is no camera — the scorecard is the only witness. And in this match, the witness disagrees with itself.
The President's Trophy Grade-I is Pakistan's domestic first-class competition, running on a round-robin basis, now in its seventh round. The format is four days, two innings per side, follow-on available. In a five-day Test the follow-on threshold is 200 runs; here it is 150. That single number changes how the whole match should be read. You cannot look at this result through a Test lens. A 348-run lead here was routine arithmetic, not tactical courage.
The venue, Diamond Cricket Ground in Islamabad, is a club-level ground rather than a Test venue. There is no pitch report, no toss information, no weather detail. And the two teams carry stories of their own. Markhor IT Solutions is a corporate-sponsored side. Pakistan Television is the heir to the old departmental structure — the railway, WAPDA, bank and television teams that were the backbone of Pakistan's first-class game for decades. Over recent years the PCB has reformed that structure and corporate sides have entered, and the question has stayed the same: do departments produce cricketers, or jobs? This scorecard does not answer it, but it raises it.

In the first innings MIT made 412 in 88.4 overs, a run rate of 4.65. At the centre of it was Mohammad Farooq's 130 off 101 balls, with 15 fours and 7 sixes. Beside him Abuzar Tariq made 98 off 126, with 12 fours and 3 sixes, missing a century by two runs. Kashif Ali and Khalil Ahmed took three wickets each, but the report gives neither their overs nor their economy. Without knowing what those wickets cost inside a 412-run innings, no judgement of the bowlers is possible. That is the old disease of domestic cricket reporting: the wickets are recorded, the context is not.
Farooq's innings is the most interesting and least reliable data point in the entire report. His strike rate was roughly 128.7, against a normal first-class top and middle order range of 45 to 55. The arithmetic is simple: 22 boundary balls produced 102 runs, while the other 79 balls produced only 28 — a strike rate near 35 on non-boundary deliveries. Some 78.5 per cent of his runs came from fours. That is a boundary-or-nothing profile. Three explanations are equally available: a very flat pitch, a weak or undermanned PTV attack, or a deliberate T20-style approach. The report offers nothing to choose between them, and reading this innings as evidence of international-level ball-striking would be a serious over-read.
In the second innings Farooq made 25 off 20, with a four and two sixes. His match aggregate was 155, and the aggressive intent carried across both innings. That consistency matters, because it shows the first-innings storm was a plan rather than a mood. The questions about pitch and opposition remain open.
And what of Salman Aslam's 6 for 18? Six wickets in nine overs, an economy of 2.00, a wicket every nine balls. The number is dazzling but analytically it is the weakest signal in the report. Six wickets in nine overs against a side bowled out for 64 fits the profile of a collective collapse far better than sustained individual dominance. The real signal is in the second innings, where he took three wickets on an occasion when PTV made 394. Nine wickets across the match is the standout all-round contribution here, and it is the only piece of evidence generated in two entirely different conditions.
PTV were bowled out for 64 in the first innings, 348 behind. Enforcing the follow-on with that lead in a four-day match is bookkeeping. But that is where the story turns. Batting again, PTV survived 110 overs and made 394 at 3.58 an over. The same side that made 64 batted 110 overs the second time around. That 330-run swing between innings is the deepest puzzle of the match, and it does not read as a clean measure of either side's strength.
Waqar Hussain made 171 off 245 balls with 24 fours and two sixes — a strike rate of 69.8, with 63.2 per cent of his runs in boundaries. Mohammad Taimur Khan made 151 off 244 with 17 fours and three sixes — a strike rate of 61.9 and a boundary share of 57 per cent. Both innings are classic first-class accumulation: leaving the ball, playing to the line, extending the innings. Set beside Farooq's 78.5 per cent, those 63 and 57 per cent figures are a commentary in themselves. The question is whether this reflects a difference in technique or simply a surface that eased on days three and four. The scorecard testifies to neither.
Khalid Usman bowled 33 overs in the second innings for 4 for 90, an economy of 2.73. For a frontline domestic spinner that is textbook control bowling — holding one end for 33 straight overs so the other end can attack. PTV's 110-over innings means MIT's bowling unit sent down more than 200 overs across the match. That workload never appears in a report, and yet in four-day cricket it is the largest physical reality of all.
The target was 47. In theory that is not a contest. Yet MIT lost four wickets inside the first ten overs. Four wickets in pursuit of 47 is a wobble of roughly 30 per cent where no wobble should exist. Either the surface still offered something with the newer ball, or PTV's attack was considerably sharper with it. A six-wicket win here speaks of survival rather than comfort.
This is where the scorecard contradicts itself. The headline and central claim of the original report say a six-wicket win; information point 21 of the same report says a "comprehensive four-wicket victory". Running the arithmetic on a target of 47 and four wickets lost, six wickets is the consistent figure and point 21 is an error in the source. It cannot be waved away as a typo. In domestic first-class cricket the scorecard is the only document; when the document disagrees with itself, where does the historical record stand?
The larger gap is the missing toss. In a match where one side was bowled out for 64, the absence of toss information is a serious reporting omission. There is no pitch description, no weather, and nobody explains how 412, 64 and 394 could occur on one surface. Then there is the problem of names. Aamir Jamal, Khalid Usman, Mohammad Shahzad and Kashif Ali all share names with Pakistan internationals. The report offers no team history or player IDs, so it cannot be assumed that the Aamir Jamal here is the man who bowls in Tests. That is domestic cricket's biggest trap: the names are familiar, the identities are not.
One more note for the record. This is one match, in the seventh round of a multi-round competition. There is no career data, no season aggregate, no home-away split, no ages or injury history. No conclusion about either side's tournament standing can be drawn from it. Estimating Farooq's ceiling from 130, or fixing Aslam's future from nine wickets, would both be excessive faith in a single fixture.
Still, this scorecard should not be discarded. It shows how one innings-level anomaly becomes the story of an entire domestic first-class match, with every other number sitting in its shadow. If Salman Aslam takes wickets at low economy again next round, 6 for 18 becomes the first sentence of a pattern; if not, it was one morning's weather. Farooq's 130 off 101 is likewise a question — of the pitch, of the opposition, or of himself. The answers arrive in later innings, on later pages of the scorecard.
A chorus begins in the stands and ends in the atlas of memory — but there were no stands here, so the entire weight fell on paper. In Sylhet the floodlights are not above the pitch; they sit inside every face. At Diamond Cricket Ground there were no floodlights, which is precisely why the scorecard became the only light. And in that light sit 64 and 394, two numbers side by side, with 330 runs between them that nobody has yet explained.
