Jangoo's Call-Up: A 239-Run ODI Ledger and a 120.74 T20I File

After the record chase at New Chandigarh finished, I closed the scorecard and opened a different file. The West Indies wicket-keeper batter had made 58 not out, 114 and 67 across three matches — 239 runs for the series, third-highest across both sides behind Shubman Gill and Shai Hope. Clean number, easy story. The other file carried a figure no highlight reel ever shows: a T20I strike rate of 120.74, from 163 runs in seven matches.

Amir Jangoo. Twenty-nine years old. International debut in December 2026. A late arrival in limited-overs cricket. West Indies have added him for the five-match T20I leg of the India tour — as cover, not as a first-choice pick. Jewel Andrew has a finger injury; the X-ray shows no fracture, he remains under observation, and he has not been ruled out of the series. Jangoo's status reads like a conditional contract: it shrinks if Andrew is passed fit, and expands sharply if he is not.

The ledger starts where the highlight reel ends.

A decision standing between two different games

This story sits on the border between formats. One has finished — a three-match ODI series. Another is about to begin — five T20Is. The record chase at New Chandigarh tells you the ODI surfaces were kind to batting; the ball came on, the bounce was honest. Making 239 on those decks is not a small thing, and it is not a final examination of quality either. It is a run of scores in favourable conditions. Miss that distinction and the whole analysis walks the wrong way.

The T20I leg travels to Lucknow, Ranchi, Indore, Hyderabad and Bengaluru — five surfaces, five kinds of bounce, five dew calculations. Over a five-match bilateral assignment, the decisions are made by squad depth rather than by a first XI. That is precisely where a reserve keeper's slot opens up, even if nobody in the first-choice side is injured.

Reading this selection, I kept looking towards Dhaka. The question it raises — where does a team find a keeper on a week's notice — is a familiar one in Bangladesh. BKSP, the National Cricket League, the Under-19 camps: our system files a keeper-batter from a very young age, and it writes glovework and batting into the same column. An English county academy keeps different paper, with keeping and batting in two separate ledgers and the system deciding which comes first. What West Indies have run into here is the product of neither method; it is a gap in a pipeline's arithmetic.

What the ODI ledger says, and what it leaves blank

Two hundred and thirty-nine runs across three innings, each a separate contribution — that is the strongest part of Jangoo's case. Not one flash, but consistency through a series. In the twelve-point template I built in 2026, consistency always gets its own column, because one innings belongs to luck and three belong to habit.

Some cells in the ledger are empty, though. How many balls did the 239 come from? What was the strike rate? Which position did he bat in? A pile of runs without balls faced is a photograph without a date on it. One more thing to hold: a record chase means the pitch was on the batter's side. Runs made in that environment are real, but their portability is the open question.

He finished third on the series run chart, behind Gill and Hope. That fact reads both ways. On one hand it is evidence of his consistency; on the other it reminds you that scoring runs was not a rare event in this series.

What the T20I file says matters more

Seven T20Is, 163 runs, a strike rate of 120.74. In the modern format, the normal benchmark for a top-order or middle-order batter runs from 130 to 145; a finisher sits above 150. A wicket-keeper batter is usually asked for more again, because his slot often falls at six or seven, where the balls are fewer and every ball has to pay.

Here is the central contradiction of the story: Jangoo has been called up on ODI form, while his own T20I record sits below the format's minimum standard. The stunning ODI run and the low T20I strike rate describe two different batters in two different formats.

Seven matches is a small sample, and a small-sample strike rate carries wide error bars. Tracking Pedri's 1,188 minutes for my 2026 load ledger taught me that the smaller the sample, the later the conclusion should be drawn. One good T20I series could lift 120.74 quickly. This is a caution flag, not a verdict.

Another blank cell: nowhere does it say which position those T20I innings came in. A batter walking in at six for the last two overs with a strike rate of 120 is not the same animal as a number three with a strike rate of 120. Without that information, the strike-rate argument is half an argument.

The age file: reliability, not upside

Twenty-nine puts him at the top of the batting curve and at the far end of a late arrival at international level. A debut in December 2026 means a long domestic ledger behind him — he is not a man you can sell as a rising prospect.

The frame that works at this age is not potential but short-term reliability. An experienced domestic performer who breaks less often under pressure, and whose ceiling is already broadly drawn. The stunning-form headline covers that distinction over.

In my 2026 Dhaka Youth Ledger I recorded ten metrics for 72 players born between 2026 and 2026 — minutes, touches, sprints, pass accuracy. Jangoo's file is not that kind of file. It belongs to a different register, where the question is not how big he might become but what he can give today.

The role file: gloves first, bat second

The clearest path is the keeping. A call-up as cover for an injured keeper means the primary duty is glovework, with batting as the secondary argument. That reframes the strike-rate discussion entirely — a keeper coming in at seven and facing eight balls produces a noisy strike rate, and noise is a poor way to set a format's standard.

Keeping is not only batting. Three fifty-over matches of squatting, followed by five T20Is across five cities with travel and heat — a keeper's load deserves its own arithmetic. My 2026 load ledger never counts a batter's minutes and a keeper's minutes together, because the work is not the same work.

There is an administrative side to a cover call-up that the original report does not carry: cover is normally time-limited and can be withdrawn once the incumbent is fit. Jangoo's squad status is provisional by design. What that means for match fees or contract terms is not stated, and it is better not to guess.

The contrary angle: where the three-act story breaks

The easy criticism is that ODI form cannot prove T20I value. Cross-format contamination. That criticism is right, and half right. When I see any workload claim, I separate the claim from the claimant and audit it on its own numbers; here the word form needs separating from the word transfer. Jangoo's ODI form is real. What is unproven is its transfer once the format changes. Miss that distinction and we repeat the same error from the opposite direction.

The second angle is less comfortable. I write injury comebacks in three movements — break, repair, return. That frame fits almost any career, which is its weakness. In Jangoo's case the fourth story is far more likely, and nobody writes it: the X-ray is clear, the finger settles in days, Andrew returns, Jangoo carries drinks in five cities, the series ends, and the file closes with zero matches. A cover call-up is provisional by design — a draft of a possibility, not a promotion.

What to watch

Andrew's fitness report: fit, and Jangoo sits on the bench; not fit, and he is first choice. Jangoo's batting position: top order or finisher, which sets the expected benchmark for his strike rate. And the direction of that strike rate across five matches: climbing towards 130 and the file rewrites itself, hovering near 120 and the seven-match sample becomes his identity.

In empty stadiums, the archive speaks louder than the crowd. The question in the end is this: how many careers are settled by somebody else's X-ray report? Every template hides a childhood the scouts never filed — in Jangoo's case that childhood is scattered across uncounted domestic matches nobody has read, because the figure on the top page says 120.74.