Fast-bowler Lasith Malinga continued his rich vein of form as he rattled the Deccan Chargers batsmen with three wickets to guide Mumbai Indians to a 37-run win.
Chasing 173, Deccan lost opener Sunny Sohal early, but fought back courtesy Shikhar Dhawan and Kumar Sangakkara. The former Sri Lanka captain top-scored (34) and Dhawan made 25. However, both the well-set batsmen were dismissed by Malinga. Late efforts by Daniel Christian (21) and Amit Mishra (25) proved futile as the visitors established their stranglehold on the contest.
Earlier, Mumbai got off to a fine start thanks to Davy Jacobs (32) and Sachin Tendulkar (28). However, their dismissal saw a flurry of wickets reducing the visitors to 70 for four. But Rohit Sharma and Andrew Symonds combined to put on 102 for the fifth wicket as Mumbai staged a remarkable comeback. Sharma top-scored with 56 to propel Mumbai to a competitive total. Mishra picked up two wickets for Mumbai.
Marsh’s effort proves futile
Shaun Marsh’s 46-ball 95 was not enough to enable Kings XI Punjab overhaul Delhi Daredevil’s target of 232, as the visitors fell 29 runs short.
Punjab lost Paul Valthaty but were propelled by a brilliant partnership between Marsh and Adam Gilchrist who put on 72 in just 40 deliveries.
After the former Australia wicket-keeper’s dismissal, Dinesh Karthik fell early to Ajit Agarkar. None of the Punjab batsmen were able to support Marsh in his lone vigil, as he continued to put the Delhi bowlers to the sword. Veteran fast-bowler Agarkar was the most successful bowler for the hosts picking up two wickets.
Earlier, Delhi were off to a fantastic start courtesy Virender Sehwag and David Warner, who both made 77 and put on a 146-run opening partnership.
The dynamic duo punished the Punjab bowlers, hitting them to all parts of the park before being separated in the 12th over with Hussey (one for 19) dismissing Sehwag.
Published in The Express Tribune, April 25th, 2011.
COMMENTS
Comments are moderated and generally will be posted if they are on-topic and not abusive.
For more information, please see our Comments FAQ