A Post-Mortem of T20I Win Rates: Uganda Above India, Bangladesh Nowhere

November 2026, Windhoek. Uganda beat Zimbabwe in the Africa Region Qualifier and qualified for a T20 World Cup for the first time. I was in Hyderabad that night, scrolling scorecards at four in the morning, because I could not square the result with what I knew about the two teams. One squad has full-time contracts, a support staff of dozens and a domestic T20 league. The other has men who train before work.

Three days later a screenshot reached my phone. A stats account had posted a table of T20I win percentages, filtered to teams with at least fifty matches. Uganda sat above India. Bangladesh sat below fifteen or sixteen sides. The comments split into two camps: one saying "see, T20 has flattened everything", the other saying "rubbish table, Associates can't beat anyone".

Both were wrong, and wrong in the same lazy direction. The table was not lying. It was reporting a truth whose every digit was measuring something other than strength, and readers were treating it as a certificate of quality. Slow it down and the story changes. A win percentage is not a merit badge; it is a ratio, and its denominator is written by schedulers, not by selectors.

Context: how this table came to exist

Before 2026 the T20I door was narrow. The ICC granted T20I status to all men's member teams from January 2026, and that single decision split the statistical world in two. Matches that were once just "T20" became official T20Is, and the pool of teams playing them crossed a hundred. An Africa sub-regional qualifier gives eight or ten teams eight or nine matches each, and that carnival runs two or three times a year. Uganda, Tanzania, Rwanda, Botswana and Nigeria began adding fifteen to twenty official T20Is a season.

Now look at Bangladesh's calendar over the same period. It is divided into four or five series a year—Asia Cup, World Cup, bilateral tours—and almost every opponent is a Full Member or a top-ten Associate. India's schedule is harsher still, because every side picks its best XI against India, and even preparation is scheduled against Australia, England and South Africa.

There is an arithmetic truth here that no win-percentage table can hide. Play twenty matches a year against sides you beat seventy per cent of the time and your five-year win rate drifts towards seventy. Play fifteen matches a year against sides you beat half the time and your rate sticks near fifty, however much your team improves. The table does not tell you how good you are. It tells you who you were sent to play.

The ICC rankings partly correct for this, weighting every result by the opponent's rating. But the account that builds the screenshot does not post rankings. It posts the raw percentage, because raw numbers look clean and start arguments.

Core: the error the table makes

I went looking for the mistake and found the system. The mistake belongs to the metric. A T20I win percentage has a numerator drawn from one world and a denominator drawn from another, and weighing them on the same scale is like crediting a batter's runs to the size of the boundary rope.

Uganda's case is interesting precisely because it is not only a schedule artefact, though most of it is. The bulk of Uganda's wins over the last six or seven years came in Africa sub-regional events against Rwanda, Tanzania, Nigeria, Botswana, Malawi, Lesotho and Kenya. Those matches are real, they carry T20I status, they enter the record. The gap in quality between them and an India fixture cannot be closed by a percentage, because the percentage hides the gap in the same stroke.

Then watch the same Uganda in Windhoek, against Zimbabwe. In that one match the bowling did what any bowling side should: wickets with the new ball, a squeeze through the middle, pressure held through the last five overs. Alpesh Ramjani's economy through that tournament was no worse than a Full Member's third spinner. Frank Nsubuga did the hardest job in Associate cricket—bowling in the powerplay, conceding little and taking wickets. Riazat Ali Shah and Simon Ssesazi gave the batting a tempo that was not merely regional standard.

That is where I had to revise my first conclusion. Uganda's win rate is largely schedule—true. But that schedule gave Uganda the chance to become a bowling unit that actually works, and no other route offers that chance. In Associate cricket, playing is the training. Uganda has fewer T20Is than Bangladesh, but enough to test every bowling plan three times in three years.

Core: Bangladesh's real illness

Bangladesh's win rate sits around forty to forty-two per cent across roughly 250 T20Is. That number looks worse than it is, because the schedule behind it is almost entirely Full Members. Drop Bangladesh into Uganda's calendar and its win rate crosses sixty and it climbs the same table. That does not dissolve Bangladesh's problem, because the problem is not in the table; it is on the tape.

Slow it down and the story changes. Bangladesh's T20 batting has rested on an anchor at No. 3 who bats to the fourteenth over while the rest repair his slow start in the last six. That model worked in 2026-2026, when 160 was a winning score. Today 160 merely keeps you in the contest. Bangladesh's T20I batting strike rate stayed near 125 for years while the top eight moved past 135 collectively. Their powerplay totals often landed in the low forties while the modern standard crossed fifty.

That is the on-tape error. But I went looking for the mistake and found the system. The question is not why Bangladesh's batters are slow. The question is why the selectors keep picking slow batters. The answer sits in the domestic structure. Dhaka pitches are slow, 150 defends there, and the domestic T20 tournament rewards the batter who bats through. A selection system that pays for domestic success produces a national side with the same profile. For years the T20 team was a gathering of Test and ODI stars sent to play T20 series between bigger assignments.

The same logic applies to the calendar. Bangladesh's T20I schedule is mostly bilateral, and many of those series are hosting obligations rather than preparation. At the 2026 T20 World Cup Bangladesh reached the Super Eight—its best result—and that achievement outranks any table. In the Super Eight all three matches went one way, because its batting tempo could not survive that standard of bowling.

Core: India's sixty per cent and Uganda's sixty per cent are not the same object

India's T20I win rate sits above sixty per cent, and it was built in a world where nearly every opponent comes from the top eight. The number is extraordinary because the pool is unforgiving. The final at Bridgetown on 29 June 2026 is the cleanest example: shutting South Africa down in the last five overs was the work of a system, not a miracle. Jasprit Bumrah's spell that night belongs to the same sequence I have kept in my clip bank since the 2026 IPL final.

If Uganda's win rate appears above India's, it does not mean Uganda is the better T20 side. It means the denominators differ. India's fifty is harder to earn than Uganda's sixty. The cleanest test is a hypothetical switch: hand Uganda India's schedule—Australia, England, South Africa, Pakistan, New Zealand every year—and ask where the percentage lands. My estimate is the low twenties to low thirties. I base that on batting depth, not bowling quality. Uganda's attack can hold a top side for two or three overs; its batting will not survive twenty overs against pace on bigger grounds.

Here is the table's deepest wound: it ranks teams in one queue when the real world has a staircase, and the steps are cut from schedules, not talent. Tanzania, Rwanda and Botswana appear high on such lists for the same structural reason.

Core: the price-and-role lesson

I keep a sheet I call the role ledger. Every auction bid buys a role—powerplay enforcer, death-overs spinner, No. 4 anchor—and my job is to check at season's end whether the cheque and the role matched. The same reasoning transfers if you change the scale. A win percentage is a price; it tells you what the market thinks you are worth. The real question is which role that price was paid for.

Bangladesh's role was set by its calendar: stand in front of the top eight at every major event and be expected to beat one or two of them. Graded against that role, its win rate is not as bad as it looks, though its knockout conversion is poor. Uganda's role is different: dominate the Associate pool, and it does. Both earn different grades in different jobs, and one table lines them up in the same queue.

Contrarian: where I could be wrong

I opened by saying both camps were wrong. Now I attack my own.

Assuming every Uganda win is a schedule effect is as careless as assuming the table is a lie. If Uganda's record is only African sub-regional matches, we should strip them out and look. If Uganda has won more than half its matches against Full Members and top-ten Associates over the last three years, my argument collapses. There are concrete reasons it might. The Zimbabwe win was no fluke—Uganda's attack carries a discipline several Full Members lack. Ramjani's economy and Nsubuga's experience is a pairing that keeps any side in the contest for fifteen overs.

Second, dismissing raw win percentage as a useless metric is dangerous for Associate cricket. It is the only window those teams have. They have no broadcast deal, no big bilateral contracts, and their ICC funding is argued from performance. If I wave the table away as "just scheduling", I am speaking the language of the people who diminish every Associate win as a weak-opponent result. That would be my error.

Third, and most important—the table being wrong does not rescue Bangladesh. I have changed the explanation of its problem, not removed the problem. The powerplay strike rate, the anchor model, the slow domestic pitches are all real, and no schedule argument defends them. If Bangladesh does not push its powerplay run rate above 8.5 within two years, its win rate will stay near forty regardless of how hard the calendar is.

Fourth, a counter-argument that may date my whole piece. The twenty-team World Cup of 2026 handed Associates a stage they never had. When the Netherlands can beat South Africa and Scotland can trap anyone on a given day, "their schedule was weak" loses legitimacy by the season. My schedule argument is correct today and may be obsolete in three years.

Takeaway: how to read this table next time

Here is a prediction with a test attached. If Bangladesh does not lift its T20I powerplay strike rate towards 140, its 2026 World Cup will again stop at the Super Eight and its win rate will stay under 45 per cent. Second prediction: Associate sides of Uganda's type will beat at least two Full Members at the next World Cup, and after that day the win-percentage table will have to be split into schedule-weighted layers before it means anything.

The auction sheet says Rs 11.5 crore. The tape says something else. Here the scorecard says Uganda above India; the schedule says something else. Reading either alone is the mistake we have made for twenty years. The real question is not who is on top. It is how many matches against what kind of opponent a team needs to look like it belongs there—and until we answer that, every table sells an illusion, whether it lifts Uganda or buries Bangladesh.