Amir Jangoo's 239 Runs and a 120.74 Strike Rate: The Format Trap Inside a T20I Cover Call-Up

New Chandigarh (Mullanpur) hosted the third ODI, and that scoreboard still sticks: West Indies pulled off the tour's record successful chase. Amir Jangoo made 67 in it. The next morning's headline was not about the chase — it was about a call-up, and the call-up was for a different format. The numbers are plain: 58*, 114, 67 — 239 runs across three innings, the third-highest run-scorer on either side, behind only Shubman Gill and Shai Hope. That tally is the stated basis for Jangoo's selection. My first objection is not about taste; it is about method. ODI runs cannot certify T20I value. Two formats, two skill sets, two different measuring sticks. I call the error format contamination. The context needs spelling out. West Indies are on tour in India: a three-match ODI series is done, a five-match T20I series is next. Those five games sit at five venues — Lucknow, Ranchi, Indore, Hyderabad, Bengaluru. Away from home, in front of Indian crowds, against a home side captained by Shubman Gill, this is not an easy T20I assignment. Jangoo's three innings came in three different matches and three different situations: an unbeaten 58 carrying the side, a 114, and a 67. This is not a single flash — it is series-long consistency. Consistency scores high on my checklist; one innings of 114 is often luck, three innings totalling 239 is closer to skill. But the value of that consistency depends on the surface, and that is where the audit stops. Look at the squad. Jangoo was called up as injury cover, after regular wicket-keeper Jewel Andrew hurt a finger. The X-ray showed no fracture, but Andrew remains under observation and has not yet been ruled out. The call-up is therefore conditional. A cover call-up is usually temporary; once the incumbent is fit, the slot can vanish. Jangoo's squad status is provisional by design. Let the record speak. Jangoo's T20I record reads: seven matches, 163 runs, a strike rate of 120.74. In the modern format that sits below par for a top-order or middle-order batter. Top-order batters are generally expected to strike at 130 to 145; finishers push past 150. For a wicket-keeper batter, 120.74 sits well behind expectation. The stunning ODI form and the below-par T20I strike rate describe two different cricketers. My method delivers every claim in three beats — rule, replay, verdict. Rule: in T20 cricket a batter is priced by strike rate and boundary rate. Replay: seven T20Is, 163 runs, strike rate 120.74. Verdict: the sample is small, but the rate is below expectation. That is exactly where editorial framing and data split apart — the headline says stunning form, the number says below expectation. Does that make the 239 runs false? No. But its readability is open to question. A series that produced a record chase at New Chandigarh was played on batting-friendly pitches, which makes scoring easier. Two hundred and thirty-nine runs on a seaming track carry far more signal than the same runs on a flat deck. Scoring away from home, without home-ground advantage, is a mild positive — no doubt. But the help came from the pitch, not from a hostile bowling attack. Jangoo is 29, and his international debut came last December. That matters. He is not a young prospect; he is a mature domestic performer who has been given a late look. That fact weakens the rising-star narrative but strengthens another dimension — short-term reliability. An experienced 29-year-old reads situations; yet standing at the batting peak of 27 to 33, his room for development is limited. Now the central question: why is he in the squad? The announcement lists him as a wicket-keeper batter. His first job is the gloves; batting is the secondary case. As cover for an injured keeper, his clearest selection value is service behind the stumps. The media narrative runs the other way, putting all the weight on batting, and specifically on ODI batting. That inverted priority pushes readers toward the wrong expectation. The nature of the five venues matters. Lucknow, Ranchi, Indore, Hyderabad and Bengaluru are generally batting-friendly, though the amount of turn varies by ground. Evening dew makes bowling harder still. In that environment a keeper's work is not only catching — it is standing up, gathering low, being quick beside the stumps. Five matches of keeping in Indian heat is a physical examination. Everything I have written since 2026 stands on a checklist. For Jangoo, my checklist has four boxes — batting position, venue, sample size, format. Three of the four are currently unknown or unfavourable: his T20I batting position is not fixed, the venues are Indian pitches, the samples are small on both sides, and the format is shifting from ODI to T20I. At sixty-eight, I have been wrong before, so I built a checklist that argues back. That checklist is what tells me you cannot merge two formats' data into one verdict. — Root: 40-Point Eye / Referee On squad structure, one signal is clear: West Indies' keeper depth is thin. One injury forces a mid-tour call-up from outside the group. Elite sides usually carry redundant keeper cover. The cover call-up is therefore an admission of a structural weakness, and it is a story about team planning more than about Jangoo's individual merit. At the rules desk, forty-seven clips are not noise; they are testimony. Here too — a single call-up proves nothing on its own, but it testifies to squad depth. Procedurally, the call-up is routine. Injury cover is a recognised mechanism under ICC and board selection rules; there is no breach, no eligibility dispute, no integrity flag. One nuance remains: cover is not the same as a regular squad member. A cover place is usually time-limited and can carry different match-fee or contract implications. The article does not detail those terms — there my information is insufficient. There is one soft industry signal the headline misses. A 29-year-old wicket-keeper batter earning a look on the back of a consistent ODI series is a message from the domestic pipeline: experienced, format-versatile performers still hold value, not only young T20 specialists. A second, unstated thread: wicket-keeper batters are a scarce, premium IPL auction category, and a strong T20I series could lift his auction visibility. The transfer market has rules too, even when the ink is still wet. But the article does not mention the IPL once, so this is directional inference, not a verdict. Now the counter-side, because a referee's eye can confuse certainty with evidence. Jangoo's strike rate is 120.74, but the sample is only seven matches and 163 runs. On such a small sample the error bars are wide; one good series could push it past 130. A keeper batting lower down is not judged by strike rate alone — match situation, team need and the fall of wickets enter the count. And the warm adjectives are not false; the problem starts when they speak louder than the data. The forty-point eye does not blink at contact; it counts it. And in that count, the two formats must be kept in separate ledgers. The real risk is not Jangoo's batting form but the expectation built around his name. If he plays and bats near a strike rate of 120, the ODI-star narrative collapses — the very narrative that has just been built. The other direction exists too: five matches, five venues, Indian heat, evening dew, keeper workload. Rotation is inevitable in that environment, and rotation can open a path onto the field. A cover call-up is a two-door room: one door may close when the incumbent is fit, another may open if he is not. Pull the clip, mark the angle, then let the rule speak. Over the coming weeks four things must be watched: whether Jewel Andrew is passed fit; which position Jangoo bats in if he plays; whether his strike rate climbs toward 130; and whether the T20I pitches favour batting or spin. Without answers to those four, no final verdict on Jangoo can be written. The 239 ODI runs are real; the only question is whether that truth opens the door to another format.