Bumrah out of ENG vs IND 3rd ODI at Lord's: a knee injury sustained in Cardiff rules India's strike bowler out of the series decider

India's premier fast bowler misses the Lord's finale after picking up an impact injury to his left knee while fielding in the second ODI at Cardiff. Left-arm seamer Arshdeep Singh comes in as the direct replacement. Here is the full Adda52 read on what changes - and what to do with your fantasy XI before contests close.

How Bumrah picked up the knee injury and what the BCCI has said

India arrived at Lord's with the three-match ODI series sitting at 1-1 and the decider a few hours away, but the playing XI sheet at the toss carried the one name almost every fantasy XI in India was waiting to see - and it was not there. Jasprit Bumrah, India's strike bowler across all three phases, was ruled out of the third ODI because of an impact injury to his left knee sustained while fielding during the second ODI at Cardiff.

The Board of Control for Cricket in India released a formal update on the eve of the match confirming that the swelling around the left knee is reactive - the kind that follows a knock or a tweak in the field - and that medical staff have advised against selection for this fixture to avoid turning a manageable injury into something more expensive. The same update made clear that Bumrah is being monitored day to day, with the medical team's priority being full recovery ahead of the upcoming international assignments rather than a one-match return.

For the casual reader this reads like a small note buried in a squad update. For anyone who watched the Cardiff ODI closely, it lands very differently. India's premier fast bowler does not leave the field casually, and a reactive swelling that has not settled between ODIs is the sort of complaint that quietly rules a fast bowler out for a couple of weeks rather than a couple of days. The BCCI wording - "to prevent further damage" - is the part that tells you the management are buying time, not chasing a comeback.

The BCCI update does not say how Bumrah picked up the knock. What it does say is that the swelling has not settled, the medical staff are cautious, and there is no point pushing a fast bowler through a decider when the calendar ahead has bigger fixtures.

Why Arshdeep Singh is the direct replacement, and what that does to the XI

The choice of replacement tells you almost everything about how India are trying to balance this attack. Arshdeep Singh - a left-arm seamer with new-ball swing, a sharp bouncer and recent T20I form behind him - has been named as the player stepping in for Bumrah. The team management have not picked an all-round filler or a like-for-like right-arm quick; they have used the slot to add a different skill profile.

There is a logic to this. Lord's offers movement off the surface in the first session, and overcast English conditions are exactly where a left-arm angle forces right-handed batters to do extra work. With three right-handers likely in England's top seven, Arshdeep's angle puts the ball on a fuller line to the batter's pads and brings both edges into play. It is a different kind of wicket-taking threat than Bumrah's scrambled-seam precision, but in these conditions it can be more dangerous.

The bigger change is structural. With Bumrah unavailable, Mohammed Siraj moves up the pecking order as the senior seamer, and one of the two remaining fast-bowling slots is filled by Arshdeep. The other slot is the toss-up to watch: it goes either to a third specialist seamer or to a fourth-bowler-all-rounder, depending on how India read the Lord's surface and the forecast.

The three India changes Shubman Gill announced at the toss

India's captain confirmed at the toss that the side has been forced into three changes from the XI that played in Cardiff. Bumrah's absence is the headline, but it is only one of the three. The other two reflect the workload and combination thinking that always sits one step behind any senior-player injury.

The structure of the changes is what matters. India have not panicked. They have kept the batting core, swapped the lead seamer, and used the freed slots to add balance. That is the difference between a team that has prepared for the possibility of Bumrah missing a game and one that has not.

Why Lord's and a series decider changes the fantasy math

Lord's is one of the few grounds in the world where the venue quietly overrides form. The slope from the Pavilion End to the Nursery End forces captains to set attacking fields rather than defensive ones, and the surface typically offers enough in the first 10-15 overs to reward the side that bowls with discipline. In a decider, that pattern is sharper - captains do not play for the second innings, they play for the new ball.

The series context adds a second layer. With the series at 1-1 and India travelling to Lord's for the third match, the captain winning the toss is overwhelmingly likely to bowl first. Lord's dew can flatten the surface in the second innings and make chasing easier, and in a one-in-three-match decider, taking the safer second-innings pitch is the obvious play. That has a direct fantasy consequence: wickets fall in the powerplay and at the death, and the bowlers who bowl in those two phases do almost all the damage on the points table.

Adda52 fantasy impact: captain picks, differentials, contest picks

This is the part that matters for fantasy users on Adda52. The decision tree has three branches, and each one points to a different kind of lineup.

The first branch is the captain pick. With Bumrah out, the captain-pick universe shifts away from a single premium seamer and towards a broader spread of options. If you had Bumrah as captain, you now need to decide whether to move the armband to Siraj - the obvious like-for-like upgrade in points profile - or to a top-order batter batting first on a difficult surface. At Lord's, with the toss almost certainly favouring bowling first, top-order batters who bat in the powerplay carry the captaincy value. Do not assume the captaincy moves to the new-ball bowler by default.

The second branch is the differential. Arshdeep Singh is the obvious differential pick for the day. He comes in under-priced relative to the points he is likely to score - a left-arm seamer with new-ball swing in English conditions, bowling at right-handers, in a series decider. The selection percentage will catch up by the second ODI he plays, but on the day of his ODI debut in this format, he is the highest-upside differential on the India side.

The third branch is contest selection. A decider ODI is a high-variance game for fantasy users, but a known-decider XI after the toss is actually the easiest game to size entries on. If you have a strong read on the XI and you have read this article, you have an edge. If you do not, the variance will punish you. The practical move: keep most of your entries in head-to-heads and small leagues for this one match, save the mega contest for the matches where you are confident in the playing XI an hour before the toss.

For readers who want a fuller view of the day's news flow, the rest of our Adda52 cricket news desk tracks every change across the series as the playing XIs are announced.

A short note on vice-captaincy while we are here. The vice-captain gets 1.5x points instead of 2x, so the VC slot is the place to take a small calculated risk. If you have already locked Arshdeep as your differential, do not also make him vice-captain - keep the VC on a high-floor batter so one of your two multiplier slots is stable. The captain armband should chase upside; the vice-captain armband should chase a floor.

India's remaining pace options and how workload moves around

The second-order question is workload. Bumrah's absence does not just take his overs out of the attack; it redistributes them. Mohammed Siraj, who was already the second new-ball option, now leads the attack in terms of overs bowled. Expect him to come back for two spells - one with the new ball, one at the death - rather than the three spells India would have used if Bumrah had been available.

The third seamer's role changes too. Instead of a four-seamer rotation that gives each bowler a rest between spells, India are now running a three-seamer rotation with one of the slots held back for a part-time option or a spin bowler. That means each of Siraj, Arshdeep and the third seamer picks up around 10 overs rather than the 8 they would have bowled in a four-seamer rotation. The captaincy knock-on is that the third seamer - whoever India pick - gets a small points bump simply from the extra overs.

For the England batters the workload redistribution matters less than the skill redistribution. England's right-handed top order will face Arshdeep's angle early, then Siraj's pace at the death. The left-handed batters in England's middle order get one less right-arm angle from around the wicket to deal with, which slightly shifts their expected scoring zones. None of this is dramatic in any single match, but it adds up across a 50-over innings.

Spin also matters more than the headline suggests. With one specialist seamer slot freed up, India have more room to play two frontline spinners through the middle overs rather than the one-and-a-part-time mix they had been running. On a Lord's surface that traditionally holds up for spinners in the second half of the innings, two frontline tweakers give Kuldeep Yadav - if he is the second spinner - more overs and more match-up opportunities against England's left-handed middle order. That is a quiet points bump you should not miss on your Adda52 fantasy XI.

What the medical update actually tells us about Bumrah's next game

The BCCI's wording matters more than the headline. Three phrases in the medical update tell you almost everything you need to know about Bumrah's availability for the next international fixture.

• "Impact injury to his left knee while fielding" - the cause is a knock, not a strain. That is better news for a fast bowler than a tendon or ligament complaint, because bone-bruise-style impact injuries usually settle when the swelling settles.
• "Reactive swelling in the knee" - this is the part that matters. Reactive swelling means the knee is still irritated, and the medical staff will not clear a fast bowler through a reactive swelling until the swelling has reduced for at least 48 hours. The decider is the wrong fixture to gamble on.
• "Full fitness ahead of the upcoming international assignments" - the language is forward-looking. India are prioritising the next block of fixtures, not this single match. That tells you the recovery window is measured in weeks, not days.

Read together, the update is saying: Bumrah is not seriously hurt, but he is not fit for this match, and the medical team are not going to push him back into the side until the swelling has fully resolved. Fantasy users tracking his availability for the next ODI or T20I block should watch for two signals - the BCCI removing "reactive swelling" from the daily update, and Bumrah returning to net sessions. Either of those will arrive before any official comeback announcement.

There is also a workload layer to keep in mind. Bumrah has carried the heaviest bowling load across formats over the last 18 months, and the management has been visibly protective of his overs in bilateral series whenever a longer tournament sits a few weeks away. A one-match absence for a knee complaint reads as both a medical decision and a workload decision - the kind of call that gets easier to make when the next assignment is a higher-priority series. The right read is conservative: assume he is back for the next block, not for the next ODI.

What to do on the Adda52 app before the toss

The hour between the playing XI being announced and the toss is the most valuable window for any fantasy user on the Adda52 app. Once the XI is locked and the toss is up, contests close fast and the edge disappears. Here is a short routine to run through before you lock your team.

Step 1: confirm the XI. Read the official playing XI sheet rather than relying on rumour-line feeds. The Bumrah-out, Arshdeep-in change has to be in the app's player pool before you can pick Arshdeep - if the app has not refreshed, your pick will not register.

Step 2: check the pitch report and weather. Lord's in July typically offers early movement and a drier second-innings surface. Confirm with the on-ground report from the broadcast if you can; app pitch reports sometimes lag by 10-15 minutes.

Step 3: size your entries. Head-to-heads and small leagues first, mega contests only if you have a strong read on the XI. The decider variance is real and the contest sizes should reflect it.

Step 4: lock 10 minutes before the toss. That is the standard professional window. Anything later and you are trading time for risk; anything earlier and you are betting on rumour-line news.

Frequently asked questions on Bumrah's absence from the Lord's ODI