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
Match Report – IND vs IRE 8th Match, Group A, June 05, 2024 – Jiaa News

Match Report – IND vs IRE 8th Match, Group A, June 05, 2024

India 97 for 2 (Rohit 52, Pant 36*) beat Ireland 96 (Delany 26, Hardik 3-27, Bumrah 2-6) by eight wickets

New York’s second match as a T20I venue was a lot like its first: low-scoring and brutal. Two days after South Africa bowled Sri Lanka out for 77 here, India bowled Ireland out for 96. A different strip was used for this game, but the bounce was just as inconsistent, and batting just as difficult, if not outright dangerous.

India’s selection was spot-on – they picked four fast bowlers including Hardik Pandya, and two spin-bowling allrounders to lengthen their batting, which meant they left Kuldeep Yadav on the bench. They didn’t need all that batting in the end, as Rohit Sharma and Rishabh Pant helped them cross the line with 46 balls remaining, but the packed pace attack proved extremely useful. Arshdeep Singh, Mohammed Siraj, Jasprit Bumrah and Hardik picked up 8 for 81 between them, extracting seam movement and up-and-down bounce right through an Ireland innings that lasted just 16 overs.

As good as those performances were, though, this match will be remembered for the conditions. Batters from both teams took body blows – Rohit retired hurt on 52, soon after being struck on the arm – and by the time India wrapped up their win, their thoughts may have gone ahead to June 9 at the same venue, and what kind of pitch they may have to play Pakistan on.

Uncategorized
Comments (0)
Add Comment