Trent Bridge had seen enough before India’s chase even reached the halfway mark.

England had already done their job with the bat, posting 201-7 after Phil Salt gave the innings authority, Jos Buttler supplied early force, and Sam Curran finished with calm aggression. The chase demanded clarity, courage, and control from India. Instead, it produced panic.

India were bowled out for 76 in 11.4 overs, losing by 125 runs. According to the full scorecard available on ESPNcricinfo and live score updates on Google Cricket feeds, this is now India’s worst ever defeat in T20I cricket by margin of runs.

For a team with India’s depth, talent pool, and financial muscle, this was not an ordinary bad night. It was a public breakdown.

For more coverage of international cricket, visit The Sports Encounter’s Cricket Hub.

TL;DR

• England beat India by 125 runs in the 3rd T20I at Trent Bridge, Nottingham.
• England posted 201-7 after Phil Salt’s 70, Jos Buttler’s 36, and Sam Curran’s unbeaten 41.
• India were bowled out for 76 in 11.4 overs, their worst T20I defeat by runs.
• Jofra Archer and Josh Tongue destroyed India’s power play, taking five wickets between them before the chase had any shape.
• India’s top order collapsed again after another confused batting display.
• England now lead the five-match series 2-0 after the opening match was washed out.

Scorecard and Key Information

Detail	Information
Match	England vs India, 3rd T20I
Result	England won by 125 runs
Venue	Trent Bridge, Nottingham
Date	July 7, 2026
England Score	201-7 in 20 overs
India Score	76 all out in 11.4 overs
Top Performer	Phil Salt, 70 off 44 balls
Bowling Impact	Jofra Archer and Josh Tongue broke India inside the power play
Turning Point	India collapsed to 52-5 after five overs
What It Means	England lead the series 2-0 and India’s T20I reset looks increasingly unstable

England’s 201 Was More Than Enough After Salt Sets the Base

England’s innings had balance even when it was not perfect.

India won the toss and chose to bowl first, a decision that looked reasonable for a short period. Arshdeep Singh began with rare control, and England did not immediately run away with the game. The innings changed once Buttler and Salt found rhythm.

Buttler’s 36 from 21 balls gave England an aggressive launch. He attacked early, forced India to adjust their fields, and helped England move through the first phase without being trapped by the new ball.

Phil Salt then turned England’s innings into a proper match-winning platform. His 70 from 44 balls included seven fours and three sixes, and it came at exactly the right tempo. He did not throw away the start. He stretched the innings deep enough to make India chase the game.

Salt’s dismissal at 158-5 in the 17th over briefly gave India a chance to keep England below 190, but Sam Curran closed that door.

Curran’s unbeaten 41 from 24 balls was the finishing hand England needed. He found gaps, punished anything loose, and helped England cross 200 despite a few late wickets and run-outs. Will Jacks added a useful 14 from seven balls, while England’s lower order kept the board moving.

India’s bowling had moments. Prince Yadav, brought into the side in place of Ravi Bishnoi, finished with 2-30 on debut. Harshit Rana picked up two wickets as well. Still, England’s 201-7 told the real story. India had taken wickets, but they had not controlled the innings.

For readers following the wider series, England’s win came after Jacob Bethell’s match-winning effort in Manchester. Read more in The Sports Encounter’s report on Jacob Bethell inspiring England’s victory over India in the 2nd T20I.

Archer and Tongue Turned the Chase Into a Wreck

India needed a sharp start. They got a collapse.

The target was 202, but the chase was effectively dead after five overs. Jofra Archer and Josh Tongue bowled with pace, bounce, and purpose. India’s top order answered with rushed shots, loose judgment, and the kind of batting that looked aggressive only on the surface.

Abhishek Sharma began with intent, hitting Tongue for six, but he soon fell for 10. Vaibhav Sooryavanshi briefly flashed his talent with two sixes in a 13-run cameo, yet Archer hurried him with pace and bounce. Ishan Kishan made 13 but picked out the fielder. Shreyas Iyer’s dismissal for 5 was one of the ugliest moments of the chase because the captain needed to calm the innings, not add to the chaos.

Axar Patel came out swinging and made 10 from four balls. His wicket left India 52-5 after exactly five overs.

That was the match.

Archer and Tongue’s first five power-play overs produced five wickets for 52 runs between them. Archer had 3-29 from his first three overs. Tongue struck three times in his opening spell and kept hitting the hard length that India’s batters kept misreading.

The bowling was outstanding, but India helped England far too much.

India’s Top Order Played Brainless Cricket When Calm Was Needed

This was not fearless cricket. It was careless cricket.

India’s top order never looked interested in building a chase. Abhishek, Sooryavanshi, Kishan, Iyer, and Axar all fell before India had completed six overs. Some shots came from pressure. Others came from poor awareness. A few were simply awful choices for the match situation.

A 202-run chase does require risk. It also requires thought.

India’s batters looked as if they wanted to win the match inside the power play. That mindset might create highlight clips on a good day, but against Archer and Tongue on a lively Trent Bridge surface, it became self-destruction.

Shreyas Iyer’s wicket will invite the most scrutiny. Captains are judged harshly in collapses, and rightly so. When the top order is falling around him, the captain has to bring a little sense to the crease. Instead, Iyer played a poor leg-side shot and gave England another easy moment.

Tilak Varma, Harshit Rana, Shivam Dube, Arshdeep Singh, Prince Yadav, and Varun Chakaravarthy were left with a chase that no longer existed. India eventually folded for 76 in 11.4 overs.

For wider context on India’s recent struggles, read The Sports Encounter’s analysis of India’s defeat against England in the 2nd T20I.

Selection Chaos Continues for India

India’s defeat at Trent Bridge cannot be separated from the larger pattern.

They have now lost four of their last five completed T20Is. That run includes a whitewash against Ireland and two straight defeats in England after the opening match of this series was washed out.

The numbers are bad. The cricket looks worse.

India’s selection thinking continues to look unsettled. The batting order has changed, the balance of the side keeps inviting debate, and the role clarity is poor. Vaibhav Sooryavanshi is an exciting young talent, but India cannot simply depend on teenage fearlessness to solve senior-level batting problems. Ishan Kishan has not given India enough stability. Abhishek Sharma remains dangerous, yet his shot selection under pressure remains a concern. Iyer’s leadership is now under serious examination.

Axar Patel’s promotion, Harshit Rana’s batting position ahead of Shivam Dube, and the overall shape of the order all raised the same uncomfortable question: did India know exactly how they wanted to chase 202?

At Trent Bridge, the answer looked painfully clear.

They did not.

India’s Worst T20I Defeats by Runs

India’s 125-run loss to England is now their heaviest T20I defeat by runs. The previous worst was an 80-run defeat against New Zealand in Wellington in 2019.

Rank	Margin	Opponent	Venue	Year
1	125 runs	England	Trent Bridge, Nottingham	2026
2	80 runs	New Zealand	Wellington	2019
3	76 runs	South Africa	Ahmedabad	2026
4	51 runs	South Africa	New Chandigarh	2025
5	50 runs	New Zealand	Visakhapatnam	2016
6	49 runs	Australia	Bridgetown	2010

This table matters because it puts the Trent Bridge collapse into proper historical perspective.

India have had bad T20I nights before. They have been outplayed, out-hit, and out-thought. This defeat sits above all of them by margin. A 125-run defeat in a 20-over match is not a routine loss. It is a structural warning.

England Looked Clear, India Looked Confused

England’s performance was not flawless, but it was coherent.

Their batters understood the surface. Salt anchored and accelerated. Buttler set the tempo. Curran gave the innings a final push. With the ball, Archer and Tongue attacked the stumps, ribs, and judgment of India’s batters. Their fields were sharp, their catching was clean, and their intensity never dropped once the collapse began.

India looked like a side stuck between slogans and systems.

They talk about intent, but intent without shot selection becomes recklessness. They talk about depth, but depth does not matter if the top order burns the game inside five overs. They talk about transition, but transition needs structure.

England had a plan. India had movement without direction.

For more England coverage, visit The Sports Encounter’s England cricket section.

What This Means for the Series

England now lead the five-match series 2-0 after three scheduled games. The opener was washed out after India made 189-7 in Durham. England then won the second T20I in Manchester before producing this ruthless performance at Trent Bridge.

India can no longer win the series. At best, they can draw it 2-2 by winning the final two matches.

That is the immediate damage.

The deeper concern is what this result says about India’s T20I direction. Their batting order looks fragile. Their selection choices lack clarity. Their captain is under pressure. Their young players are being asked to carry too much emotional weight in an unstable structure.

England, meanwhile, will feel they have found a sharper white-ball rhythm. Salt’s return to form, Curran’s finishing, Archer’s power-play hostility, and Tongue’s new-ball threat give them a strong base for the rest of the series.

For India, Trent Bridge will not fade quickly.

A defeat like this stays in selection meetings. It follows captains into press conferences. It becomes part of the public argument about who belongs, who leads, and what kind of T20 cricket the team actually wants to play.

India did not simply lose the 3rd T20I.

They suffered their worst T20I defeat by runs, and the scoreboard exposed a team still searching for order in the middle of its reset.

Pakistan have gone back to Babar Azam. That sentence alone tells a story. The story of a failed Shan Masood captaincy project, a battered Test side, a fast-bowling identity crisis, a selection committee running out of attractive leadership options, and a cricket board that has spent too many years treating captaincy like a revolving door.

Babar Azam has been named Pakistan’s Test captain for the upcoming two-match series in the West Indies and the three-Test tour of England that follows. The Pakistan Cricket Board confirmed Babar’s appointment for both series while announcing the squad, with the West Indies Tests scheduled from July 25 to August 6 before Pakistan head to England later in August.

On paper, this is a leadership change. In reality, it is an admission.

Pakistan did not simply remove Shan Masood. They conceded that the red-ball reset after Babar’s earlier exit had collapsed. Masood’s record became historically poor. Pakistan’s Test reputation kept slipping. Babar’s own batting suffered in the years after his captaincy was taken away. And now, with Pakistan at the bottom end of the World Test Championship conversation and facing five tough Tests in quick succession, the PCB has returned to the man it once moved away from.

This is not a neat comeback story.

It is a rescue mission wrapped inside a familiar Pakistan cricket contradiction: the same system that unsettled Babar now wants him to restore order.

For more cricket coverage, player analysis, selection debates, and major Test cricket storylines, follow The Sports Encounter’s Cricket section.

The Breaking Point: Shan Masood’s Captaincy Had Run Out of Road

Shan Masood’s removal did not come out of nowhere. It came after a Test captaincy run that had become impossible to defend.

Masood captained Pakistan in 16 Tests and lost 12. That raw number is brutal enough. The deeper issue was not only losing. It was the way Pakistan kept losing.

They lost 3-0 in Australia. They suffered home and away embarrassment against Bangladesh. They failed to protect winning positions. They leaked decisive lower-order partnerships. They lost control at key moments. They became the kind of Test team that could compete for four sessions and still find a way to lose in the fifth.

That is why Aaqib Javed’s explanation matters. The selector and high-performance director pointed not just to results, but to repeated failures in game management: over-rate discipline, DRS calls, toss decisions, and the captain’s responsibility to finish matches. In other words, the PCB’s case against Masood was not merely statistical. It was operational.

Masood’s own batting complicates the picture. He was not removed because he personally failed with the bat. His Test average as captain rose to 34.06 from 28.51 before his appointment, and he produced two centuries and seven half-centuries during that period. The selectors have kept him in the squad, which shows they separated his place as a batter from his failure as captain.

That distinction is fair. It also makes the leadership decision clearer.

Pakistan did not drop Shan Masood the player. They abandoned Shan Masood the Test captain.

Why Babar Again?

The obvious answer is experience. The uncomfortable answer is lack of options.

Babar’s first Test captaincy stint was far from flawless, but it had more structure, more success, and more batting authority than what came after. He led Pakistan in 20 Tests and won 10 of them.

His early captaincy phase brought a sense of direction. Pakistan beat South Africa 2-0 at home. They swept Bangladesh away. They won in Sri Lanka. In 2021, Babar became the first Pakistan captain to win his opening four Tests. That detail now feels almost from another era.

There were problems too. The biggest one was the 3-0 home whitewash against England, the only such defeat in Pakistan’s Test history. That series badly damaged the Babar captaincy narrative because it suggested Pakistan had lost tactical control at home, where they should have been strongest.

Still, when placed beside Masood’s record, Babar’s earlier tenure looks considerably stronger. More importantly, Babar the batter was also better when he was captain. During his first Test leadership run, he averaged above 50 in the format. After losing the captaincy, his Test returns fell sharply. Under Masood, Babar averaged just over 27 in Tests.

That is the real human cost of Pakistan’s captaincy churn.

The board removed the armband, but it may also have removed something less visible: rhythm, authority, and security from its best batter.

Babar’s Batting Decline Was Not Just a Form Slump

Great batters go through lean periods. That is normal. What happened with Babar felt heavier because it arrived in the middle of public captaincy chaos, role changes, squad uncertainty, and Pakistan’s broader decline across formats.

Babar stepped down from captaincy in all formats after Pakistan’s disappointing 2023 ODI World Cup campaign. He was later reappointed as limited-overs captain in 2024, then resigned again from white-ball leadership to focus on his batting. By 2026, he had been dropped from Pakistan’s ODI squad for the Bangladesh series despite scoring an unbeaten century in his previous ODI against Sri Lanka.

That is not the normal arc of a settled world-class player.

It is the arc of a player repeatedly pulled into Pakistan cricket’s leadership storm, then pushed out of it, then dragged back toward it when the structure around him failed.

The Test decline after Babar’s removal cannot be blamed entirely on the PCB taking captaincy away from him. Cricket is not that simple. Pakistan had selection issues, domestic-structure problems, tactical confusion, bowling decline, and a batting order that did not consistently absorb pressure. But Babar’s own drop in Test output under Masood matters because it shows that leadership shuffles do not happen in isolation.

When a board changes captains too often, the damage does not stop at the toss. It affects dressing-room hierarchy. It affects player roles. It affects confidence. It affects how senior players see their future. It affects whether a batter feels trusted or constantly judged by the next administrative mood swing.

Babar was once Pakistan’s central cricketing figure. Then he became a former captain trying to find form inside a team that had lost its shape.

Now he is being asked to become the center again.

Pakistan’s Test Decline After Babar Was Removed

Pakistan did not become a stronger Test team after moving away from Babar.

That is the hard truth.

Under Shan Masood, Pakistan’s red-ball cricket produced one short burst of hope, a comeback series win over England, but the larger picture remained bleak. The team lost four of seven series under Masood, won only one, and finished at the bottom of the World Test Championship 2023-25 table during that cycle.

The post-Babar phase included a 3-0 defeat in Australia, historic trouble against Bangladesh, home failures, and a seven-Test losing streak that equaled Pakistan’s worst in the format.

Pakistan’s Test cricket also lost something harder to measure: intimidation.

For decades, even flawed Pakistan Test sides carried danger. They had mystery spin, reverse swing, unpredictable fast bowling, and batters who could turn a session. In recent years, that aura has weakened. Teams no longer fear Pakistan’s home conditions the same way. Touring sides have found ways to attack. Even the fast-bowling production line, once Pakistan’s most reliable cricketing identity, now looks uncertain.

That is why this captaincy change arrived alongside major selection surgery.

Pakistan’s upcoming England tour will also land against a wider debate around modern Test identity. England are going through their own red-ball reckoning, which we explored in our deep analysis of how Bazball changed and exposed England.

The Squad Tells Its Own Story: Pakistan Are Not Just Changing Captains

Babar’s return came with major omissions. Shaheen Shah Afridi, Hasan Ali, and Noman Ali were all left out of Pakistan’s squad for the West Indies and England Tests, while Saud Shakeel was ruled out of the West Indies tour because of fitness concerns.

This is not a cosmetic reshuffle. It is a red-ball reset.

Shaheen’s omission is the biggest signal. Since returning from a knee injury in 2023, he has not been the same Test bowler. The reporting around the squad noted that he had taken only 27 wickets in 16 Test innings at an average of 40.11, with a strike rate of 67.6. Those are not spearhead numbers. They are warning signs.

Aaqib Javed’s comments about pace were even sharper. He said Pakistan were concerned about fast bowlers’ speeds dropping to around 126 kph on the second or third day of Tests in Bangladesh. That single number tells a grim story. Pakistan cricket has spent generations celebrating pace as an instinct. Now the selectors are using speed-gun evidence from a camp to justify a refresh.

That is why Ubaid Shah has been fast-tracked.

Ubaid, the youngest of the Shah brothers, has taken 72 first-class wickets in 16 matches since his debut in October 2024. His selection is not just about promise. It is about Pakistan trying to rediscover velocity in a format where their attack has become too easy to survive.

Noman Ali’s omission and Ali Usman’s call-up also point to a more evidence-led selection approach. Ali Usman has 192 first-class wickets at 28.81 and topped the 2026-27 Quaid-e-Azam Trophy wicket charts with 48 wickets at 21.10, including six five-wicket hauls in eight matches for Multan.

Pakistan are trying to say performance matters again.

The challenge is whether the same system can stay patient long enough to let that principle work.

Pakistan’s fast-bowling identity has always been central to its Test cricket image. In England, that conversation will become even sharper because England’s own Test tradition has been built around elite all-rounders and seam pressure, a theme we revisited in Sir Ian Botham: England’s Greatest All-Rounder and Cricket’s Ultimate Showman.

The Musical Chairs Problem

Pakistan cricket’s captaincy churn has become more than a meme. It is now a performance issue.

Babar was captain. Then he was not. Masood came in. Rizwan took white-ball duties. Shaheen became ODI captain. Salman Ali Agha’s name floated around the Test conversation. Babar has been brought back.

That is not succession planning. That is reaction management.

Elite Test teams build identity over time. Australia know what kind of cricket they want to play. India have developed depth and role clarity. England, even when debated, have a recognizable Test philosophy. South Africa, New Zealand, and Sri Lanka have their own constraints, but they rarely look as administratively restless as Pakistan.

Pakistan, by contrast, often confuse change with progress.

A captain loses a series, so a new captain arrives. A batting star loses form, so the leadership question returns. A bowler slows down, so the whole pace structure is debated. A new selector enters, and the language changes again. Everyone talks about long-term planning, but too many decisions feel driven by the last bad scorecard.

This is how teams lose Test reputation.

Not in one defeat. Not in one collapse. Not in one bad tour.

They lose it through years of inconsistency, where no captain gets enough stability, no player feels fully protected, and no cricketing philosophy survives long enough to become culture.

The pressure on modern Test captains is not unique to Pakistan. England have faced similar questions around aggression, control, and leadership, which we explored in The Curious Case of Ben Stokes and His Opponents.

Babar’s First Stint: What Worked and What Failed

To understand why Pakistan returned to Babar, it is worth separating the myth from the record.

His first stint was not perfect. The England whitewash at home was a huge failure. Pakistan’s tactics at home were often questioned. His captaincy sometimes looked conservative. And critics argued that Babar the leader lacked the ruthlessness that elite Test captains need.

But his team did win. Pakistan won 10 of his 20 Tests as captain. They had a clearer top-order identity. Babar’s own batting was stronger. His authority inside the dressing room was obvious. The side looked less fractured than it later became.

His early captaincy achievement also mattered symbolically. Babar became the first Pakistan captain to win his opening four Tests, while Pakistan had also completed a strong series-winning run across formats during that period.

That does not mean Babar was a tactical genius. It does mean Pakistan had a period when leadership, batting form, and results moved in the same direction.

That alignment disappeared later.

Why the West Indies Series Is Bigger Than It Looks

A two-Test series in the West Indies may not sound like the biggest stage for a leadership restart, but for Babar, it is crucial.

Pakistan cannot afford to enter the England tour carrying fresh damage. The West Indies series must give Babar three things: a win, runs, and authority.

The first Test begins on July 25 at the Brian Lara Cricket Academy in Tarouba. The second is scheduled at Queen’s Park from August 2 to 6. After that, Pakistan travel to England for Tests at Headingley, Lord’s, and Edgbaston.

That schedule is unforgiving.

West Indies conditions will test patience and adaptability. England will test technique, temperament, seam movement, and captaincy under scrutiny. If Pakistan stumble in the Caribbean, Babar will reach England already under pressure. If they win well, the tour of England becomes a bigger, cleaner examination rather than another crisis response.

For Babar personally, the West Indies series is the reset before the storm.

That England tour will carry major leadership intrigue because England are also moving into a new phase after Ben Stokes’ retirement and England’s next Test chapter.

The Shaheen Question Adds Another Layer

Babar’s return also comes without Shaheen Shah Afridi in the Test squad.

That matters because Babar’s earlier captaincy identity was closely tied to a more threatening Pakistan bowling unit. Shaheen at full tilt gives any captain a different kind of power. He attacks new batters. He shapes sessions. He creates fear before lunch on day one.

The current Shaheen question is uncomfortable. Has Pakistan dropped him to manage his workload? Has his Test bowling declined too far? Is he now being nudged toward format specialization? Aaqib’s comments about format-wise central contracts suggest the PCB is thinking seriously about who belongs where.

For Babar, this means his second stint begins without the automatic strike weapon he might have expected in earlier years.

That makes his captaincy harder and more interesting. He must lead not only a team, but a transition.

What Babar Must Fix Immediately

Babar’s second Test captaincy stint will be judged on more than whether Pakistan beat West Indies.

He has to fix five things quickly.

1. Restore batting calm

Pakistan’s batting has too often moved between soft starts and sudden collapses. Babar must set the tempo himself. Runs from him will calm the dressing room faster than any press conference.

2. Give Shan Masood a clear role

Masood remains in the squad. That could be awkward, or it could be useful. Babar must make sure Masood is treated as a batter, not as a defeated former captain haunting the XI.

3. Protect the young players

Ubaid Shah, Ali Usman, and Awais Zafar cannot be treated as instant miracle fixes. Pakistan must give them clarity, not panic after one bad innings or spell.

4. Rebuild fast-bowling standards

If Pakistan’s pace is dropping deep into Tests, that is not only a selection issue. It is a conditioning, workload, and tactical issue. Babar will need to use his bowlers smarter.

5. Close games

This was the biggest criticism of Masood. Pakistan must stop letting strong positions drift. Babar’s first major test will be whether his team can finish sessions, days, and matches.

Scorecard of the Pakistan Test Reset

Area	What Changed	What It Means
Captaincy	Babar Azam replaces Shan Masood	PCB returns to experience after failed red-ball reset
Former captain	Masood stays in squad	Batting form saved his place, captaincy record cost him leadership
Fast bowling	Shaheen and Hasan dropped, Ubaid Shah called up	Pakistan want more pace and stamina across long spells
Spin	Noman Ali out, Ali Usman in	Domestic red-ball performance rewarded
Middle order	Saud Shakeel unavailable for West Indies, Awais Zafar called up	Pakistan test new batting depth before England
Immediate schedule	West Indies then England	Babar gets no soft landing in his second stint

Pakistan Squad for West Indies and England Tests

Babar Azam (capt), Aamir Jamal, Abdullah Fazal, Ali Usman, Azan Awais, Imam ul Haq, Khurram Shahzad, Mohammad Abbas, Mohammad Ali, Mohammad Rizwan (wk), Mohammad Awais Zafar, Mohammad Ghazi Ghouri, Sajid Khan, Salman Ali Agha, Shan Masood, Ubaid Shah.

Final Word: Babar Is Back, But Pakistan Must Stop Breaking Its Own Rhythm

Babar Azam’s return as Test captain will please many Pakistan fans, but it should not be treated as a magic fix.

He can bring authority. He can bring experience. He can bring a better record than Shan Masood. He can also bring personal motivation after a messy period in which his captaincy status, batting form, and standing inside Pakistan cricket all took hits.

But one man cannot repair a system that keeps changing direction every few months.

Pakistan’s Test decline after Babar’s first stint was not caused by one captain alone. It was built through unstable leadership, confused selection, declining pace standards, weak game management, and a board culture that too often reacts rather than plans.

Now Babar has the job again.

The West Indies series will be his first chance to show that Pakistan can still win Test cricket with clarity rather than chaos. England will be the harder examination. And the PCB, for once, must resist its oldest temptation: moving the chairs again before the music has even settled.

Babar is back.

Now Pakistan have to prove they know why.

FAQs

Why is Babar Azam back as Pakistan Test captain?

Babar Azam has returned after Shan Masood was removed following a poor Test captaincy run. Pakistan lost 12 of 16 Tests under Masood, and selectors decided a leadership change was needed before the West Indies and England tours.

What was Babar Azam’s Test record as Pakistan captain before this return?

Babar previously captained Pakistan in 20 Tests and won 10 of them. His tenure included home success against South Africa and away series wins in Bangladesh and Sri Lanka, but also a 3-0 home whitewash against England.

Why was Shan Masood removed as Pakistan Test captain?

Masood was removed because Pakistan’s Test results declined badly under his leadership. The selectors also pointed to repeated failures to finish close matches, poor game management, over-rate issues, DRS calls, toss decisions, and lack of results.

Has Shan Masood been dropped from the Pakistan Test squad?

No. Shan Masood has been removed as captain but remains in the squad. His batting improved during his captaincy tenure, so the selectors separated his role as a batter from his leadership record.

Why has Shaheen Shah Afridi been dropped from the Test squad?

Shaheen Shah Afridi has been left out after a difficult period in Test cricket since returning from a knee injury. His recent Test numbers have been poor, and selectors have also raised concerns about Pakistan fast bowlers losing pace during long matches.

When does Pakistan’s West Indies Test series begin?

Pakistan’s first Test against West Indies begins on July 25, 2026, at the Brian Lara Cricket Academy in Tarouba. The second Test will be played at Queen’s Park from August 2 to 6.

Who are Pakistan’s new players in the Test squad?

Ubaid Shah, Ali Usman, and Mohammad Awais Zafar have earned maiden call-ups. Ubaid strengthens the pace department, Ali Usman adds left-arm spin depth, and Awais Zafar provides a middle-order batting option.

The Sports Encounter’s cricket coverage focuses on match analysis, player form, team selection, tactical debates, tournament context, and the biggest stories shaping world cricket.

Jacob Bethell did not just win England a T20I at Old Trafford. He dragged them out of a first-over disaster, absorbed India’s pressure, broke the chase open, and turned Manchester into the night England found a new finisher under fire.

England beat India by four wickets in the second T20I on July 4, 2026, chasing 191 with six balls remaining after Bethell’s unbeaten 76 off 46 balls transformed a game that had looked India’s after five deliveries.

India had posted 190/7 after choosing to bat first, built around Abhishek Sharma’s 43, Ishan Kishan’s 49, Shreyas Iyer’s 37, and a late 24 not out from Tilak Varma. It was a strong total, especially after the first T20I had been washed out, and India looked even better placed when Arshdeep Singh removed Phil Salt and Jos Buttler inside the opening over.

At 1/2, England were not chasing a target. They were chasing stability.

Bethell gave them that first. Then he gave them the match.

For more cricket coverage, follow The Sports Encounter’s Cricket section and our wider analysis of rising young players, including Vaibhav Sooryavanshi’s early cricket journey.

England Were 1/2 Before Bethell Took Control

India’s opening burst was almost perfect. Arshdeep struck with the first ball of England’s chase, removing Salt for a golden duck. Four balls later, Buttler followed without scoring. England’s two most explosive openers were gone, India’s fielders were buzzing, and the scoreboard read 1/2.

That kind of start usually distorts a chase. Batters become hesitant. Required rates climb quietly. Every dot ball feels heavier than it should.

ALSO READ: Ireland Clean Sweep T20I World Champions India in Belfast

Harry Brook refused to let India settle. England’s captain launched a savage counterattack, smashing 39 from just 15 balls with four fours and three sixes. His innings carried the violence England needed in the powerplay, but it also came with risk. When Axar Patel removed him at 51/3 in the fifth over, India had broken through again.

England had scored quickly, but they had also lost three wickets inside five overs. The match was still unstable. That is where Bethell’s innings began to separate itself from a normal T20 cameo.

Bethell’s 76* Was a Chase Built in Layers

Bethell finished with 76 not out from 46 balls, striking five fours and five sixes at 165.21. The numbers are excellent, but the timing of his acceleration tells the real story.

He did not swing blindly after the early collapse. He let Brook attack first. He then worked through the middle overs with Tom Banton, who made a valuable 39 from 32 balls. Their partnership gave England breathing room after India had threatened to tear through the chase.

At drinks, England were 91/3 after 10 overs. The game was alive, but India still had a path. Banton’s dismissal at 118/4 brought the pressure back. Will Jacks followed at 133/5, and suddenly India were one more wicket away from exposing England’s lower order with the asking rate rising.

Bethell stayed calm. That mattered more than the boundaries at first.

He reached his half-century from 39 balls, a measured landmark in the context of a chase that demanded both patience and nerve. Then, once the equation tilted toward danger, he changed gears brutally.

The Ravi Bishnoi Over That Changed Everything

The match turned in one over.

England needed 49 from the final four overs. India still had enough runs to defend. Ravi Bishnoi had one over left, and Shreyas Iyer would have expected his leg-spinner to at least keep the chase in the balance.

Bethell had other plans.

He took Bishnoi apart in the 17th over, clearing the boundary and slicing into India’s control with a burst of clean, fearless hitting. The over went for 29 runs. By the time it ended, England’s equation had crashed from 49 off 24 balls to 20 off 18.

That was the match.

India did not lose because of one poor over alone, but that over changed the emotional direction of the chase. Until then, India had pressure. After it, England had belief, momentum, and a set batter who had already beaten the hardest part of the game.

ALSO READ: Ben Stokes Shocks World Cricket with Sudden Retirement

India’s 190 Looked Enough Until England’s Middle Order Found Its Nerve

India’s innings had plenty of good work. Abhishek Sharma gave them early tempo with 43 from 24 balls, hitting eight fours and one six. Vaibhav Sooryavanshi, making his T20I debut, produced a short but fearless 14 from 10 balls, including two sixes, before being stumped by Buttler off Will Jacks.

Ishan Kishan missed a half-century by one run after making 49 from 40 balls. Shreyas Iyer’s 37 from 22 pushed India through the middle overs, while Tilak Varma’s unbeaten 24 from 11 balls lifted the total to 190.

On most nights, 190 in Manchester gives a team a serious chance. India also had the perfect start with the ball. Arshdeep’s first-over double strike should have put England into survival mode.

Instead, England found three different answers: Brook’s violence, Banton’s steadiness, and Bethell’s finish.

Sam Curran Kept India Below 200

England’s chase will dominate the headlines, but Sam Curran’s 3/33 was vital. India were moving toward 200-plus before Curran broke their rhythm. He dismissed Abhishek, Shivam Dube, and Ishan Kishan, giving England just enough control at the back end.

Jofra Archer also played an important role, taking 1/40 and then returning with the bat to finish unbeaten on 10 from seven balls. His calm presence alongside Bethell helped England avoid late panic after Sam Curran fell at 179/6.

For England, this win was more than a chase. It was a response to pressure from the first ball of the innings.

Scorecard Snapshot

Team	Score	Top Scorer	Best Bowler Against Them
India	190/7 in 20 overs	Ishan Kishan 49	Sam Curran 3/33
England	191/6 in 19 overs	Jacob Bethell 76*	Arshdeep Singh 3/40

Key Match Facts

• England won by four wickets with six balls remaining.
• Jacob Bethell finished unbeaten on 76 from 46 balls.
• England recovered from 1/2 after Arshdeep Singh removed Salt and Buttler in the first over.
• Harry Brook smashed 39 from 15 balls to restart England’s chase.
• Tom Banton made 39 from 32 balls in a crucial middle-overs stand with Bethell.
• Ravi Bishnoi conceded 60 runs in four overs, including the decisive 29-run 17th over.
• Sam Curran was England’s best bowler with 3/33.
• Vaibhav Sooryavanshi made his T20I debut for India and scored 14 from 10 balls.

What This Means for England and India

For England, the result gives Harry Brook’s side early control in the five-match series after the opening game was abandoned due to rain. It also gives them a major middle-order story. Bethell has talent, but this was different. This was responsibility under scoreboard pressure against India, after England’s chase had almost collapsed at birth.

For India, the loss will sting because they did so much right. They batted well enough to reach 190. Arshdeep delivered a dream start. Axar Patel bowled four overs for just 20. Still, India could not control the one phase that mattered most.

That will worry Shreyas Iyer and his staff. T20s can swing in one over, but elite teams protect winning positions better than this.

ALSO READ: England Fall Apart at Trent Bridge as New Zealand Seal Historic Comeback and Stokes Era Ends in Defeat

England now have the result, the momentum, and the player who changed the mood of the series in one innings. India have firepower, young promise, and enough depth to respond, but they also have a clear problem to solve: how to close a game when a batter like Bethell refuses to blink.

Final Word

Some T20 innings win matches because they are fast. Bethell’s 76 not out won this one because it was shaped perfectly. He survived the collapse, trusted Brook’s counterattack, rebuilt with Banton, waited for his over, and then finished the chase with the calm of a player who knew exactly when to attack.

Old Trafford saw India control the match twice. First with the bat, then with Arshdeep’s new-ball burst.

Bethell still found a way through.

That is why this was not simply a win for England. It was Bethell’s arrival under pressure.

The Sports Encounter’s cricket coverage focuses on match reports, player analysis, tactical breakdowns, tournament trends, and the biggest talking points from the game.