Follow us

Sport

IPL 2018: Here's why Ravindra Jadeja didn't celebrate after taking Virat Kohli's wicket

Jadeja said that he wasn't ready for a celebration because he dismissed Kohli on the first ball of his spell

Prabhjeet Singh Sethi 6 May 2018, 6:43 PM
Jadeja took three crucial wickets against Royal Challengers Bangalore on Saturday

Jadeja took three crucial wickets against Royal Challengers Bangalore on Saturday Image: AFP

After a poor run this Indian Premier League (IPL), Ravindra Jadeja finally found his mojo with a wicket of Royal Challengers Bangalore (RCB) captain Virat Kohli on Saturday.

But there's something Twitter is busy losing sleep over. Why didn't Jadeja celebrate after knocking off Kohli's stumps?

For those who are still wondering why, Jadeja has an explanation. Soon after the RCB innings, he said, "It was my first ball and I was not ready to celebrate. Virat's wicket is always a huge wicket, I was thinking I got a good wicket."

Further giving credit to veteran off-spinner Harbhajan Singh for bowling exceptionally well from the other end, he said, "Bhajji from the other end was also bowling very well, he took the important wicket of ABD. We bowled as a pair and that is required as a bowling unit. We have a very good batting line-up so we should not worry about the total much. We need to bat the 20 overs and we will get the desired result."

Jadeja dismissed Kohli with a quicker one. The RCB captain tried to cut a good length delivery behind square, but ended up losing his wicket to an exceptional delivery that rammed into the stumps.

Read More:

IPL: Jadeja gets roasted after dropping catches against KKR

Watch video: Shoe hurled at CSK player Ravindra Jadeja

Dhoni told me I have the ability of a proper batsman: Jadeja

Trending stories

BACK TO TOP
We use cookies to enhance your experience on our website by showing you relevant ads and content. By continuing your navigation, you accept the placement and use of cookies. To learn more about cookies and/ or to opt-out of these services, please see our Cookie Policy.