⚔️HEAD-TO-HEAD
Ben Stokes vs Yuzvendra Chahal — International Fantasy Cricket Stats Comparison
Ben Stokes (England) has 576 T20I runs at avg 23.0 in 41 matches. Yuzvendra Chahal (Punjab Kings) has 6 T20I runs at avg 3.0 in 80 matches. Head-to-head batting, bowling & fielding across T20I, ODI & Test.
Full season · batting · bowling · fielding · MOTM · form
Ben Stokes vs Yuzvendra Chahal — 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 | Ben Stokes | Yuzvendra Chahal |
|---|---|---|
| Matches | 2 | 13 |
| Avg fantasy points | 135 | 29 |
| Best fantasy score | 231 | 94 |
| Runs | 57 | 0 |
| Strike rate | 72.2 | 0.0 |
| Fours | 5 | 0 |
| Sixes | 2 | 0 |
| Highest score | 45 | 0 |
| Wickets | 7 | 12 |
| Economy rate | 2.89 | 9.39 |
| Best spell (wkts) | 6 | 3 |
| Catches | 0 | 2 |
| Total dismissals | 0 | 2 |
| Statistic | Ben Stokes | Yuzvendra Chahal |
|---|---|---|
| Matches | 41 | 80 |
| Runs | 576 | 6 |
| Batting average | 23.04 | 3.00 |
| Strike rate | 129.4 | 46.1 |
| Half-centuries (50+) | 1 | 0 |
| Wickets | 23 | 96 |
| Bowling average | 35.17 | 25.09 |
| Economy rate | 8.52 | 8.19 |
| Five-wicket hauls | 0 | 1 |
Ben Stokes vs Yuzvendra Chahal — T20I is a highly-debated cricket matchup. Below are their T20I career highlights.
T20I career: Ben Stokes has scored 576 T20I runs in 41 matches at an average of 23.04, with 1 half-century. He has also taken 23 T20I wickets at an average of 35.17 with an economy of 8.52.
T20I career: Yuzvendra Chahal has scored 6 T20I runs in 80 matches at an average of 3.00. He has also taken 96 T20I wickets at an average of 25.09 with an economy of 8.19.
Fantasy Impact: From a pure fantasy perspective, Ben Stokes is the stronger pick with an average of 135 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.
Found an issue or have a suggestion? Contact us — we’d love to hear from you.