⚔️HEAD-TO-HEAD
Johan Botha vs Rohit Sharma — International Fantasy Cricket Stats Comparison
Rohit Sharma has the edge on the headline numbers: Rohit Sharma leads on T20I batting (4,231 runs, avg 32.0). Full T20I, ODI, Test and IPL stats are below.
Johan Botha () has 201 T20I runs at avg 18.3 in 40 matches. Rohit Sharma (India) has 4,231 T20I runs at avg 32.0 in 159 matches. Head-to-head batting, bowling & fielding across T20I, ODI & Test.
Full season · batting · bowling · fielding · MOTM · form
Johan Botha vs Rohit Sharma — Stat Comparison Table
Head-to-head numbers at a glance. Higher value is highlighted in green (lower is better for economy and bowling/batting averages).
| Statistic | Johan Botha | Rohit Sharma |
|---|---|---|
| Matches | 0 | 19 |
| Avg fantasy points | 0 | 79 |
| Best fantasy score | 0 | 214 |
| Runs | 0 | 885 |
| Strike rate | 0.0 | 126.2 |
| Fours | 0 | 85 |
| Sixes | 0 | 49 |
| Half-centuries (50+) | 0 | 5 |
| Centuries (100+) | 0 | 2 |
| Highest score | 0 | 138 |
| Catches | 0 | 9 |
| Total dismissals | 0 | 9 |
| Statistic | Johan Botha | Rohit Sharma |
|---|---|---|
| Matches | 40 | 159 |
| Runs | 201 | 4231 |
| Batting average | 18.27 | 32.05 |
| Strike rate | 121.8 | 140.9 |
| Centuries (100+) | 0 | 5 |
| Half-centuries (50+) | 0 | 32 |
| Wickets | 37 | 1 |
| Bowling average | 22.24 | 113.00 |
| Economy rate | 6.38 | 9.97 |
📋 Format by format
T20I. Johan Botha has played 40 T20Is and Rohit Sharma 159. Johan Botha has 201 runs at 18.3 (strike rate 121.8), against 4,231 at 32.0 (140.9) for Rohit Sharma, so Rohit Sharma has scored more. Hundreds: Johan Botha 0, Rohit Sharma 5. Fifties: 0 and 32. With the ball, Johan Botha has 37 wickets at an economy of 6.38 and Rohit Sharma 1 at 9.97; Johan Botha has more wickets.
ODI. Johan Botha has played 78 ODIs and Rohit Sharma 291. Johan Botha has 609 runs at 19.0 (strike rate 85.8), against 12,120 at 49.3 for Rohit Sharma, so Rohit Sharma has scored more. Hundreds: Johan Botha 0, Rohit Sharma 35. Fifties: 0 and 63. With the ball, Johan Botha has 72 wickets at an economy of 4.58 and Rohit Sharma 9 at 5.24; Johan Botha has more wickets.
Test. Johan Botha has played 5 Tests and Rohit Sharma 67. Johan Botha has 83 runs at 20.8 (strike rate 34.9), against 4,301 at 40.6 (57.1) for Rohit Sharma, so Rohit Sharma has scored more. Hundreds: Johan Botha 0, Rohit Sharma 12. Fifties: 0 and 18. With the ball, Johan Botha has 17 wickets at an economy of 3.38 and Rohit Sharma 2 at 3.51; Johan Botha has more wickets.
International numbers up to 19 July 2026.
Johan Botha vs Rohit Sharma — T20I is a highly-debated cricket matchup. Below are their T20I career highlights.
T20I career: Johan Botha has scored 201 T20I runs in 40 matches at an average of 18.27. He has also taken 37 T20I wickets at an average of 22.24 with an economy of 6.38.
T20I career: Rohit Sharma has scored 4,231 T20I runs in 159 matches at an average of 32.05, with 5 centuries. He has also taken 1 T20I wickets at an average of 113.00 with an economy of 9.97.
Fantasy Impact: From a pure fantasy perspective, Rohit Sharma is the stronger pick with an average of 79 pts per game in recent fantasy cricket. Always check the playing XI and toss before locking in your captain.
Stats are sourced from international career records. Compare more players using our Player Comparison Tool.
Who has better fantasy stats — Johan Botha or Rohit Sharma?
Johan Botha vs Rohit Sharma — who is a better fantasy captain?
Who has a better strike rate — Johan Botha or Rohit Sharma?
What is the price difference between Johan Botha and Rohit Sharma?
How many MOTM awards have Johan Botha and Rohit Sharma won?
Should I pick Johan Botha or Rohit Sharma in my fantasy XI?
Who has more T20I runs, Johan Botha or Rohit Sharma?
Who has the better T20I strike rate?
Who has more ODI runs, Johan Botha or Rohit Sharma?
Who has taken more ODI wickets, Johan Botha or Rohit Sharma?
Who has more Test runs, Johan Botha or Rohit Sharma?
SETTLE IT IN A GAME
Numbers only get you so far. Pick a side — Johan Botha or Rohit Sharma — and see who actually delivers.
Found an issue or have a suggestion? Contact us — we’d love to hear from you.