Rain Ruins Durham: Abhishek's 59, Iyer's 68, and Five Questions Left Unanswered

 

Durham has a history of doing this. The Riverside Ground has seen more international matches ended by rain than most venues in England, and on Tuesday evening it did it again — this time to one of the most anticipated T20Is of the summer. India posted 189 for 7 from their 20 overs, Shreyas Iyer top-scored with 68 and Abhishek Sharma blazed a 24-ball 59 in the powerplay, Saqib Mahmood took three wickets on his England comeback — and then the heavens opened, the covers came out, and the match was abandoned without England facing a single delivery. No result. No winner. A good cricket match reduced to a statistic.

It is the third time an international match in Durham has been washed out after the first side has batted. The ground's record in this regard is beginning to feel less like bad luck and more like a structural problem. But the cricket that did happen on Tuesday told several genuinely interesting stories — and with the series now moving to Nottingham for the second T20I, all of them will have consequences.

Abhishek Sharma in Six Overs: The Innings That Changed the Match

India lost the toss — Harry Brook called correctly and asked India to bat — and then immediately lost both openers inside the first two overs. Sanju Samson was brilliantly caught at backward point by Tom Banton off Saqib Mahmood's second ball of the match, for 5. His last three scores for India now read 5, 0, and 1. In the very next over, Ishan Kishan was run out — for the second innings in succession — and India were six for two inside two overs on a pitch that had something in it for the seamers.

At that point, with a new captain already under scrutiny and a bowling attack that had just been 2-0'd by Ireland, India needed something to steady the innings. What they got instead was Abhishek Sharma, who appeared to have decided that the pitch, the conditions, and the situation were entirely someone else's problem. His 59 came off 24 balls. He hit six fours and three sixes. He reached his fifty off 20 balls — among the fastest T20I half-centuries an Indian batter has made in England. By the time he was brilliantly caught at deep square leg off Adil Rashid in the eighth over, India had 63 on the board and the match had already tilted in their direction.

Abhishek's innings was the kind of powerplay assault that reframes a T20 match completely. India had gone from crisis to platform in the space of a single partnership — 57 runs in 22 balls between Abhishek and Shreyas Iyer for the third wicket — and England never fully recovered their grip on the game from that moment.

Shreyas Iyer's 68: The Captain Answers His Critics

Whatever you thought of Iyer coming into this series — and after losing 2-0 to Ireland and publicly admitting India had not done their homework on conditions, there was plenty to criticise — his innings on Tuesday was an answer of sorts. Not a complete answer, but a meaningful one.

He came in at three with India still fragile at six for two and played the first 15 balls of his innings with unusual care, rotating strike and leaving the boundary hitting to Abhishek. Once the platform was set, Iyer opened up: he reached his fifty off 38 balls, then accelerated sharply through the middle overs, taking on Rashid and Liam Livingstone with reverse sweeps and ramps that England had no answer to. His 68 came off 44 balls and included nine fours. He was eventually trapped lbw by Rashid attempting an ill-advised slog across the line — a dismissal that would have irritated him — but the innings had already done its job. India's total of 189 for 7 was a strong one on a surface that was offering movement early and turn late.

It is worth noting the context. As we wrote in our preview of this series, Iyer came into this tour having lost immediately to Ireland after replacing Suryakumar Yadav as captain. The pressure on him to perform both as a leader and as a batter was significant. A score of 68 in difficult early conditions, built with intelligence and capped with some excellent hitting, is not nothing. The captaincy decisions — winning the toss, backing his bowlers in the right sequences, reviewing intelligently — were also competent without being spectacular. Iyer still needs more, but Tuesday was a start.

Saqib Mahmood's Return — and What It Means

The other major subplot of the evening was Saqib Mahmood's return to England colours after more than a year away. The 28-year-old Lancashire seamer had played his last England match in September 2025, a Lord's ODI against South Africa, where he finished with 0 for 53 and then immediately underwent left knee surgery. He missed the SA20, the Ireland T20I tour, and England's T20 World Cup campaign at the start of 2026 — a frustrating period of rehabilitation that included an England Lions return and pre-season red-ball work with Lancashire before he was finally cleared fit for this series.

On Tuesday he repaid the faith with 3 for 33 — his first T20I wickets in over a year. The three dismissals were spread across the innings: Samson in the second over to capitalise on early movement, a middle-overs breakthrough, and a death-overs scalp to restrict India's late acceleration. The wickets were different types, required different skills, and suggested a bowler who was properly fit and properly match-ready rather than one still finding his rhythm. His spell in overs 17-19 was particularly impressive, conceding only 11 runs while taking one wicket against a batting lineup that was trying to push the total past 200.

For England this matters beyond this series. Jofra Archer has been managing his workload carefully, and England have needed a reliable second seam option in T20Is for two years. If Mahmood can stay fit, he provides exactly that — right-arm pace at the death, intelligent variation in the powerplay, and enough quality to take wickets in all three phases. Tuesday suggested the surgery has not cost him anything. Whether his knee holds over a full summer of cricket is a different question, but the signs were encouraging.

Shivam Dube's 42: The Finishing Act

With India seven down and still four overs remaining, Shivam Dube walked in and hit 42 off 23 balls — an innings that pushed India from a competitive total to a genuinely strong one. His hitting in the final three overs, particularly against Jordan Cox and Livingstone, was clean and powerful. Three sixes in the last two overs turned what might have been 178 into 189, and on a surface like Durham's that difference matters. It is easy to overlook a lower-order cameo like Dube's against a top score of 68 and a powerplay of 61 — but the final total of 189 owed as much to those 23 balls at the death as to anything that came before.

Sooryavanshi: Still Waiting

The question that dominated pre-match coverage was whether Vaibhav Sooryavanshi would make his T20I debut at Durham. He did not play. India went with the expected batting order — Abhishek Sharma and Sanju Samson opening, Ishan Kishan at three — and Sooryavanshi remained on the bench, still waiting for his moment.

As we noted in our series preview, Sooryavanshi was always likely to have to wait — India's opening combination was established and in form coming into this tour, despite the Ireland series. The question is whether Tuesday changes the calculation. Samson's 5 from two balls — his third consecutive single-digit score — will intensify the debate heading into Nottingham. Former India players have already publicly argued that Sooryavanshi's X-factor is too valuable to leave on the bench when the established combination is failing. Aakash Chopra suggested on his YouTube channel that Samson is the opener Sooryavanshi would replace. Whether the selectors agree — and whether Iyer has the authority to make that call — is the biggest selection story going into the second T20I. Dale Steyn made his famous prediction about where Sooryavanshi's career is headed — and on this evidence, the argument for fast-tracking him into the starting XI is only getting stronger.

What Durham Actually Told Us

A no-result match is always frustrating — for fans, for players, and for anyone trying to draw definitive conclusions. But Tuesday was not without information. India's top order is brittle at the top — two wickets for six runs in two overs is not the platform a strong batting lineup should require Abhishek Sharma to rescue. Iyer can bat and can captain, but one good innings against a weakened bowling attack on a used pitch does not fully answer the Ireland questions. Samson is in serious form trouble and will face the hardest selection conversation of the series before Nottingham.

For England, Mahmood's return is the headline. Brook's captaincy was competent in the field — his bowling rotations were sensible and his DRS use was measured — but a total of 189 to chase at Durham on a good surface was manageable, and England never got the chance to find out whether their batting order, which includes Phil Salt, Jos Buttler and Liam Livingstone, would have handled it. The rain denied us that answer.

The second T20I at Trent Bridge — the same ground where Ben Stokes' Test captaincy ended on Sunday, a story we covered in full detail here — now carries more weight than a second game in a five-match series normally would. With the first match producing no result, both sides need to win in Nottingham to avoid falling behind. And with the Sooryavanshi question still unanswered and Samson's place under serious pressure, the selection story alone is enough to make it unmissable.

Should India replace Sanju Samson with Vaibhav Sooryavanshi for the second T20I at Nottingham? And does the no-result at Durham put more pressure on Shreyas Iyer than a defeat would have? Drop your thoughts in the comments.