Jangoo's T20I Call-Up: The Gap Between 239 ODI Runs and a 120.74 Strike Rate

Last week, after West Indies' innings ended on the New Chandigarh pitch, one name kept returning to the scorecard — Amir Jangoo. Fifty-eight not out in the first ODI, 114 in the second, 67 in the third. Two hundred and thirty-nine runs across three innings, the third-highest run-scorer across both teams, behind only Shubman Gill and Shai Hope. The ODI leg of the India tour was, for Jangoo, a near-perfect audit report. But my hand stops right there. Because the batter being called into the T20I squad on the strength of "stunning form" has an existing T20I ledger that tells a different story. Seven T20Is, 163 runs, a strike rate of 120.74. The modern T20I benchmark for a top-order or wicket-keeper batter is 130 to 145; for finishers, above 150. Jangoo sits below that line. So the question is not simple. The real question is whether the 239 ODI runs and the 120.74 T20I strike rate are two different batters speaking two different languages — and whether we are reading them as one. I built the Rajshahi xG ledger one match at a time, and the first lesson was patience. In 2026 I hand-coded all 42 matches of the Rajshahi Premier League, logging 3,780 shots, separating every shot's angle, distance and defensive pressure. That ledger taught me that a number never speaks alone — format, pitch and situation must be placed behind it. Change the format and the language of the maths changes too. That is exactly what is happening here. A record successful chase occurred at New Chandigarh, which means the pitch was batting-friendly, true-bounce, the ball coming onto the bat. Scoring 239 runs on such a deck is creditable, but it is easier than the same output on a track offering spin or swing. And the T20I series moves through Lucknow, Ranchi, Indore, Hyderabad and Bengaluru — five different Indian venues, five different behaviours. A five-match series means squad depth, not just a first XI, is decisive. Jangoo's call-up is not straightforward either. He arrives as cover for injured keeper Jewel Andrew, and Andrew has not yet been ruled out. This is not a first-choice selection; it is a contingent addition. One confusion must be cleared up here, because it is the heart of the whole story. ODI and T20I are not the same game — they are two separate books of account. In ODI, 50 overs give room to build an innings; a batter can start slowly and finish explosively, earning average and innings-building value. In T20I there is no time — across 20 overs, strike rate and boundary-hitting are the primary currency. The very metric that earns praise in ODI can be a barrier in T20I. Jangoo's ODI series is genuinely strong — 239 runs spread across multiple innings, not a single-innings fluke. But three innings is a small sample, and runs made on batting-friendly pitches generally give a weaker signal than runs on difficult tracks. His T20I ledger, meanwhile — 7 matches, 163 runs, 120.74 — is clearly below par on strike rate. This is cross-format contamination: the error of using success in one format to prove value in another. My Rajshahi rule was simple — one innings is never a decision, only an entry. In 2026, sitting in Russia, I tracked 64 matches and 1,842 shots; in Croatia's 3-0 win, Argentina's PPDA rose to 18.4, proof their press had collapsed. That desk taught me no decision holds without format-specific metrics. Russia 2026 taught me that a data desk is a war room with better coffee. Now, what is the real logic behind Jangoo's selection? Not strike rate, but glovework. He is a wicket-keeper batter, and being called up as cover for an injured keeper means his primary job is the gloves, with batting the secondary case. Here the gap between media framing and data truth is clearest. Why does this matter? Because in T20I, a wicket-keeper batter is a scarce, premium category. If someone enters a T20I squad purely on the glow of ODI runs while carrying a strike rate below 130, a gap opens between expectation and output. West Indies' keeper-depth fragility also surfaces here — one injury forces a mid-tour call-up. Elite sides normally carry redundant keeper cover; that necessity is itself a squad-structure signal. Let me also separate out the venue factor. Five matches in India, a hostile environment for West Indies; heat, dew and travel make workload management vital for a keeper. So rotation is natural here, and Jangoo may get game time even without a first-choice place. There is another layer. A 29-year-old with a December 2026 international debut means he is not a young prospect but a late-blooming, experienced domestic performer. That reduces development upside but increases short-term reliability. The "stunning form" framing hides this nuance. Now the counter-angle. Suppose Jangoo plays a superb T20I series and his strike rate crosses 140. Does that make his 120.74 irrelevant? No — but the limits of the sample must be remembered. In a seven-match ledger the margin of error is wide; one hot series can lift a strike rate quickly. So a low strike rate is a caution flag, not a final verdict. The reverse is also true: the media's adjectives — "stunning", "sparkling", "spectacular" — come from ODI, not from T20I metrics. Where the framing is warm, the data is cold. And since the call-up is contingent — it ends the moment Andrew is fit — this story has a built-in expiration trigger. One more thing to keep in mind. Jangoo sits in T20I with that 120.74 strike rate. It is no disaster, but it is also not the basis of a star narrative. The truth is he has not yet built his T20I identity, and one series could change it. But treating that possibility as success in advance is the work of media framing, not of analysis. So what do we watch going forward? Two signals. First, Jewel Andrew's fitness — if he is fit, Jangoo sits on the bench; if he is out, Jangoo is first choice. Second, the trend of Jangoo's strike rate — across five matches, is it climbing toward 130, or stalling near 120? Until this ledger fills, patience is required: repeat, reconcile, and never trust a single match.