The Dream11 points system: a scoring reference that explains what each rule rewards.

Dream11 publishes its scoring table inside the app and on the operator's help pages. This scoring reference is not a substitute for the operator's own scoring table — it is an editorial reference that explains why each rule exists, what behaviour it rewards, and how it interacts with the captain multiplier. Every figure here is reproduced from the operator's published scoring rules at the time of last verification (see the stamp at the top). Re-verify against the operator's current scoring FAQs before publishing any team.

Batting points

The batting points table rewards runs scored with a small per-run rate, then layers in bonuses for milestones and strike rate. A typical batting table awards one point per run, a four-point bonus for a boundary, a six-point bonus for a six and milestone bonuses at 30, 50, 100. A dismissal for a duck costs a small number of points (often two) for batsmen other than the top order — a useful detail when deciding which role to captain.

Bowling points

Bowling points reward wickets generously: typically 25 points per wicket, with bonuses for LBW / bowled, for a hat-trick and for a four-wicket or five-wicket haul. Runs conceded carry a small negative per run — the same idea as the batting rate, but in the opposite direction.

Fielding points

Catches, stumpings and run-outs add additional points per dismissal. Fielding points are small in absolute terms but disproportionate in low-scoring contests where a single brilliant catch changes the leaderboard. They are also the points a captain's research often overlooks — a fielder in good ground-position form is more valuable than the table implies.

Captain and vice-captain multipliers

The captain earns 2x the player's actual score; the vice-captain earns 1.5x. The structural consequence: a captain who scores 80 points actually contributes 160. That is the single highest-leverage decision on the team. The trade-off is ownership: the most obvious captain is also the highest-owned captain, which compresses your lineup's differentiation in large-field contests.

Strike-rate bonuses

Strike-rate bonuses (and penalties) appear above certain run thresholds. The point is to reward aggressive scoring in the death overs and to penalise low-rate innings in the powerplay. The exact cutoffs vary by format (T20 vs ODI) — always cross-check the format-specific cutoff before locking your captain.

Economy-rate bonuses

Economy-rate bonuses work the same way: above a certain overs threshold, bowlers earn bonuses for sub-6 economy and penalties for economy above 9–10. This is the rule that makes death-over specialist bowlers disproportionately valuable relative to their salary cost in T20.

Worked T20 example

Hypothetical: an opener scores 56 off 38 balls with five fours and two sixes. Batting points = 56 (runs) + 5×4 (boundaries) + 2×6 (sixes) + 8 (50 milestone) = 84 raw. As captain, that becomes 168 effective. The same player in the same match, but captained by someone who scored 35 off 30 with no boundaries, contributes 35 × 2 = 70 effective. The captain choice alone moved the team's expected score by nearly 100 effective points.

FAQ

How strike-rate bonuses differ by format

Strike-rate bonuses are the rule that most rewards aggressive batting. In T20 the cutoff is typically a 130+ strike rate above a minimum run threshold; in ODI the cutoff is looser because run accumulation is more important. Always check the format-specific cutoff before locking a captain — a player who is the obvious captain in T20 may not be the obvious captain in ODI, even at the same match.

How economy bonuses differ by format

Economy bonuses work the opposite way. In T20 the cutoff is typically sub-6 economy above a minimum overs threshold; in ODI the cutoff is sub-5 economy. A bowler who is dominant in T20 may be less effective in ODI not because their skill has changed but because the cutoff has. Format-specific awareness is part of the scoring literacy that separates repeatable habits from hot takes.

Why the captain multiplier makes captaincy a structural decision

The captain multiplier (2x for captain, 1.5x for vice-captain) is structural because it changes the relative value of every player in your team. A player who scores 60 points contributes 120 as captain and 90 as vice-captain. The same player off the captain role contributes 60. The captain pick is not "the player you think will score the most" — it is the player whose expected score, after the multiplier, most exceeds the second-best option.

What to do when the rules change mid-season

The operator updates scoring rules occasionally — typically at the start of a new tournament season, rarely mid-season. When the rules change, the operator publishes the new table inside the app and on its help pages; the change is usually accompanied by a one-week notice window. Re-read the table before locking your first team under the new rules; the captaincy candidate set you built under the old rules may no longer be optimal.

Editorial addendum: a closing reflection

This guide is part of the Dream11 Today editorial library, an independent publication not affiliated with Dream11, Dream Sports or any real-money gaming operator. The desk's purpose is to publish research-first, evidence-led guides that help Indian adults decide whether real-money fantasy fits their situation and, if so, how to navigate the platform's product, legal and account flows with as few avoidable mistakes as possible.

Every guide on this site follows the same editorial standards: claims are sourced where they are not common knowledge; volatile information (bonus terms, scoring rules, legal status) carries a "verified on" stamp and is reviewed within 30 days; commercial links carry rel="sponsored nofollow" and an adjacent disclosure; and the editorial position is unaffected by commercial relationships. The standards apply equally to the most casual beginner guide and to the most technical APK safety walkthrough.

If you have read this far, you are already doing the editorial work the desk exists to encourage. The next step is to apply what you have read: set a deposit cap on day one; bookmark the operator's official channels; bookmark the responsible-play page; keep a notebook of every contest; re-read the standards after every month of play. Habits compound; predictions do not.

For corrections, sourcing questions or disclosure queries, use the contact page. We aim to respond within seven working days. For product support, use the operator's in-app flow (Help → Contact support) — the desk does not have access to the operator's account systems and cannot resolve product issues.

Finally, a reminder: real-money fantasy is entertainment, not income. The platform's rake structure means the average player loses money over time; no honest publication can promise a profit. Treat every contest entry as spent money; set a hard monthly cap; step away the moment the experience stops being fun. If the platform is no longer working for you, the responsible-play guide explains how to opt out cleanly.

A pre-match scoring checklist

1. Confirm the format-specific cutoffs

   Strike-rate and economy thresholds differ between T20, ODI and Test formats.

2. Re-read the captain multiplier rules

   Standard 2x for captain, 1.5x for vice-captain; some special contests vary.

3. Check the wicket values

   Wickets typically 25 points; LBW / bowled may carry an additional bonus.

4. Confirm milestone bonuses

   Batting milestones (30, 50, 100) and bowling milestones (4-wicket, 5-wicket haul) — verify the current thresholds.

5. Re-read the fielding table

   Catches, stumpings and run-outs — small in absolute terms but disproportionate in low-scoring contests.

6. Note any recent rule changes

   The operator updates scoring rules occasionally; check the in-app release notes before locking your team.