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
Tom Bruce makes 345, third-highest score in New Zealand history – Jiaa News

Tom Bruce makes 345, third-highest score in New Zealand history

Bruce, who has played 17 T20Is, faced 401 balls and hit 36 fours alongside six sixes. Only one player, Bert Sutcliffe, has higher scores than Bruce in the New Zealand game with 355 and 385 for Otago.

Having been unbeaten on 212 after the first day, he brought up his triple-century with a dab into the leg side from his 379th delivery.

When Bruce went to 339, he surpassed Roger Blunt’s 1931-32 score, also for Otago, having previously moved past Dean Brownlie (334 in 2014-15) and Devon Conway (327 not out in 2019-2020). Michael Papps and Peter Fulton also have triple-centuries in New Zealand’s domestic cricket.

Bruce had come to the crease with his team 29 for 2, which became 75 for 3. He then added 292 with Dane Cleaver for the fourth wickets and 303 with Josh Clarkson for the fifth – both new records for Central Stags – before finally being caught down the leg side sweeping at Louis Delport. The Auckland players quickly made their way towards Bruce to congratulate him.

Overall, it was the 11th century of Bruce’s first-class career. On the opening day, he went past 6000 first-class runs.

Uncategorized
Comments (0)
Add Comment