Kapil Dev: The All-Rounder Who Made India Believe in Itself
Kapil Dev was more than India’s 1983 World Cup-winning captain. He was the fast-bowling all-rounder who changed Indian cricket’s confidence, records, ambition, and global identity, leaving behind a legacy built on courage, wickets, runs, leadership, and belief.
Indian cricket had great players before Kapil Dev. It had stylish batters, gifted spinners, proud captains, and men who carried the game through difficult decades.
Kapil Dev gave it something different.
He gave Indian cricket a new physical language. He ran in hard. He swung the ball at pace. He hit the ball cleanly. He fielded like a natural athlete. He carried himself with the directness of a cricketer who did not wait for permission to compete with the strongest teams in the world.
That may be the simplest way to understand his place in Indian cricket. Before India became a global cricket power, before the IPL, before packed white-ball calendars, before fast-bowling depth became normal, Kapil Dev made India believe it could attack.
His record still explains the size of the cricketer. According to ESPNcricinfo’s Kapil Dev profile, he played 131 Tests, scored 5,248 runs, took 434 wickets, held 64 catches, and became one of the most complete cricketers India has produced. In ODIs, he played 225 matches, scored 3,783 runs, took 253 wickets, and held 71 catches.
The numbers matter. The meaning goes further.
Kapil Dev did not inherit an Indian team used to winning World Cups. He captained one that had won only one match across the first two editions of the tournament before 1983. He then led India to the title at Lord’s, beating the West Indies, the most dominant cricket force of that era, by 43 runs in the final. The full India vs West Indies 1983 World Cup final scorecard still reads like one of cricket’s greatest upsets.
That victory changed Indian cricket’s self-image. It also changed how the world saw Indian cricket. For more stories around major cricket moments and current match coverage, follow The Sports Encounter’s complete Cricket coverage.
Key Facts: Kapil Dev Career Snapshot
| Category | Record |
|---|---|
| Full name | Kapil Dev Ramlal Nikhanj |
| Born | January 6, 1959 |
| Role | Fast-bowling all-rounder |
| Test matches | 131 |
| Test runs | 5,248 |
| Test wickets | 434 |
| Test centuries | 8 |
| Test five-wicket hauls | 23 |
| Best Test bowling | 9 for 83 |
| ODI matches | 225 |
| ODI runs | 3,783 |
| ODI wickets | 253 |
| Best ODI bowling | 5 for 43 |
| Biggest captaincy achievement | 1983 Cricket World Cup title |
| Major individual World Cup innings | 175 not out vs Zimbabwe in 1983 |
| Major honors | ICC Cricket Hall of Fame, Wisden Indian Cricketer of the Century, CK Nayudu Lifetime Achievement Award |
The Cricketer India Did Not Know It Needed
Kapil Dev arrived in Indian cricket at a time when India was known more for spin, patience, and batting craft than pace and athletic aggression. The country had produced some of the finest spin bowlers in the world, but genuine fast-bowling all-rounders were rare. Kapil gave India a player who could take the new ball, bat in the middle order, rescue an innings, change the tempo, and inspire a dressing room through visible energy.
The ICC Hall of Fame profile for Kapil Dev describes him as India’s finest fast-bowling all-rounder and places him alongside Imran Khan, Ian Botham, and Richard Hadlee among the great all-rounders of his time. It also notes that he was India’s strike bowler for nearly 15 years and finished with 434 Test wickets, a world record at the time.
That comparison is important. The 1980s were an all-rounder’s era. Imran had command and reverse swing. Botham had charisma and match-winning instinct. Hadlee had precision and control. Kapil had a different blend. He brought pace, stamina, natural hitting, attacking fields, and a stubborn refusal to treat Indian cricket as smaller than anyone else’s.
He was called the Haryana Hurricane for a reason. The name matched his cricket. He played with movement, force, and a certain rural athleticism that felt different from India’s earlier cricketing image.
Kapil was never only a bowler who could bat. He was a cricketer who gave India balance. That balance mattered because India’s teams of that period often needed one player to cover two roles. Kapil opened the bowling, batted with the lower middle order, fielded with energy, and captained without looking overwhelmed by bigger reputations.
The Test Record That Still Stands Apart
Kapil Dev’s Test career remains one of the most extraordinary statistical achievements by any Indian cricketer. He scored 5,248 runs at an average a little above 31 and took 434 wickets at an average under 30. His batting brought eight Test centuries, while his bowling brought 23 five-wicket hauls and two 10-wicket match hauls, as listed in his ESPNcricinfo career record.
The defining all-round number is simple: 5,000 runs and 400 wickets.
Kapil remains the only cricketer in Test history to complete that exact double of more than 5,000 runs and more than 400 wickets. Others have built elite all-round combinations in different ways, but Kapil’s combination of volume batting and strike-bowling workload remains rare.
His 434 Test wickets made him the highest wicket-taker in Test history when he passed Richard Hadlee’s record in 1994. Courtney Walsh later broke Kapil’s record, but Kapil’s achievement carried special weight because he came from a cricket system that did not have the fast-bowling culture, pitches, or support structure enjoyed by many pace greats of his era.
Kapil bowled long spells on Indian pitches that often rewarded spin more than pace. He played years without the kind of pace-bowling depth that allows a lead fast bowler to rotate workload easily. He often had to be the first threat, the holding option, the reverse-swing hope, and the lower-order batting insurance in the same match.
That is why his Test numbers cannot be read in isolation. They are also a record of endurance.
The ODI Record and the Shape of a Modern All-Rounder
Kapil Dev’s ODI career came from a period when the format was still learning what it wanted to become. The game was slower than today’s ODI cricket. Strike rates were lower. Batting power was used differently. Fielding standards were still evolving.
Inside that era, Kapil looked ahead of his time.
He scored 3,783 ODI runs and took 253 wickets in 225 matches. He was the first player to take 200 wickets in ODIs, and his best ODI bowling figures were 5 for 43. His combination of wickets, late-order runs, and fielding made him one of the format’s early complete players.
His batting strike rate in ODIs stood out for his time. In the 1983 World Cup, he made 303 runs at an average of 60.60 and a strike rate above 100, while also taking 12 wickets and holding seven catches. That tournament showed his value across every discipline.
That is the heart of Kapil’s ODI value. He did not only contribute. He changed the speed of a match.
India had many players who could occupy the crease. Kapil could shift pressure. He could turn 180 into 230, or 230 into 270. He gave bowlers a target to defend and batters a model of courage. When India later built its white-ball identity around aggression, athleticism, and all-round balance, Kapil’s influence sat quietly beneath that evolution.
The 175 Not Out That Became Indian Cricket Folklore
No Kapil Dev tribute can move far without returning to June 18, 1983.
India were playing Zimbabwe at Tunbridge Wells in a World Cup group match. The situation was desperate. India collapsed to 17 for 5. Kapil, the captain, walked into a match that was sliding toward humiliation and produced one of the most important innings in cricket history.
He made 175 not out from 138 balls. India reached 266 for 8 and won by 31 runs. The India vs Zimbabwe 1983 World Cup scorecard records Kapil’s 175 not out with 16 fours and six sixes, an innings that remains part of cricket folklore.
Its place in cricket history grew partly because there was no live television footage of the innings due to a BBC strike. That absence made the innings feel almost mythical. Fans heard about it, read about it, repeated it, imagined it, and passed it down as a story. In a strange way, the missing footage made the innings larger.
The scorecard still gives the basic structure. The captain came in with India broken. He refused to let the match end there. He hit with force, protected the lower order, and transformed the tournament.
In World Cup context, that innings saved India. Without it, India likely would not have reached the semifinal. Without the semifinal, there is no Lord’s final. Without the Lord’s final, there is no 1983 moment that changed Indian cricket.
Kapil’s 175 was more than a rescue. It was the innings that kept the possibility of Indian cricket’s biggest psychological breakthrough alive.
Lord’s 1983: The Catch, the Cup, and the Shock
India’s 1983 World Cup final against West Indies remains the central chapter of Kapil Dev’s career.
India were bowled out for 183 at Lord’s. Against the West Indies batting lineup, that total looked light. The West Indies had won the first two World Cups and were seeking a third straight title. They had elite fast bowlers, powerful batters, and the aura of a team that expected to win.
Then came the defining moment.
Viv Richards was batting freely. He had moved to 33 from 28 balls. Madan Lal bowled, Richards pulled, and the ball went high into the London sky. Kapil ran back from mid-wicket and completed one of Indian cricket’s most famous catches. The official 1983 World Cup final scorecard records Richards as caught by Kapil Dev off Madan Lal.
The catch became a symbol because of who hit the shot and who caught it. Richards was the most intimidating batter in the world. Kapil was India’s captain. The moment did not win the final by itself, but it punctured the sense that West Indies were untouchable.
India went on to bowl West Indies out for 140 and win by 43 runs. Mohinder Amarnath was player of the match for his all-round performance, but Kapil’s captaincy, fielding, energy, and tournament-wide contribution turned him into the face of the triumph.
The image of Kapil lifting the World Cup at Lord’s became one of Indian sport’s foundation photographs. Later generations would have their own moments: Sachin Tendulkar carried around Wankhede in 2011, MS Dhoni’s six, Virat Kohli’s global dominance, Rohit Sharma’s white-ball era, Jasprit Bumrah’s fast-bowling excellence. Yet 1983 came first.
Kapil’s team made all of that feel possible.
What Kapil Dev Brought to Indian Cricket
Kapil Dev brought five major things to Indian cricket.
The first was fast-bowling belief. India did not suddenly become a pace factory because of him, but he changed what young players could imagine. A boy in India could watch Kapil and think pace bowling was not only for Australians, West Indians, Pakistanis, or Englishmen.
The second was all-round ambition. Before Kapil, India had great specialists. Kapil showed the value of a cricketer who could influence the game in three ways. He made Indian cricket think harder about balance, depth, and utility.
The third was World Cup confidence. India’s 1983 win gave the country its first major global cricket title. That victory helped cricket grow into a mass emotional force in India. It also made future World Cup dreams feel realistic rather than decorative.
The fourth was physical courage. Kapil was athletic in a way that felt visible. His running catch in the 1983 final, his bowling workloads, and his lower-order hitting all carried the same message: India could match anyone in intensity.
The fifth was leadership without fear. Kapil’s captaincy was not perfect, and his record as a leader had ups and downs. But the image of him leading India past West Indies gave Indian cricket a new kind of captaincy memory. He was not managing decline. He was inviting risk.
That is his deepest legacy. Kapil made Indian cricket bolder.
Records and Major Achievements
Kapil Dev’s career is full of headline records and honors.
He finished with 434 Test wickets, which was a world record at the time. He became the first player to reach the 5,000-run and 400-wicket double in Test cricket. He led India to the 1983 World Cup. He scored the famous 175 not out against Zimbabwe. He finished his ODI career with 253 wickets, becoming one of the format’s early great wicket-takers.
He was named one of Wisden’s Cricketers of the Year in 1983, a recognition tied to the scale of his influence during that period. In 2002, Rediff reported that Kapil Dev was chosen as Wisden Indian Cricketer of the Century by a jury of 35 cricketers, journalists, and thinkers at Wembley.
Kapil was inducted into the ICC Cricket Hall of Fame in 2010. ESPNcricinfo reported that he played 131 Tests and 225 ODIs across a 16-year international career, while the ICC profile presents him as India’s greatest fast-bowling all-rounder.
In 2013, the BCCI honored him with the Col. C.K. Nayudu Lifetime Achievement Award, the board’s highest lifetime honor for a former Indian cricketer.
Those honors matter because they came from different directions. Wisden recognized his century-scale place in Indian cricket. ICC recognized his global status. BCCI recognized his lifetime contribution to Indian cricket.
The Difficult Moments and the Human Side of the Legend
Kapil Dev’s career was glorious, but it was not untouched by pain.
The first difficult layer was expectation. After 1983, Kapil became more than a captain. He became a national symbol. Every defeat, every selection debate, every captaincy decision, and every personal slump carried extra scrutiny.
India did not become a consistently dominant world team immediately after 1983. The World Cup win changed belief, but it did not instantly fix infrastructure, overseas performance, or team depth. Kapil remained a central figure through that gap between inspiration and sustained power.
The second difficult moment came at the 1987 World Cup. India entered as co-hosts and defending champions but lost to England in the semifinal. Kapil was criticized for his dismissal in that match after attempting a big shot at a crucial stage. For a player who had built his reputation on brave, attacking cricket, the same instinct became a source of criticism when it failed.
The third difficult chapter was his coaching period. Kapil coached India from 1999 to 2000 during one of the most turbulent periods in world cricket. His tenure coincided with Indian cricket’s match-fixing storm and ended with his resignation. ABC reported in September 2000 that Kapil Dev resigned as Indian coach after months of pressure while defending his reputation.
The most painful public moment involved match-fixing allegations made by Manoj Prabhakar. The Central Bureau of Investigation later found no evidence of Kapil Dev’s role in match-fixing and related malpractice. ESPNcricinfo’s publication of the CBI report section states that the inquiry had not disclosed evidence of Kapil’s role. That finding is central to any fair account of the episode, and the relevant section is available in ESPNcricinfo’s archive of the CBI report on cricket match-fixing.
That chapter matters in any honest tribute. It was a brutal personal and public ordeal. It placed one of India’s greatest cricket heroes in the middle of a national trust crisis. The CBI finding cleared him of the allegation, but the experience left a scar on how that period is remembered.
The fourth difficult layer was post-retirement comparison. As Indian cricket grew richer and more powerful, later generations sometimes reduced Kapil to one image: the 1983 captain. That is unfair. He was not only a World Cup symbol. He was also India’s greatest fast-bowling all-rounder, a long-serving Test match-winner, an ODI pioneer, and a cricketer who carried enormous workloads before modern sports science, rotation, and recovery systems became normal.
Kapil Dev the Batter: Better Than the Average Suggests
Kapil’s Test batting average of just over 31 can make his batting look useful rather than elite. That misses context.
He often batted in difficult situations. He played attacking cricket before lower-order counterpunching was celebrated in the modern way. He was capable of centuries, rescue acts, and momentum-shifting cameos. His highest Test score was 163, and his eight Test centuries confirmed that he was more than a tail-end hitter.
Kapil’s batting had a particular value for India. He could change the mood of a dressing room. A collapse did not always feel terminal when he was still to come. Bowlers could be attacked. Fields could be moved. A match could breathe again.
The 175 against Zimbabwe is the greatest example, but it was not the only proof. Kapil’s batting gave India a rare form of lower-order intimidation. He made opponents think about him. In an era when India did not regularly bat deep with power, that mattered.
He was not a textbook stylist in the Sunil Gavaskar tradition. He was not a long-form technician in the Rahul Dravid tradition. He did not have the modern white-ball finishing templates of Dhoni or Hardik Pandya. Kapil’s batting lived through instinct, timing, hand speed, and courage.
That courage often gave India runs it had no right to expect.
Kapil Dev the Bowler: India’s First Great Pace-Bowling Standard
Kapil’s bowling legacy may be even more important than his batting.
India has now produced fast bowlers who win Test matches overseas. Jasprit Bumrah, Mohammed Shami, Mohammed Siraj, Ishant Sharma, Zaheer Khan, and others have given Indian cricket a pace tradition that looks normal today. It was not normal when Kapil began.
Kapil had to carry the idea of Indian pace before the system fully supported it.
His numbers show range and longevity. In Tests, he took 434 wickets with 23 five-wicket hauls. In ODIs, he took 253 wickets. He bowled with stamina across formats and conditions.
He was not express pace throughout his career, but he had rhythm, outswing, control, and a natural ability to make things happen. His best Test innings figures, 9 for 83, remain one of the great Indian bowling performances.
Kapil gave Indian fast bowling a target. He showed that an Indian pacer could lead an attack, survive workloads, and earn global respect. Later Indian fast bowlers did not follow his exact style, but they inherited the permission he created.
That is a rare kind of influence.
Kapil Dev the Captain: Imperfect, Instinctive, Historic
Kapil Dev’s captaincy cannot be judged only through win-loss numbers.
His Test captaincy record was mixed, and India in the 1980s faced strong teams with structural limitations. But captaincy is also about moments, and Kapil owns the biggest captaincy moment in Indian cricket before the 21st century.
The 1983 World Cup title remains his defining leadership achievement. He was 24 when India won the tournament, making him one of the youngest World Cup-winning captains in cricket history. More importantly, he was the first Indian captain to win a Cricket World Cup.
Kapil’s leadership style was built on instinct and example. He was not a distant strategist. He led through action. He bowled, batted, fielded, smiled, attacked, and kept moving. His team reflected that in 1983. India were not the most powerful side in the tournament. They became the side that refused to leave.
There were also tactical criticisms across his captaincy years, as there are with most captains. Yet history is sometimes decided by whether a leader opens a door others later walk through. Kapil opened one of Indian cricket’s largest doors.
Why 1983 Changed India Beyond Cricket
The 1983 World Cup victory did more than give India a trophy.
It changed cricket’s emotional market in India. It helped create a generation of children who saw cricket as a field of possibility. It strengthened the idea that India could beat the best in a global final. It became a reference point for future teams, sponsors, broadcasters, administrators, and fans.
Kapil’s image with the trophy at Lord’s became a national sporting memory. Before that, Indian cricket had pride, but not the same global event identity. After 1983, World Cups became part of India’s cricketing imagination.
That imagination produced long-term consequences. Sachin Tendulkar’s generation grew up in the shadow of 1983. India’s 2011 World Cup win carried emotional echoes of 1983. The expansion of cricket as a national obsession also drew strength from that moment.
Kapil did not create modern Indian cricket alone. No player does that. But he gave it one of its first great global proofs.
Comparing Kapil Dev With Other Great All-Rounders
Kapil Dev belongs in the elite all-rounder conversation because his career combines volume, durability, and historical impact.
Imran Khan had a stronger bowling average and a commanding leadership arc. Ian Botham had spectacular peaks and match-winning charisma. Richard Hadlee was one of the most precise fast bowlers the game has seen. Kapil’s case is different.
He carried a less pace-friendly system. He played for a team that was not as consistently strong overseas. He shouldered huge bowling responsibility. He scored more than 5,000 Test runs while taking more than 400 wickets. He captained a World Cup-winning team from outside the favorites.
That combination gives him a unique place.
The ICC groups him with Imran, Botham, and Hadlee as one of the great all-rounders of his time. That framing is accurate, but India’s context makes Kapil’s career even more remarkable.
Kapil was not simply India’s version of those players. He was India’s original fast-bowling all-rounder template.
The Worst Moments Did Not Shrink the Legacy
Every great career has shadows. Kapil’s had a few.
The 1987 World Cup semifinal exit hurt. His coaching tenure ended badly. The match-fixing allegation period was deeply painful, even though the CBI report found no evidence against him. His later public image sometimes became complicated by outspoken comments and the natural friction that follows legends who remain visible after retirement.
Yet those moments do not reduce the scale of his contribution. They make the story fuller.
Greatness in sport is rarely clean. It includes risk, criticism, failure, recovery, and reputation battles. Kapil’s career had all of that. The reason he remains so large in Indian cricket is that the achievements outweigh the wounds by a distance.
He gave India records. He gave India a World Cup. He gave India a fast-bowling dream. He gave India an all-rounder’s model. He gave India a fearless sporting memory.
Kapil Dev’s Place in Indian Cricket Today
Kapil Dev’s legacy has changed shape over time.
For older fans, he is the captain who lifted the 1983 World Cup. For cricket historians, he is the all-rounder who completed one of Test cricket’s rarest doubles. For fast bowlers, he is a pioneer. For Indian cricket’s commercial history, he is part of the moment that helped cricket become a national emotional economy.
For younger fans, Kapil may sometimes feel like a figure from archive clips and anniversary specials. That is why his numbers and context need repeating.
He played 131 Tests and 225 ODIs. He took 687 international wickets across Tests and ODIs. He scored more than 9,000 international runs across the two formats available to him. He held a Test wicket world record. He was India’s first World Cup-winning captain. He played one of the greatest ODI innings ever.
Those are not nostalgic claims. They are hard cricket facts.
The greater point is this: Kapil Dev helped Indian cricket walk differently.
Before him, India could win. After him, India could dream bigger.
Final Take
Kapil Dev’s tribute cannot be contained by one innings, one catch, or one trophy.
The 175 not out against Zimbabwe saved India’s 1983 World Cup campaign. The catch of Viv Richards helped turn the final. The Lord’s trophy lift gave Indian cricket one of its defining images. The 434 Test wickets gave him a world record. The 5,248 Test runs and 400-plus wickets gave him a statistical identity no other Test cricketer has matched in the same way.
His worst moments were real. The 1987 disappointment, the difficult coaching exit, and the match-fixing allegation period all belong in the record. The CBI’s finding of no evidence against him is just as important to that record.
Kapil Dev remains one of Indian cricket’s most important lives because he changed what the country thought was possible.
He was not polished into greatness by a perfect system.
He ran in anyway.
He swung the ball anyway.
He hit back anyway.
And in 1983, he made Indian cricket believe the world could be beaten.
For more cricket stories, records, match reports, and long-form features, visit The Sports Encounter’s Cricket section.
FAQs About Kapil Dev
Who is Kapil Dev?
Kapil Dev is a former Indian cricket captain and fast-bowling all-rounder. He is best known for leading India to its first Cricket World Cup title in 1983 and for becoming one of the greatest all-rounders in cricket history.
What are Kapil Dev’s major cricket records?
Kapil Dev scored 5,248 runs and took 434 wickets in Test cricket. In ODIs, he scored 3,783 runs and took 253 wickets. He was the first cricketer to complete the Test double of more than 5,000 runs and 400 wickets.
Why is Kapil Dev’s 175 not out against Zimbabwe famous?
Kapil Dev’s 175 not out against Zimbabwe in the 1983 World Cup is famous because India were struggling at 17 for 5 before he rescued the innings. India won the match by 31 runs, and the victory helped keep their World Cup campaign alive.
What was Kapil Dev’s role in India’s 1983 World Cup win?
Kapil Dev captained India during the 1983 World Cup. He played a key role with bat, ball, fielding, and leadership. His catch to dismiss Viv Richards in the final against West Indies became one of Indian cricket’s most iconic moments.
How many Test wickets did Kapil Dev take?
Kapil Dev took 434 wickets in Test cricket. At the time of his retirement, he held the world record for the most Test wickets.
How many runs did Kapil Dev score in Test cricket?
Kapil Dev scored 5,248 runs in Test cricket, including eight centuries. His batting was especially valuable because he often played aggressive innings from the lower middle order.
Was Kapil Dev only important because of the 1983 World Cup?
No. The 1983 World Cup is his most famous achievement, but Kapil Dev’s legacy is much larger. He was India’s greatest fast-bowling all-rounder, a former Test wicket world-record holder, a major ODI performer, and a pioneer who changed how India viewed pace bowling and all-round cricket.
Did Kapil Dev face difficult moments in his career?
Yes. Kapil Dev faced criticism after India’s 1987 World Cup semifinal exit, had a difficult coaching stint from 1999 to 2000, and was affected by match-fixing allegations during that period. The CBI later found no evidence of his role in match-fixing and related malpractice.
What honors has Kapil Dev received?
Kapil Dev was inducted into the ICC Cricket Hall of Fame, named Wisden Indian Cricketer of the Century in 2002, and received the BCCI’s C.K. Nayudu Lifetime Achievement Award.
What did Kapil Dev bring to Indian cricket?
Kapil Dev brought fast-bowling belief, all-round balance, attacking confidence, athletic fielding, and fearless leadership to Indian cricket. His 1983 World Cup triumph gave India a new sense of possibility on the global stage.
Breaking News
India Hit New T20I Low as England Storm to 125-Run Win
England posted 201-7 at Trent Bridge before Jofra Archer and Josh Tongue ripped through India’s chase in a record 125-run T20I defeat.
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.
Cricket
Babar Azam Returns as Test Captain: Is Pakistan’s Red-Ball Crisis Over?
Babar Azam has returned as Pakistan Test captain after Shan Masood’s disastrous run, but the real story is how PCB’s constant captaincy shuffle damaged Pakistan’s red-ball cricket and Babar’s own form.
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.
Cricket
Jacob Bethell Shines as England Muster India in 2nd T20I to Go One Up
Jacob Bethell produced a stunning unbeaten 76 as England recovered from 1/2 to beat India by four wickets in the 2nd T20I at Old Trafford.
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.
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.
