Site icon Cricfit

[Watch] Sai Sudarshan Gets Hit-Wicket In The Most Bizarre Fashion vs MI

Sai Sudarshan

Sai Sudarshan gets hit wicket (Credit: Twitter)

Gujarat Titans (GT) batter Sai Sudarshan got out in the most bizarre fashion during their game against bottom-placed Mumbai Indians (MI) on Friday night. Eventually, the dismissal put the Titans on the backfoot as they failed to chase down 178 runs despite a superb start by Wriddhiman Saha and Shubman Gill.

Saha and Gill put on a 106-run stand in just 12.1 overs to set the platform for the run chase. But Gujarat lost both their openers in the same over that pulled the brakes on the runs. Hardik Pandya and Sai Sudarshan tried to keep up the run-scoring spree but an unfortunate dismissal put the side under pressure.

The incident took place in the 16th over of the match when Kieron Pollard bowled a slower delivery of the surface. Sudarshan went hard on the pull and connects with thin air as the ball bounces over the edge. The bottom hand comes off the bat handle but Sai Sudharsan kept pivoting. He got off-balance as well and broke the stumps with his bat.

This is the first instance in IPL that a batter has got out hit-wicket, one of the most unfortunate ways of getting out. Mumbai Indians captain Rohit Sharma is pumped up as is the entire team.

Watch the clip here:

It all went downslide for Gujarat Titans from there as two run-outs cost them the match. The equation came down to nine runs needed off the final six deliveries and Daniel Sams gave away only three runs in the final over to hand Mumbai Indians a win.


“Two run-outs didn’t help me” – Gujarat Titans captain Hardik Pandya

The GT captain rued two run-outs as the reason behind their defeat against the five-time IPL champions. Speaking at the post-match presentation ceremony, the 28-year-old all-rounder said:

“We’ll take 9 runs in the last over on any given day, but the two run-outs didn’t help us. In T20 cricket you can’t keep losing back-to-back wickets, it pushes you back. It’s one of the games where we ended on the losing side. We kind of played 19.2 or 19.3 overs of good cricket, but losing wickets didn’t help us like I said before.”


Get the latest cricket news here and like us on Facebook, and follow us on Twitter and Instagram for more such updates.

Exit mobile version