⚔️HEAD-TO-HEAD
Lockie Ferguson 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.
Lockie Ferguson (Punjab Kings) has 38 T20I runs at avg 4.2 in 54 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
Lockie Ferguson 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 | Lockie Ferguson | Rohit Sharma |
|---|---|---|
| Matches | 11 | 19 |
| Avg fantasy points | 35 | 79 |
| Best fantasy score | 154 | 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 | 10 | 0 |
| Economy rate | 10.29 | 0.00 |
| Best spell (wkts) | 4 | 0 |
| Catches | 3 | 9 |
| Total dismissals | 4 | 9 |
| Statistic | Lockie Ferguson | Rohit Sharma |
|---|---|---|
| Matches | 54 | 159 |
| Runs | 38 | 4231 |
| Batting average | 4.22 | 32.05 |
| Strike rate | 90.5 | 140.9 |
| Centuries (100+) | 0 | 5 |
| Half-centuries (50+) | 0 | 32 |
| Wickets | 76 | 1 |
| Bowling average | 17.82 | 113.00 |
| Economy rate | — | 9.97 |
| Five-wicket hauls | 1 | 0 |
📋 Format by format
T20I. Lockie Ferguson has played 54 T20Is and Rohit Sharma 159. Lockie Ferguson has 38 runs at 4.2 (strike rate 90.5), against 4,231 at 32.0 (140.9) for Rohit Sharma, so Rohit Sharma has scored more. Hundreds: Lockie Ferguson 0, Rohit Sharma 5. Fifties: 0 and 32. With the ball, Lockie Ferguson has 76 wickets and Rohit Sharma 1 at 9.97; Lockie Ferguson has more wickets.
ODI. Lockie Ferguson has played 65 ODIs and Rohit Sharma 291. Lockie Ferguson has 122 runs at 7.2 (strike rate 51.7), against 12,120 at 49.3 for Rohit Sharma, so Rohit Sharma has scored more. Hundreds: Lockie Ferguson 0, Rohit Sharma 35. Fifties: 0 and 63. With the ball, Lockie Ferguson has 99 wickets and Rohit Sharma 9 at 5.24; Lockie Ferguson has more wickets.
Test. Lockie Ferguson has played 1 Test and Rohit Sharma 67. Lockie Ferguson has 1 runs (strike rate 11.1), against 4,301 at 40.6 (57.1) for Rohit Sharma, so Rohit Sharma has scored more. Hundreds: Lockie Ferguson 0, Rohit Sharma 12. Fifties: 0 and 18.
International numbers up to 19 July 2026.
Lockie Ferguson vs Rohit Sharma — T20I is a highly-debated cricket matchup. Below are their T20I career highlights.
T20I career: Lockie Ferguson has scored 38 T20I runs in 54 matches at an average of 4.22. He has also taken 76 T20I wickets at an average of 17.82.
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 — Lockie Ferguson or Rohit Sharma?
Lockie Ferguson vs Rohit Sharma — who is a better fantasy captain?
Who has a better strike rate — Lockie Ferguson or Rohit Sharma?
What is the price difference between Lockie Ferguson and Rohit Sharma?
How many MOTM awards have Lockie Ferguson and Rohit Sharma won?
Should I pick Lockie Ferguson or Rohit Sharma in my fantasy XI?
Who has more T20I runs, Lockie Ferguson or Rohit Sharma?
Who has more ODI runs, Lockie Ferguson or Rohit Sharma?
Who has taken more ODI wickets, Lockie Ferguson or Rohit Sharma?
Who has more Test runs, Lockie Ferguson or Rohit Sharma?
SETTLE IT IN A GAME
Numbers only get you so far. Pick a side — Lockie Ferguson or Rohit Sharma — and see who actually delivers.
Found an issue or have a suggestion? Contact us — we’d love to hear from you.