Amir Jangoo in West Indies' T20I Squad: The 104.25 Strike-Rate Question Behind an ODI Century

Fifty-seven off thirty-four. Four fours, three sixes. A strike rate of 168. Amir Jangoo's innings in the Caribbean Premier League final is now the single biggest piece of evidence in the hands of West Indies' selectors. Across the tournament he made 213 runs at a strike rate of 107.57 — which means the final innings sits far above his own tournament average. And immediately before that, on Indian soil in the ODI series, he made 58*, 114 and 67 — 239 runs, third-highest of the series.

Now set the numbers side by side. Seven T20Is, 163 runs, a strike rate of 120.74. Across his whole T20 career, 34 appearances, a strike rate of 104.25. In modern T20, par is roughly 130-140; for finishers it is above 150. The player West Indies are calling up for the India T20I leg does not meet the format's first requirement.

That is the real story — not the squad change, not the injury, but a format mismatch buried beneath the headline. In Barishal I learned that the fee is never the story; the story sits in the ledger behind it. Here the headline says "cover", but the ledger says something else.

Let me set the context. West Indies are on tour in India. All five T20Is are on Indian soil — Lucknow, Ranchi, Indore, Hyderabad and Bengaluru. The series begins just as the ODI leg has ended, and that leg's scoring hierarchy speaks for itself: Shubman Gill topped it with 334 runs, Shai Hope second with 278.

That is where Jangoo's call-up comes in. Nineteen-year-old wicketkeeper Jewel Andrew injured a finger taking a catch to dismiss Naman Dhir. Hospital scans showed no fracture, but Cricket West Indies stated clearly that he remains under the medical team's monitoring. For a wicketkeeper, the hands are the primary asset — so "no fracture" does not mean "fit"; it means only that the worst outcome was avoided.

Against that backdrop Jangoo has been added as cover. The word matters — cover. He is not being pencilled into the XI; he is insurance. But the question is this: if West Indies' batting depth were genuinely sufficient, would a man who just scored an ODI century be needed as T20 insurance at all? I have watched this pattern for years: when a team says "this is only cover", it is usually confessing a shortfall. Injury, format transition, host advantage — this series carries three layers of pressure for West Indies. At the centre of that pressure sits a 29-year-old batter whose century in one format cannot settle the ledger in another.

Strike rate: the first language of T20

Strike rate is the only indispensable currency of T20 cricket. Score 120 off 120 balls and you are a debtor in the modern batting economy; score 120 off 80 and you are an asset. Jangoo's T20I strike rate is 120.74 — he sits exactly on the edge where a team can carry him but cannot accelerate through him. Strike rate is not just a number; it reveals which balls a batter scores from, which he wastes, and how much risk he will take under pressure.

One thing needs clarifying, because many readers — and some commentators — conflate the two. An ODI 114 is not a T20I 114. In 50-over cricket there is time; you can bat slowly for 20 balls and accelerate later because 50 overs remain. In T20 there is no such time. This is exactly the format-transfer problem: a batter's 50-over skill does not automatically convert into 20-over skill. And the most reliable indicator of that failed conversion is strike rate.

What the data says, what the headline hides

Jangoo's ODI series was genuinely excellent — a century, a fifty, 239 runs. Anyone who says "he scored against India on Indian soil, so he deserves the call" is not making an incomplete argument. But it is incomplete. Because the same player's T20 record reads: seven T20Is, 163 runs, strike rate 120.74; overall T20, 34 matches, strike rate 104.25; and CPL 2026, 213 runs at 107.57.

The CPL figure matters especially, because it is being used as his strongest credential. But a 107.57 strike rate across a full tournament is below the modern Caribbean T20 benchmark. And the 57* off 34 in the final (strike rate 168) is a single innings that flatters the aggregate. I call this the selectorial expression of recency bias: the final is recent, so it carries the most weight; but a batter's true ability is measured across the whole tournament. By that measure, Jangoo is a long-format player — his value has come in ODI centuries and Test-style accumulation, not in T20 tempo.

I have built a habit over years of reading batters' scorecards — not just the final tally, but which phase the runs came in. If someone bats the powerplay at a strike rate of 45, he is holding his team back, even if he finishes at 140. In T20 that masking is easy, because a few late sixes can make the overall strike rate look respectable. With Jangoo we need the internal picture, not just the aggregate.

Keeper depth: the shortfall an injured finger exposed

Now the structural truth. Jangoo's call-up is not about batting — it is about wicketkeeping. Once Andrew was hurt, West Indies had to bring in a specialist keeper-batter from outside the squad. That single event exposes a system problem: the team's wicketkeeping redundancy is very thin. In a five-match series where every game needs a keeper, one injured finger forcing an external call-up is not a selection problem — it is a planning problem.

Here I want to draw a comparison, carefully. In football a transfer fee is never merely a price — it is a confession the market writes about itself. €222 million was not a valuation; it was a receipt a broken market issued in its own name. But in cricket the same event occurs inside a different structure. Football has high labour mobility — a player can change clubs mid-season, so clubs paper over shortfalls with fees. Cricket's national squads are locked for a series, mobility is lower, so a single injury requires an outside call-up — and that call-up becomes the declaration of the shortfall. Where football hides its gap with a fee, cricket reveals its gap with a cover call-up. The two economies are different; the comparison is a mirror, not an equivalence.

And the revelation here is plain: one finger, a five-match series, one alternative. That is West Indies' keeping equation. Yet West Indies are two-time T20 world champions — we do not expect this kind of planning from that side. That mismatch is the loudest signal to me: a gap has opened between the team's reputation and its current structure.

India's advantage and Gill's form

There is another layer buried under the call-up news: all five matches are on Indian soil. West Indies are the away side throughout. India's home advantage is not merely weather or crowd; it is a structural asymmetry — pitch behaviour, dew, short boundaries all favour the host. My experience says that in India in October, batting heaven and spin hell sit so close together that the toss decides roughly half the matches.

On top of that, Gill topped the ODI series with 334 runs. India's key batter enters the T20 leg in form. Between an in-form opposition batter and a keeper still fighting his own T20 strike rate stands this series. It is a lopsided fight for West Indies — and within that lopsidedness, the call-up of a strike-rate-limited batter may be papering over the team's biggest tactical weakness.

Dew and the October question

On Indian October evenings dew is a familiar factor. A wet ball kills spinners' grip, reduces second-innings bowling control, and generally favours the chasing side. This is absent from the original news but tactically important: if batting is easier second, the toss and strike tempo gain value. And strike tempo is precisely where Jangoo is weakest. I have seen many matches where dew-affected second innings added 10-15 runs to chases purely through strike tempo. Those extra 15 runs decided the game.

The selection dilemma

Put together, West Indies face a delicate dilemma. If Andrew is cleared, one of two keepers must be dropped — but which? The ODI in-form Jangoo, or the younger incumbent Andrew? A pleasant problem on one side, a distraction on the other. And if Andrew is not fully fit, Jangoo may have to bat in the top order — and the old strike-rate ledger returns.

I have watched many matches where a team picked a keeper for batting depth and lost powerplay tempo. If a batter with a 104.25 strike rate opens, the run rate required in six overs will not arrive. This is not moral criticism — it is arithmetic. And arithmetic never knows emotion.

Where I could be wrong

Now let me stand against my own argument, because the case for Jangoo is real — and not weightless.

First, the sample is small. Only seven T20Is, 163 runs. Around a 120.74 strike rate in a sample that size there is wide variance; it is directional, not definitive. A batter can change his strike rate over eight or ten innings, especially if he has just found a format's rhythm.

Second, that 57* off 34 in the final is not weightless. Under pressure, in a trophy fight, he showed he can accelerate. A CPL final is exactly the stage where T20 temperament is tested. If that single innings is the true signal — and the tournament average is rather the product of slow pitches and poor conditions — then my whole argument weakens. I concede that strike-rate-centric analysis sometimes writes the crime of a slow pitch into a batter's name.

Third, and most important: Jangoo is probably being picked as a keeper, not a batter. He is insurance — Andrew's alternative. If he never plays the XI, his strike rate is irrelevant. In that case my criticism loads an unnecessary weight onto a squad-news item. I am willing to concede that.

Fourth, I may be falling into my own favourite trap. In T20 analysis "strike rate" has become a sacred number with which any selection can be dismissed. But keeping, batting depth, team balance — these have value beyond strike rate. Whoever looks only at strike rate sees half the story.

I watched Germany fall in ninety minutes and kept the receipt — but that receipt taught me that collapse never comes from a single cause. The same here. If Jangoo's call-up fails, the cause will not be strike rate alone — it will be squad construction, format-transition pressure, and an injured keeper's uncertainty.

The forward ledger

So what is the testable prediction? My arithmetic says that if Jangoo plays regularly in the top order this series, his strike rate will sit below 120 — and West Indies' powerplay run rate will sit below their average. But if he remains keeper-insurance only, those numbers will never be tested, and that is West Indies' safest path.

The real question is not about Jangoo. It is this: when a team keeps its keeping depth so thin that one finger rewrites the whole series ledger — is that a selection problem, or a structural one? And every transfer, every call-up, is a confession written in instalments and add-ons — we only have to know how to read it.