Top 10 Bowlers Who Took Wickets But Lost the Match

Table of Contents

1. Mohammad Amir – 2017 Champions Trophy Final (vs India)

2. Bhuvneshwar Kumar – India vs South Africa, 2018 Jo’burg

3. Shaheen Afridi – Pakistan vs Australia, T20 World Cup 2021 Semi-Final

4. Lasith Malinga – MI vs CSK, IPL 2012

5. Kagiso Rabada – DC vs PBKS, IPL 2020

Why These Performances Matter

Can a bowler take multiple wickets and still lose the match?

Why don’t these performances get the recognition they deserve?

How common is it for top-performing bowlers to end up on the losing side?

Here are 10 legendary bowling spells where the bowlers took wickets but lost the match — efforts full of fire, but just not enough.

1. Mohammad Amir – 2017 Champions Trophy Final (vs India)

Took Wickets But Lost

Figures: 6-2-16-3

Amir blew away India’s top order — Kohli, Rohit, and Dhawan. A dream spell. But in another match against Australia in 2016, Amir bowled with fire and picked up 3 crucial wickets. Yet, Pakistan collapsed and lost the game.

Why It Hurt:

He took wickets but lost due to poor batting support. His fire was wasted.

2. Bhuvneshwar Kumar – India vs South Africa, 2018 Jo’burg

Figures: 10-2-44-3

Bhuvi was all swing and seam. He struck early, got middle-order scalps, and nearly gave India a strong defense. But fielding lapses and poor finishers let the game slip.

Why It Hurt:

He took wickets but lost due to lack of finishing by other bowlers and some poor field placements.

3. Shaheen Afridi – Pakistan vs Australia, T20 World Cup 2021 Semi-Final

Took Wickets But Lost

Early wickets — Warner & Finch

Shaheen started with fire, removing Finch and troubling Warner. But dropped catches and Matthew Wade’s late carnage ended Pakistan’s dream.

Why It Hurt:

Shaheen took wickets but lost — because Wade smashed 3 sixes in a row off Hasan Ali’s missed catch and Shaheen’s over.

4. Lasith Malinga – MI vs CSK, IPL 2012

Took Wickets But Lost

Figures: 4-0-16-2

Malinga nailed yorkers, took big wickets including Raina and Bravo. But Dhoni and Jadeja chased it down calmly in the last overs.

Why It Hurt:

Malinga took wickets but lost as his teammates leaked runs at the other end.

5. Kagiso Rabada – DC vs PBKS, IPL 2020

Took Wickets But Lost

Figures: 4-0-26-2

Rabada struck twice at crucial points, but Mayank Agarwal’s blinder and a Super Over twist turned it around. Despite Rabada bowling the Super Over — DC still lost.

6. Mitchell Starc – Australia vs New Zealand, 2015 WC Group Stage

Took Wickets But Lost

Figures: 9-0-28-6

Starc ripped through the Kiwi lineup and nearly won it single-handedly. But lack of runs (Australia were bowled out for 151) cost them.

Why It Hurt:

Starc took wickets but lost despite producing one of the best World Cup spells.

7. Ravi Rampaul – WI vs India, 2011 WC

Took Wickets But Lost

Figures: 10-1-51-5

Rampaul was unplayable. Took Sehwag, Kohli, and Yuvraj. But India posted 268, and WI failed with the bat.

Why It Hurt:

He took wickets but lost in a tournament that badly needed West Indies wins.

8. Umesh Yadav – RCB vs KKR, IPL 2018

Took Wickets But Lost

Figures: 4-0-27-3

Umesh gave RCB a golden start. But the batting flopped, and Andre Russell’s monster finish stole it.

Why It Hurt:

Umesh took wickets but lost in a game RCB should’ve sealed.

9. Mustafizur Rahman – Bangladesh vs India, T20 Asia Cup 2016

Took Wickets But Lost

Figures: 4-0-24-2

Mustafizur bowled with variation, dismissed Rohit and Yuvraj, but India chased it with ease due to lack of support from others.

Why It Hurt:

He took wickets but lost, despite being the best bowler on the field.

10. Josh Hazlewood – CSK vs DC, IPL 2021 Qualifier

Took Wickets But Lost

Figures: 4-0-29-2

Hazlewood got Dhawan and Hetmyer but couldn’t stop Dhoni and Gaikwad’s rampage in the end.

Why It Hurt:

He took wickets but lost, and DC missed out on a place in the IPL final.

Why It Hurt:

He took wickets but lost — even in the Super Over. One of IPL’s cruel endings.

Why These Performances Matter

They show individual brilliance.

They prove that cricket needs more than one hero.

They teach resilience — even in defeat.

In a sport that glorifies winning, these stories show the other side — bowlers who gave everything but still ended up on the losing team. When you take wickets but lose, it cuts deep — but it also earns respect. These bowlers didn’t fail. The match did.

Whether it’s Amir’s fire, Shaheen’s heartbreak, or Rabada’s unlucky Super Over — these took wickets but lost moments are etched into the emotional side of cricket.

FAQ – Why bowlers face such Situations

Can a bowler take multiple wickets and still lose the match?

Yes. Cricket is a team sport. Even if a bowler delivers a top-class spell, the match can still be lost due to weak batting, poor fielding, or lack of support from other bowlers.

Why don’t these performances get the recognition they deserve?

Because match results often overshadow individual brilliance. When the team loses, fans and media tend to focus on the defeat rather than standout performances in a losing cause.

How common is it for top-performing bowlers to end up on the losing side?

Very common, especially in T20s and ODIs. A bowler may dominate for 4–10 overs, but one bad over from another bowler or a batting collapse can undo the good work.