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 Champions Trophy 2024/25, AUS vs IND 1st Semi-Final Match Report, March 04, 2025 – Jiaa News
Jia Meena
Jiaa News is a collecting news throughout the Global and sharing them for our readers.
India 267 for 6 (Kohli 84, Iyer 45, Rahul 42*, Ellis 2-49, Zampa 2-60) beat Australia 264 (Smith 73, Carey 61, Shami 3-48, Jadeja 2-40, Varun 2-49) by five wickets
Dubai will host the final of the Champions Trophy, and India will be in it, after proving their edge over a weakened Australia side in an absorbing first semi-final. Their win wasn’t achieved without a fight, however, and Australia may yet look back on several moments that could have moved the contest in other, tantalising directions.
In the end, India’s quality and experience made the telling difference, and the member of their line-up who most embodies those words was a central figure. Virat Kohli had made one of his trademark chase-controlling hundreds earlier in the tournament, against Pakistan, and seemed set for another here, only for an uncharacteristic attempt at a big hit to cut his innings short at 84. By then, however, he had passed 8000 runs in ODI chases, and whittled this one down to a more-than-manageable 40 off 44 balls.
They only needed 33 of those balls, as KL Rahul and Hardik Pandya all but sealed the deal before the latter departed with India one hit away. And as in a similar chase during the Chennai World Cup clash between these sides in 2023, it was Rahul who finished things off, this time with a six over long-on off Glenn Maxwell.