T20 cricket is fast and exciting. Players usually score runs quickly, hit big shots, and entertain the crowd. But sometimes, things don’t go as planned. Even the best Indian cricketers have had matches where they found it hard to score. In this article, we’ll look at those unusual innings when Indian players struggled in T20s and ended with very slow scores.
What Does a Slow T20 Innings Mean?
In T20 matches, every ball is important. Teams expect their players to score fast. But when a batter plays many balls and makes only a few runs, it becomes a slow innings.
A slow innings usually includes:
- A low strike rate (below 80)
- Very few boundaries
- Lots of dot balls
- Added pressure on the team
These types of innings are not common but do happen, especially when the pitch is tough or the bowler is doing well.
Top 5 Indian Players with the Slowest T20 Innings
Below is the list of Indian cricketers who played some of the slowest innings in T20 cricket. These performances surprised many fans, as these players are usually known for their aggressive style.
| Player | Score (Balls) | Strike Rate | Opponent | Year |
| Virat Kohli | 1 (5) | 20.00 | Ireland | 2024 |
| MS Dhoni | 5 (12) | 41.66 | South Africa | 2009 |
| Yashpal Singh | 6 (20) | 30.00 | Punjab (IPL) | 2009 |
| R. Ashwin | 10 (20) | 50.00 | New Zealand | 2016 |
| Yuvraj Singh | 11 (21) | 52.38 | Sri Lanka | 2014 |
Analysing Each Slowest Innings in T20
Virat Kohli: 1 from 5 Balls (vs Ireland, 2024)
Kohli batted first in the T20 World Cup 2024 but never got into his rhythm. After amassing 1 run in 5 balls, he attempted to hit a big shot in the 3rd over but got caught. This was a rare occurrence for one of India’s finest players.
MS Dhoni: 5 from 12 Balls (vs South Africa, 2009)
Dhoni got to the crease in a deep hole for India. He took time to settle down, but without hitting the rhythm. After making only 5 runs in 12 balls, he was run out. His slow scoring run made chasing even more difficult for the team.
Yashpal Singh: 6 from 20 Balls (vs Punjab, IPL 2009)
Yashpal Singh had a slow innings in the IPL representing Kolkata. After taking 20 balls, he scored just 6 runs. Though Kolkata won that match, his strike rate of 30 made him take one of the slowest recorded innings in T20 history.
Ravichandran Ashwin: 10 from 20 Balls (vs New Zealand, 2016)
Ashwin is known for his bowling only, but in this match, he was advised to bat under difficult circumstances. He took 20 balls to score just 10 runs. Wasted balls added pressure when India arguably needed quick runs.
Yuvraj Singh: 11 off 21 Balls (vs Sri Lanka, 2014 Final)
In the T20 World Cup Final, fans expected fireworks from Yuvraj. But he could not find his form. He struggled to hit boundaries and ended up with just 11 runs from 21 balls. This innings was disappointing, especially in such an important game.
Why Do These Slow Innings Happen?
T20 cricket is fast, but slow innings still happen due to:
- Good bowling and field placements
- Poor pitch conditions
- Pressure of the game
- Trying to avoid getting out early
- Lack of timing or form
Even top players can go through tough patches. These innings are proof that cricket is not always predictable.
Follow Every Ball with Premium bet 77 Login
If you enjoy keeping track of live scores, strike rates, and player stats, the PB77 is a great website. The app gives real-time tracking and lets you see how each player is doing (even if they are not doing well). Whether you are at home or on the go, the app keeps you connected to the game.
