ALSO READIPL 2018: Jason Roy's 91 gets Delhi their first win; beat MI by 7 wickets IPL 2018: Don't bite your nails, Mumbai, you are used to losing thrillers IPL 2018: Why Gambhir failed to turn things around for Delhi Daredevils IPL 2018: Mumbai Indians snatched defeat from jaws of victory against CSK IPL 2018: Bravo, CSK! Mumbai Indians lose opening match by 1 wicket
Yet another cliffhanger involving Mumbai Indians, and yet another defeat for them. After losing the first one to Chennai Super Kings and the second to Sunrisers Hyderabad, Mumbai Indians managed to do the same in their third clash of Indian Premier League 2018 (IPL 2018) – this time against Delhi Daredevils.
No matter whom they play against, where they play, what combinations they try, Mumbai Indians manage to get the same result – a defeat after an exciting contest that drags the match up to the last over. Indeed, three defeats in a row seem rather unbecoming of a team that is playing to defend its title. The latest tie where Mumbai Indians played against Delhi Daredevils was an important battle for both the teams. Both were searching their first win of IPL 2018. Both had lost their previous two matches against different opponents.
Gautam Gambhir invited MI to bat first and MI were off to the best start in IPL — 84/0 in 6 overs. They crossed 100 within 9 overs and looked set to breach 200, but they could not. After the dismissal of the openers, Suryakumar Yadav and Evin Lewis, no other batsman could capitalise on the platform that had been built. And that included captain Rohit Sharma.
Ishan Kishan and Rohit Sharma got together, started building a partnership. Kishan even got a few strokes right but then he got carried away and threw way his wicket after scoring 44. That is not a bad score, but the way he got out and the temperament behind that was very unfortunate. He could have turned this 44 into a 80+ score, but he got careless. The captaincy and performance of Rohit Sharma also deserve criticism. Despite demoting himself in the order, he failed to click. He was not in good touch at all, and he did not look like the responsible player he once used to be.
Kieron Pollard came and went in a matter of one ball. He just didn't care to take a moment and analyse the situation. He came in, decided to play a shot and ended up losing his wicket – not something worthy of his T20 stature. The Pandya brothers did nothing much and went cheaply. Perhaps the entire Mumbai team took DD a bit too lightly. When the score was 194-7 after 20, they must have thought the match was theirs to win.
Not a sub-par total, but it should have been much more, given the start MI had got.
While bowling, the Mumbai bowlers seemed to be playing a good host at Wankhede, ensuring Delhi batsmen had no trouble playing their shots. Hardik Pandya, Mayank Markande leaked runs like water. Poor economy, no discipline in bowling, some sloppy fielding and sub-par captaincy made Delhi win the match easily.
Only three wickets fell, and though Delhi dragged the match to the last ball, they never seemed like losing it. Every batsman that came in to bat settled quickly and played sensibly. Delhi batsmen did what Mumbai batsmen failed to do. A team that is three-time champion of the tournament and is currently the defending champion, is not supposed to play like Mumbai has been doing so far this season. Delhi did not win this game, Mumbai let then win it.