ICC Cricket World Cup 2019 (Match 26): Australia vs Bangladesh – Statistical Highlights

Published - 21 Jun 2019, 12:48 PM | Updated - 23 Aug 2024, 04:00 AM

Australia, Bangladesh, Cricket World Cup
Image Credit: Twitter

On Thursday (20th June), Australia clinched a 48-run victory in the high-scoring match against Bangladesh in the match 26 of the 2019 ICC Men’s Cricket World Cup at Nottingham.

Australia managed to score 381/5 (50 overs) in the first innings. Chasing down that target, Bangladesh scored 333/8 (50 overs).

Brief Scores: Australia – 381/5 in 50 overs (David Warner 166, Usman Khawaja 89; Soumya Sarkar 3/58)

Bangladesh – 333/8 in 50 overs (Mushfiqur Rahim 102*, Mahmudullah 69; Marcus Stoinis 2/54)

Result – Australia won by 48 runs

Here are some of the statistical highlights of the match:

Teams’ stats

Australia vs Bangladesh

i) The aggregate total of this match was 714 runs which is the highest aggregate total in a Cricket World Cup match. The previous highest aggregate total in CWC history was 688 runs during the match between Australia and Sri Lanka at Sydney on 8th March 2015.

Australia

i) Australia scored 381/5 (50 overs) in the first innings. It is the third highest total for Australia in ODI history. Their top two highest ODI totals are 434/4 (50 overs) against South Africa at Johannesburg on 12th March 2006 and 417/6 (50 overs) against Afghanistan at Perth on 4th March 2015.

ii) Australia won this match by 48 runs which is their smallest victory (by runs) against Bangladesh in ODI history. Their previous smallest ODI victory (by runs) against Bangladesh was winning by 60 runs (at Dhaka on 9th April 2011).

Bangladesh

i) In the second innings, Bangladesh managed to score 333/8 (50 overs) which is their highest ODI total. Their previous highest ODI total was 330/6 (50 overs) against South Africa at The Oval on 2nd June 2019.

Players’ stats

Australia

i) Opening batsman David Warner scored 166 runs. This innings is the second highest individual score by an Australian batsman in Cricket World Cup history. The record is 178 by David Warner against Afghanistan at Perth on 4th March 2015. Also, it is the second highest individual ODI score by an Australian batsman against Bangladesh as the record is 185* by Shane Watson (at Dhaka on 11th April 2011).

Australia, Bangladesh, Cricket World Cup
David Warner (Image Credit: Twitter)

ii) David Warner is the first batsman to play two 150+ scores in CWC history.

iii) This 166-run was David Warner’s sixth 150+ score in ODI career. Only Rohit Sharma (India) has scored more 150+ ODI scores than Warner. Till the date, Rohit Sharma has scored seven ODI 150+ scores.

iv) By the end of this match, the left-arm pacer Mitchell Starc has taken 37 wickets in Cricket World Cup. Among the Australian bowlers, only the former Australian pacer Glenn McGrath (71 wickets) picked up more CWC wickets than Starc.

Mitchell Starc (Image Credit: Google)

Bangladesh

i) Rubel Hossain had the bowling figures of 9-0-83-0. It is the second most expensive bowling figures in Cricket World Cup history by a Bangladesh bowler. The record holder is Abdur Razzak with the bowling figures of 10-0-86-1 against Sri Lanka in 2007 ICC Cricket World Cup.

Rubel Hossain (Image Credit: Google)

ii) Mushfiqur Rahim, the Bangladesh wicketkeeper-batsman, was not out on 102 runs. It is the highest individual ODI score by a Bangladesh batsman against Australia. The previous record holder was Mohammad Ashraful with 100 runs (at Cardiff on 18th June 2005). Also, Mushfiqur Rahim’s 102* is the second highest individual CWC score for a wicketkeeper-batsman against Australia. The record is 104 runs by Kumar Sangakkara (Sri Lanka) at Sydney on 8th March 2015.

Australia, Bangladesh, Cricket World Cup
Mshfiqur Rahim (Image Credit: Twitter)

Tagged:

ICC World Cup 2019 Mitchell Starc Mushfiqur Rahim Rubel Hossain Statistical Highlights
logo
Stay Updated with the Latest Cricket News from Cricket Addictor.

You will receive the latest updates on cricket news throughout the day. You can manage them whenever you need in browser settings.