In the 22nd Match of BPL 2025-26, for a short time, this appeared to be one of those chases that will become part of local legend. The chase was for 185 runs steep; however, it is not unreasonable to expect on a pitch that gives timing. In addition, Dhaka Capitals had put the crowd on edge with late hitting. However, when the dust finally settled, the score reflected an ugly reality: 143 all out in 18.2 overs, a 41-run loss. A close loss didn’t go wrong; it fell apart tactically. It was not one poor over; it was death from a thousand small tactical cuts.
A top-order collapse that turned a chase into a salvage job
Chasing a total of 185 when your first 5 batsmen have combined to make 13 runs will be difficult. In just 4.2 overs, Dhaka lost 4 wickets for 19, and 3 of them fell to the same bowler in a matter of seconds. The 3 that were out were all caught trying to play shots on a slow pitch. However, after losing those early wickets, Mohammed Mithun & Shammim Hossain tried their best to build a foundation for their team. Unfortunately, the game was now at the point where they were fighting for survival. To successfully chase large totals, you need to have two types of batsmen in your top order (at least): an anchor who can stay and bat for long periods, and a counter-puncher who can try and get the score going quickly.
Hassan Eisakhil’s innings set a benchmark. Dhaka never truly chased
Many times, matches can be decided by a single performance, which will redefine the term “par.” In this case, it was Hassan Eisakhel’s 92 of 60 balls of pure poise and planned destruction. Initially, he absorbed the first few deliveries as they moved around, then allowed Soumya Sarkar to unleash some firepower (48 off 25) before shifting through the gears clinically. Once again, when two partnerships were lost in a mini collapse, Eisakhel did not panic and instead continued to target areas of the field and look for singles over sixes until the death overs came into play. Ultimately, Noakhali had a total of 184/7 at the end of their innings, forcing Dhaka into a risk-taking approach from the very first delivery of their reply. Compare the two sides’ methods to the way the match unfolded. At all times, Noakhali relied on its ability to assess each situation and react accordingly.
Failure to manage the middle overs and a chronic lack of finishing depth
The power play had already conceded the game; the middle overs were simply finishing the job by ensuring that the loss was complete. The bowlers of Noakhali suffocated the chase with a rotating choke hold: Hasan Mahmud (2/21), Mehedi Hasan Rana (2/25), Mohammad Nabi (2/23). It was neither express pace nor mysterious spin; it was quality lines and length, smart field placement, and relentless dot balls. At this point, Dhaka completely miscalculated the tempo of the chase. Although Mithun’s 33 from 31 was a sincere effort, it was insufficient at that point; although Shamim’s 29 from 16 came on board much later than it needed to be to make a difference in the equation. When Mohammad Saifuddin scored a gallant 34 from 20, the chase had become unattainable due to the large increase in the run rate. In addition to the issue of the run rate, there was a structural issue within the team composition of Dhaka.
FAQs
Why did Dhaka Capitals lose the match?
A catastrophic top-order collapse left them too far behind the required rate.
Who was the turning point player?
Hassan Eisakhil, whose 92 anchored Noakhali to a commanding total.
Could Dhaka have chased 185?
On this pitch, yes, but only with powerplay stability and a deeper finishing plan.
Disclaimer: This Exclusive News is based on the author’s understanding, analysis, and instinct. As you review this information, consider the points mentioned and form your own conclusions.
SA20 2025-26: Predicting top 3 player battles for match 22
BBL 2025-26: Predicting playing XI for match 33
SA20 2025-26: Predicting playing XI for match 22
BBL 2025-26: Predicting top 3 player battles for match 33
