News
Former India cricketer Irfan Pathan questioned why Jasprit Bumrah's workload was managed whereas Ben Stokes bowled himself to the ground in Lord's.
The former Indian pacer stated that the injury-prone England captain's workhorse spells across both innings in the Lord's ...
26m
CricTracker on MSNENG vs IND 2025: 'No talk of workload with Stokes' - Irfan Pathan questions India's usage of Jasprit Bumrah at Lord's"Archer was playing a Test match after four years but he did not stop. He bowled a six-over spell in the morning," said Irfan ...
After India's 22-run defeat to England in the third Test at Lord's, former cricketer Irfan Pathan highlighted the difference ...
Jasprit Bumrah showed tremendous grit and determination to survive in the middle for 54 balls. But in the end, a loose shot ...
10h
India Today on MSNAt Lord's, India's defiance crafts a tale greater than victoryRavindra Jadeja, Jasprit Bumrah, and Mohammed Siraj fight to the last ball, turning a Test match defeat into a timeless saga ...
India would have had a fair chance of winning the Lord's Test if they had forced England into taking the second new ball.
England Test captain Ben Stokes classified tearaway Jofra Archer's blistering spell in the opening hour as the moment that ...
With Lord’s Test on the line, England’s injury-prone captain Ben Stokes threw workload management out of the window to bowl two marathon spells on day five, raising the benchmark not just for his own ...
Ravindra Jadeja's fight went in vain as England picked up a famous 22-run win against India in the third Test at the Lord's ...
8h
ESPN Cricinfo on MSNSix years on from World Cup glory, Stokes and Archer light up Lord's againOn the sixth anniversary of England's 2019 ODI World Cup win, on the final day at Lord's, with six wickets to get before ...
England captain Ben Stokes says he never thought about stopping during his mammoth bowling spells that helped seal the third Test win over India at Lord's.
Some results have been hidden because they may be inaccessible to you
Show inaccessible results