How scoring works
Your eleven earns from the real match's recorded events. Values follow the standard fantasy pattern; exact tables display in-app per format (T10, T20 and ODI weight things differently). The shape below is what you are optimising for when you build.
Batting
- Points per run, with bonuses at milestone scores (half-century tier, century tier).
- Boundary bonuses: fours pay extra, sixes pay more.
- Strike-rate adjustments in short formats: slow fifties earn less than fast forties.
- A duck costs points for batters; one more reason top-order form matters.
Bowling
- Wickets are the big line, with bonuses for three-plus and five-plus hauls.
- Maiden overs pay in short formats, where they are rare and match-turning.
- Economy-rate adjustments: cheap overs add, expensive ones subtract.
- Bowled and LBW dismissals often carry a small extra over caught.
Fielding and extras
- Catches pay per take, with a bonus tier for multiple catches.
- Stumpings and direct-hit run-outs pay the keeper and the arm.
- Playing-eleven points: being on the field at all earns the base tick.
What actually separates leaderboards
- Captain choice first, nothing else is close. The 2x on the right all-rounder routinely beats an extra star in the eleven.
- Death-over bowlers: three wickets in two overs happen there, not in the powerplay.
- Keeper picks: stumpings plus top-order batting makes keepers credit-dense in T10.
- Fielding is luck you can tilt: slip and boundary-rider regulars catch more than fine-leg hiders.
Scoring questions
Do points update live during the match?
Yes, the leaderboard moves ball by ball with the official feed, and settles once the result is official. Rain-rule outcomes follow the real fixture's ruling.
Are T10 and T20 scored the same?
The event types match, the weights differ; the in-app table per match is the binding version. Shorter formats lean harder on strike rate and economy.