⚔️HEAD-TO-HEAD
Kwena Maphaka 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.
Kwena Maphaka (Rajasthan Royals) has 19 T20I runs at avg 9.5 in 20 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
Kwena Maphaka 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 | Kwena Maphaka | Rohit Sharma |
|---|---|---|
| Matches | 4 | 19 |
| Avg fantasy points | 25 | 79 |
| Best fantasy score | 44 | 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 |
| Wickets | 2 | 0 |
| Economy rate | 7.43 | 0.00 |
| Best spell (wkts) | 1 | 0 |
| Catches | 1 | 9 |
| Total dismissals | 1 | 9 |
| Statistic | Kwena Maphaka | Rohit Sharma |
|---|---|---|
| Matches | 20 | 159 |
| Runs | 19 | 4231 |
| Batting average | 9.50 | 32.05 |
| Strike rate | 79.2 | 140.9 |
| Centuries (100+) | 0 | 5 |
| Half-centuries (50+) | 0 | 32 |
| Wickets | 19 | 1 |
| Bowling average | 31.74 | 113.00 |
| Economy rate | 9.05 | 9.97 |
📋 Format by format
T20I. Kwena Maphaka has played 20 T20Is and Rohit Sharma 159. Kwena Maphaka has 19 runs at 9.5 (strike rate 79.2), against 4,231 at 32.0 (140.9) for Rohit Sharma, so Rohit Sharma has scored more. Hundreds: Kwena Maphaka 0, Rohit Sharma 5. Fifties: 0 and 32. With the ball, Kwena Maphaka has 19 wickets at an economy of 9.05 and Rohit Sharma 1 at 9.97; Kwena Maphaka has more wickets.
ODI. Kwena Maphaka has played 3 ODIs and Rohit Sharma 291. Kwena Maphaka has 1 runs at 0.3 (strike rate 12.5), against 12,120 at 49.3 for Rohit Sharma, so Rohit Sharma has scored more. Hundreds: Kwena Maphaka 0, Rohit Sharma 35. Fifties: 0 and 63. With the ball, Kwena Maphaka has 5 wickets at an economy of 8.93 and Rohit Sharma 9 at 5.24; Rohit Sharma has more wickets.
Test. Kwena Maphaka has played 2 Tests and Rohit Sharma 67. Kwena Maphaka has 17 runs at 8.5 (strike rate 60.7), against 4,301 at 40.6 (57.1) for Rohit Sharma, so Rohit Sharma has scored more. Hundreds: Kwena Maphaka 0, Rohit Sharma 12. Fifties: 0 and 18.
International numbers up to 1 September 2026.
Kwena Maphaka vs Rohit Sharma — T20I is a highly-debated cricket matchup. Below are their T20I career highlights.
T20I career: Kwena Maphaka has scored 19 T20I runs in 20 matches at an average of 9.50. He has also taken 19 T20I wickets at an average of 31.74 with an economy of 9.05.
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 — Kwena Maphaka or Rohit Sharma?
Kwena Maphaka vs Rohit Sharma — who is a better fantasy captain?
Who has a better strike rate — Kwena Maphaka or Rohit Sharma?
What is the price difference between Kwena Maphaka and Rohit Sharma?
How many MOTM awards have Kwena Maphaka and Rohit Sharma won?
Should I pick Kwena Maphaka or Rohit Sharma in my fantasy XI?
Who has more T20I runs, Kwena Maphaka or Rohit Sharma?
Who has more ODI runs, Kwena Maphaka or Rohit Sharma?
Who has taken more ODI wickets, Kwena Maphaka or Rohit Sharma?
Who has more Test runs, Kwena Maphaka or Rohit Sharma?
SETTLE IT IN A GAME
Numbers only get you so far. Pick a side — Kwena Maphaka or Rohit Sharma — and see who actually delivers.
Found an issue or have a suggestion? Contact us — we’d love to hear from you.