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 – BAN vs NEP 37th Match, Group D, June 16, 2024 – Jiaa News

Match Report – BAN vs NEP 37th Match, Group D, June 16, 2024

Toss Nepal chose to bowl against Bangladesh

At the ground where their spinners tamed South Africa, Nepal won the toss and asked Bangladesh to bat. Nepal made one change to the side they fielded in their last game, with batter Sundeep Jora replacing fast bowling allrounder Karan KC. Bangladesh have not made any changes to their XI from their win against Netherlands in Kingstown.

Nepal captain Rohit Paudel said that they want to give their bowlers the best conditions, saying that he expects dew in the second innings.

Samuel Badree in his pitch report said variable bounce is expected, as in the Nepal-South Africa match, and that spinners could dictate proceedings again.

A win for Bangladesh will see them make it to the Super Eight stage, but if Nepal win today, Netherlands could pip Bangladesh if they beat Sri Lanka in Gros Islet, in the game that starts an hour after this one.

Bangladesh: 1 Tanzid Hasan, 2 Najmul Hosain Shanto (capt), 3 Litton Das (wk), 4 Shakib Al Hasan, 5 Towhid Hridoy, 6 Mahmudullah, 7 Jaker Ali, 8 Rishad Hossain, 9 Tanzim Hasan, 10 Taskin Ahmed 11 Mustafizur Rahman.

Nepal: 1 Kushal Bhurtel, 2 Aasif Sheikh (wk), 3 Rohit Paudel (capt), 4 Anil Sah, 5 Dipendra Singh Airee, 6 Kushal Malla, 7 Gulsan Jha, 8 Sompal Kami, 9 Sundeep Jora, 10 Sandeep Lamichhane, 11 Abinash Bohara.

Uncategorized
Comments (0)
Add Comment