From 5/4 to 221/7: the shape of Afghanistan's T20I recovery
Afghanistan were still 45/5 after ten overs against Zimbabwe, then scored 176 in the last ten. We checked how that recovery compares with 27 recorded early four-wicket collapses in 2026 men's T20Is.
Afghanistan did not move directly from 5/4 to a commanding total against Zimbabwe. At the end of six overs in Sharjah on 29 October they were 19/4. At the halfway point, they were only 45/5. The extraordinary part of their 221/7 came later: 176 runs in the final ten overs, an average of 17.6 per over with five wickets already down.
The Afghanistan Cricket Board's match report confirms the four-wicket collapse for five runs, the 142-run sixth-wicket partnership between Azmatullah Omarzai and Ijaz Ahmadzai, and Afghanistan's 19-run win. The ICC's account also records Omarzai's 116, the 221/7 total and Rashid Khan reaching 200 T20I wickets. Our question is narrower than a match recap: how unusual was this climb among innings that lost four wickets in the powerplay?
The late acceleration
CricChase's ball-by-ball record of the second T20I puts the fourth wicket at 5 runs after 20 legal balls. Sixteen balls later the total was 19/4. A fifth wicket fell with the score on 38 during the ninth over, and Afghanistan finished the tenth at 45/5. From that point, 176 runs arrived in 60 legal balls. The 17th over added 27 and the 20th added 25. Those two overs alone contributed 52 of the final 176.
This sequence matters because a final score can hide when a recovery happened. The sixth-wicket stand was central, but the first response to the collapse was not instant acceleration. At 45/5, Afghanistan still had to score more than three quarters of their eventual total in the back half of the innings. The score progression is observable; it does not tell us what the batters intended on any particular delivery.
How rare in our archive?
We selected completed men's T20I first innings scheduled from 1 January through 29 October 2026 UTC. Each needed a complete ball feed, a six-ball over, a scheduled 20 overs or a full 120-ball innings when the scheduled length was missing, an outright match result and no revised target. In 27 qualifying innings, the fourth wicket fell within the first six overs. Afghanistan's 221 was the only final total of at least 200; the next-largest was 184.
Nine of those 27 teams were below 20 when the fourth wicket fell. Their final totals, ordered from lowest to highest, were 18, 42, 75, 92, 103, 108, 114, 166 and 221. Afghanistan's total was 55 higher than the next-largest in that smaller group. The reproducible cohort query, result notes and over-by-over calculation show exactly how we selected and counted them.
Nine is a small, mixed sample. Teams, opponents, grounds and playing conditions differ; the fourth wicket also fell at different moments in the powerplay. These scores cannot be turned into the probability that a future side will recover from 5/4. Our database does not cover every T20I worldwide, and excluding incomplete feeds can change which matches appear. The comparison describes the scale of this innings within a defined CricChase snapshot, not an all-time ranking.
The striking lesson from the recorded sequence is about timing. Afghanistan were 5/4 early and 45/5 halfway, yet still had ten overs to build and then accelerate. The board report establishes the partnership and result; the phase breakdown, cohort comparison and interpretation are original CricChase analysis prepared with AI assistance and checked against the linked delivery data.
Conversation
Join the discussion. Replies stay attached to the article or result.
Sign in to comment, reply, or react.
Loading comments…












