IPL 2026: Suryakumar Yadav Acknowledges MI's Batting Deficit Against DC

Share:
Audio Loading voice…
IPL 2026: Suryakumar Yadav Acknowledges MI's Batting Deficit Against DC

Synopsis

In a recent match, Mumbai Indians' stand-in captain Suryakumar Yadav admitted that his team was 15-20 runs short in their batting performance, leading to a six-wicket loss to the Delhi Capitals. Discover how MI plans to bounce back in their upcoming game.

Key Takeaways

MI fell short by 15-20 runs in their batting effort against DC.
Suryakumar Yadav scored 51 runs , making him the top scorer for MI.
Sameer Rizvi's outstanding performance with 90 runs helped DC chase down the target.
MI aimed for a target of 180-185 but fell short.
MI plans to regroup and focus on strategies for their next match against the Rajasthan Royals.

New Delhi, April 4 (NationPress) Suryakumar Yadav, the acting captain of the Mumbai Indians (MI), acknowledged that his team fell short by 15-20 runs with the bat, contributing to their six-wicket defeat against the Delhi Capitals (DC) at the Arun Jaitley Stadium on Saturday.

On a challenging pitch where scoring opportunities were limited, Suryakumar emerged as the top scorer for MI with 51 runs, helping the team post a total of 162/6. However, DC successfully chased down the target as the conditions improved for batting under lights, with Sameer Rizvi making an impressive 90.

“It was a reasonable wicket. We anticipated it might play a bit slow, yet from a batting standpoint, we were indeed 15-20 runs short. However, I don't wish to undermine the performance of their bowlers, and they also batted exceptionally well in the second half,” Suryakumar remarked post-match.

Regarding Rizvi’s consecutive fifties in the tournament, he stated, “Absolutely, I mean, coming in at 7 for 2 and batting the way he did, he deserves a lot of credit. He prevented us from getting into the match.”

Suryakumar observed that the pitch conditions remained consistent throughout both innings but credited the opposition for better adaptation. “I think the playing conditions were quite similar. It didn’t alter significantly, but the way they approached their innings was commendable. They understood the conditions exceptionally well during the second innings and played beautifully,” he noted.

He added that MI had aimed for a target of 180-185 as a competitive score but missed it. “We believed that 180-185 would be a solid score. We came up short by 15-20 runs. Naman and I both got out during crucial moments in the 16th and 18th overs; otherwise, we could have crossed the par score,” he elaborated.

Despite the loss, the captain remained hopeful as MI prepares to face the Rajasthan Royals in Guwahati on Tuesday. “There will be days like this when things don’t go as planned, but we will regroup, work diligently, and aim to bounce back in the next match,” he concluded.

Point of View

Suryakumar Yadav highlighted the challenges faced by the Mumbai Indians. His acknowledgment of a batting shortfall underscores the importance of adaptability in cricket. As the team prepares for their next challenge, the focus will undoubtedly shift to enhancing their performance.
NationPress
7 Jul 2026

Frequently Asked Questions

What was the score of the match between MI and DC?
Mumbai Indians scored 162/6, while Delhi Capitals successfully chased the target, winning by six wickets.
Who was the top scorer for MI in the match?
Suryakumar Yadav was the top scorer for Mumbai Indians with 51 runs.
What did Suryakumar Yadav say about the pitch conditions?
Suryakumar indicated that the pitch was decent but acknowledged that they were 15-20 runs short.
When will MI play their next match?
Mumbai Indians will face the Rajasthan Royals in Guwahati on Tuesday.
What was Sameer Rizvi's contribution in the match?
Sameer Rizvi scored a remarkable 90 runs for Delhi Capitals.
Nation Press
The Trail

Connected Dots

Tracing the thread behind this story — newest first.

8 Dots
  1. Latest 3 months ago
  2. 3 months ago
  3. 3 months ago
  4. 3 months ago
  5. 3 months ago
  6. 3 months ago
  7. 1 year ago
  8. 1 year ago
Google Prefer NP
On Google