⚔️HEAD-TO-HEAD
Aiden Markram vs Kane Williamson — International Fantasy Cricket Stats Comparison
Aiden Markram (Lucknow Super Giants) has 1,938 T20I runs at avg 31.8 in 75 matches. Kane Williamson (New Zealand) has 2,537 T20I runs at avg 33.0 in 91 matches. Head-to-head batting, bowling & fielding across T20I, ODI & Test.
Full season · batting · bowling · fielding · MOTM · form
Aiden Markram vs Kane Williamson — 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 | Aiden Markram | Kane Williamson |
|---|---|---|
| Matches | 12 | 1 |
| Avg fantasy points | 40 | 69 |
| Best fantasy score | 89 | 69 |
| Runs | 231 | 18 |
| Strike rate | 138.3 | 47.4 |
| Fours | 20 | 2 |
| Sixes | 11 | 0 |
| Highest score | 45 | 18 |
| Economy rate | 13.67 | 0.00 |
| Catches | 8 | 4 |
| Total dismissals | 9 | 4 |
| Statistic | Aiden Markram | Kane Williamson |
|---|---|---|
| Matches | 75 | 91 |
| Runs | 1938 | 2537 |
| Batting average | 31.77 | 32.95 |
| Strike rate | 148.7 | 124.3 |
| Half-centuries (50+) | 14 | 18 |
| Wickets | 16 | 6 |
| Bowling average | 36.81 | 27.33 |
| Economy rate | 8.79 | 8.34 |
Aiden Markram vs Kane Williamson — T20I is a highly-debated cricket matchup. Below are their T20I career highlights.
T20I career: Aiden Markram has scored 1,938 T20I runs in 75 matches at an average of 31.77, with 14 half-centuries. He has also taken 16 T20I wickets at an average of 36.81 with an economy of 8.79.
T20I career: Kane Williamson has scored 2,537 T20I runs in 91 matches at an average of 32.95, with 18 half-centuries. He has also taken 6 T20I wickets at an average of 27.33 with an economy of 8.34.
Fantasy Impact: From a pure fantasy perspective, Kane Williamson is the stronger pick with an average of 69 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.