Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the acf domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /www/wwwroot/livecricket.cricket/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the masterslider domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /www/wwwroot/livecricket.cricket/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-bulk-delete domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /www/wwwroot/livecricket.cricket/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the jetpack domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /www/wwwroot/livecricket.cricket/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the publisher domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /www/wwwroot/livecricket.cricket/wp-includes/functions.php on line 6121
IPL 2024 – Hardik Pandya banned for MI’s slow over rate, will miss first game next season – Jiaa News
Jia Meena
Jiaa News is a collecting news throughout the Global and sharing them for our readers.

IPL 2024 – Hardik Pandya banned for MI’s slow over rate, will miss first game next season

0 20
Hardik Pandya, the Mumbai Indians captain, has been banned for one match for his team’s slow over rate against Lucknow Super Giants at the Wankhede Stadium. MI have already played their last match of IPL 2024, which means Hardik will miss the team’s first match next season.

In case Hardik moves to another team for the next season, he will miss that particular team’s first game.

It was the third time this IPL that MI failed to maintain a minimum over rate. As a result, Hardik, apart from the one-match ban, was fined INR 30 lakhs and the rest of the playing XII, including the Impact Player, were each individually fined either INR 12 lakhs or 50% of their respective match fees, whichever is lesser.

It was a forgettable season for both MI and Hardik. The 18-run defeat to LSG meant MI finished with just four wins from their 14 games and finished at the bottom of the points table. Hardik, who had come in as a pre-season trade and had taken over captaincy from Rohit Sharma, was booed by the Wankhede crowd throughout the tournament. On the field, he scored 216 runs at an average of 18.00 and a strike rate of 143.04. With the ball, he took 11 wickets at an economy of 10.75.

Mark Boucher, MI head coach, also admitted that the off-field noise might have “clouded” Hardik and played a part in the team’s “below-par” performance.

Leave a Reply