One Innings of Collapse Decided It: The Ledger Behind MIT Solutions' Win in Islamabad

Four wickets down inside ten overs while chasing 47. On the scoreboard, Markhor IT (MIT) Solutions' win over Pakistan Television (PTV) in Round 7 of the President's Trophy Grade-I at Diamond Cricket Ground, Islamabad, looks comfortable. From Dhaka, matching the over-by-over details, I stopped at one number first: PTV's 64 in the first innings. After a reply of 412, being bundled out for 64 means the whole drama of the match sat inside one innings. In 2026, while keeping a travel ledger with Dhaka Abahani, I used to write beside such collapses: the travel ledger remembers the away days the scoreboard forgets. Here too the scoreboard shows a six-wicket win, but the inner ledger says PTV's one innings matters more than the victory.

The structure of this first-class match has to be kept in view. In a four-day domestic first-class game the follow-on threshold is 150 runs; in a five-day game it is 200. MIT made 412 in 88.4 overs. PTV were bowled out for 64, 348 behind. The follow-on was enforced. In the second innings PTV batted 110 overs for 394; MIT's target became 47. Read together, the story is clear: a big MIT first innings, one PTV collapse, then a long PTV resistance. But there is no toss, no pitch report, no weather detail in the account. In a first-class report, the absence of toss information after a side is bowled out for 64 is a major gap.

The most eye-catching innings is Mohammad Farooq's 130 off 101 balls, with 15 fours and 7 sixes. Strike rate: 128.7. A first-class batter usually sits in the 45 to 55 range; here 78.5 percent of the runs came in boundaries, meaning 79 non-boundary balls produced only 28 runs, a strike rate near 35. That is a boundary-or-nothing profile. Three explanations are equally possible: a very flat pitch, a weak bowling attack, or a deliberate T20-style approach. The report offers no evidence for any of them. Reading Farooq's innings as proof of international-level ball-striking would be a clear over-read.

Salman Aslam's 6/18 in 9 overs, economy 2.00, strike rate 9 balls per wicket, is extraordinary by first-class standards, but the context shrinks the figure. Against a side bowled out for 64, six wickets are more the product of a collective collapse than of sustained individual dominance. The more meaningful signal is in the second innings: on a surface where PTV made 394, Salman took three wickets. In the same match, 6/18 and three wickets are two different numbers; the second carries more weight. In MIT's first innings, Abuzar Tariq made 98 off 126 balls with 12 fours and 3 sixes; strike rate 77.8, with 67.3 percent of runs in boundaries. It was aggressive, but not as extreme as Farooq.

In PTV's second innings, Waqar Hussain made 171 off 245 balls with 24 fours and 2 sixes; strike rate 69.8. Mohammad Taimur Khan made 151 off 244 balls with 17 fours and 3 sixes; strike rate 61.9. Their boundary shares were 63 and 57 percent. Innings of 245 and 244 balls are examples of first-class patience; against MIT's 78.5 percent boundary dependence in the first innings, this is a different batting language. On the bowling side, Khalid Usman took 4/90 in 33 overs in the second innings, economy 2.73. For a domestic first-class spinner that is a control-bowling workload, not a flashy figure. In the first innings Kashif Ali and Khalil Ahmed took three wickets each, but their overs and economy are missing from the report. Without knowing who bowled under pressure in a 412-run innings and who took cheap wickets, the bowling analysis remains incomplete.

The outside reading is easy: MIT led by 348 and controlled the match, so it was a one-sided win. The arithmetic looks the other way too. The gap between PTV's two innings is 330 runs, from 64 to 394. Such a swing between the two innings of the same side in the same match is not usually proof of a permanent strength gap; it points instead to a change in pitch, a first-innings application failure, or the effect of toss conditions. MIT's 412 and PTV's 394 came at run rates of 4.65 and 3.58, broadly comparable batting outputs. The whole margin of the match sits inside PTV's 64.

The target was 47, yet MIT lost four wickets inside ten overs. That cannot be waved away as a comfortable win; either PTV's attack was sharper with the new ball, or the pitch retained some help. There is another inconsistency inside the report: one place says a four-wicket win, another says six wickets. Chasing 47 and losing four wickets makes a six-wicket win the arithmetically consistent figure. That discrepancy needs to be entered in the reporting ledger, because a wrong scoreline later becomes history.

The verdict here rests on a single-match sample. No career average, age, injury, contract or season aggregate appears in the report. So Farooq's 130 or Salman's 6/18 cannot be turned into a judgment that either will succeed at the next level. Using domestic first-class results as Test evidence is another major trap. In Dhaka's club cricket, the whispers I have heard in locker rooms say this: the locker room speaks in whispers long before the press conference does. Something similar is hidden in this Islamabad match. PTV's 394 in the second innings may restore some dressing-room confidence, but the 64 in the first innings will eat at its foundation. In Dhaka, the suitcase was a position on the team sheet; here that suitcase contains PTV's first-innings collapse.

The real test for MIT begins in the next round. If the opposition does not fold for 64, how long does their bowling plan hold? For PTV the question is inverted: is the 394 an indication of a new start, or a reaction after the 64? The scoreboard does not answer that, and I will have to go back to the ledger to find it.