Dream11 Points Rules: Match Format and Calculation Checks
Dream11 scoring depends on the sport, match format and applicable rules. The official cricket reference checked on 30 October 2026 provides format-specific values: its T20 section awards one point per dot ball, while OD awards one point per three dot balls. Use the selected examples below with the full rules for your match; this is not an exhaustive points table.
By ComeAPK Editorial. Text review (UTC): . Source observation dates and limits appear below.
Identify the rule set for your match
The numerical scoring references here belong to Sporta’s Dream11 rules. This site uses dream11app.live for Dream11 App downloads; that distribution choice does not establish the same dot-ball rates or multipliers for Dream11App or a partner contest. Match the provider, format and applicable rule before using a number below.
Start with the sport, match and format shown by the provider, then open the scoring reference attached to that task. Dream11’s official cricket how-to-play page was readable on 30 October 2026. Its format sections provide the selected examples below; they should not be combined into one universal scoring table.
These are dated reference values, not a live score feed, a complete rulebook or confirmation that a particular account or contest is available. Read the complete format section for thresholds, exclusions, substitutions and later changes before calculating.
| Official format section | Selected rule checked on 30 October 2026 | Limit of this example |
|---|---|---|
| T20 | Dot ball: +1 point per dot ball. | Use the applicable T20 rules and event eligibility; do not transfer this rate to OD. |
| OD | Dot balls: +1 point for every 3 dot balls. | The grouping differs from T20; review the full OD rules for the match. |
| T20 | Catch: +8 points. | Fielding bonuses and other player events need their own rule checks. |
| T20 | Captain: 2x; vice-captain: 1.5x. | Confirm the assigned role and applicable format; do not silently apply a multiplier twice. |
T20 bonuses, substitutes and excluded events: avoid double counting
The selected exceptions below come from the T20 section of Dream11’s official cricket format reference, retained on 7 November 2026. They supplement the earlier dated examples above. Confirm the current format and mode before using them; this is a partial reference rather than a complete scoring schedule.
Calculate eligible base events first, then apply the applicable milestone or capped bonus and the confirmed role multiplier. A player’s presence in an announced substitute list does not by itself establish appearance points or eligibility for every contribution. Keep the participation evidence alongside the event calculation.
| T20 condition in the dated reference | Treatment | Calculation check |
|---|---|---|
| A batter reaches a century | The 100-run milestone bonus is +16; the 25/50/75 bonuses are not added to it. | At exactly 100, the milestone contribution is 16, not 4 + 8 + 12 + 16. Runs and other eligible events remain separate. |
| A player takes more than three eligible catches | The three-catch bonus remains +4; it does not repeat for each group of three. | Hypothetical six catches: 6 × 8 + 4 = 52 for the catch contribution before role multipliers; not 56 or a complete player total. |
| A listed Concussion, X-Factor, Impact or full-time playing replacement is only announced | The reference awards 0 for the substitute announcement alone. An eligible replacement who actually plays receives +4 plus eligible contributions. | Establish actual participation and the permitted replacement category; ordinary substitute contributions are excluded by the stated rules. |
| An action occurs during a Super Over or Super Five | The reference excludes points for those actions. | Separate those events from eligible match events before adding a role multiplier. |
T20 strike rate and economy: check the minimum before the band
The T20 section of the Dream11 cricket rules, checked on 11 November 2026, requires at least 10 balls faced for strike-rate points and excludes bowlers from that batting adjustment. Economy-rate points require at least two overs bowled. A rate can fall inside a published band while the minimum participation condition is still unmet.
The examples below use invented counts to explain those conditions; they are not match results. Compute the rate from the eligible record, check the player category and minimum, then apply the published band once. Keep the provider’s full rule for decimal boundaries and rounding rather than inventing a rounding policy.
| Hypothetical T20 input | Eligibility and published band | Rate adjustment only |
|---|---|---|
| Batter: 18 runs from 9 balls | Strike rate 200, but fewer than 10 balls faced. | No strike-rate adjustment; this does not remove eligible run or boundary points. |
| Batter: 40 runs from 25 balls | Strike rate 160; at least 10 balls and the 150.01–170 band. | +4; other eligible batting, fielding and appearance events are separate. |
| Batter: 6 runs from 10 balls | Strike rate 60; at least 10 balls and the 60–70 band. | −2; the actual runs still have their own contribution. |
| Bowler: 12 runs conceded in 1 completed over | Economy 12, but fewer than two overs bowled. | No economy-rate adjustment; inspect other eligible bowling events separately. |
| Bowler: 12 runs conceded in 2 completed overs | Economy 6; at least two overs and the 6–7 band. | +2; this is not the player’s complete bowling score. |
Worked T20 example: 82 base points, 164 as captain
Illustrative scenario, not a real fixture or player: a batter starts the match, actually plays, scores 40 from 25 balls with four fours and one six, and takes one eligible catch. Assume no other contributions or exclusions. The T20 batting, fielding and role reference, checked on 11 November 2026, supports each value below; the 40 runs already include runs from those boundaries, while boundary and six bonuses are separate additions.
The unmultiplied total is 40 + 16 + 6 + 4 + 4 + 8 + 4 = 82. Under the cited T20 role rules it becomes 164 for captain or 123 for vice-captain, applied once to the eligible total. One catch does not earn the three-catch bonus, and 40 runs does not qualify for a 50-run milestone. A different format, second-innings mode, substitute status or event record requires a fresh calculation.
Check the role against the saved Dream11 team before comparing a displayed total. If the app shows a different number, use the 82-point reconciliation example to separate a role-scale difference from an unexplained event difference.
| Eligible event or adjustment | Calculation | Unmultiplied contribution |
|---|---|---|
| Runs | 40 × 1 | 40 |
| Boundary bonus for four fours | 4 × 4 | 16 |
| Six bonus for one six | 1 × 6 | 6 |
| 25-run milestone | One qualifying milestone in this example | 4 |
| Strike rate: 160 from 25 balls | Applicable batter band: 150.01–170 | 4 |
| One eligible catch | 1 × 8; no three-catch bonus | 8 |
| Starting-lineup participation | Announced starter who actually plays | 4 |
| Unmultiplied player total | Sum of the seven contributions above | 82 |
Build a score record you can check
Use one row per eligible event or adjustment. Write the base contribution, the bonus/exclusion and the role multiplier separately; then total the same player and match at the same observation time. If a rule, count or participation status is unknown, leave that line unresolved instead of assigning zero by assumption.
A final sports score answers who won the match, not who won a fantasy contest. The checked IPL final result records RCB vs GT on 31 May 2026 with official innings totals. Those team totals do not supply each player’s eligible events, fantasy score or a particular entry’s final rank; keep those records separate when checking a displayed total.
| Record | Why it matters |
|---|---|
| Match and format | Makes sure the correct scoring rule set is being applied. |
| Player event and official scorecard reference | Separates the real event from the fantasy points assigned to it. |
| Base rule and threshold | Shows whether a run, wicket, fielding action, rate or milestone qualifies. |
| Adjustment or exclusion | Captures conditions that prevent double counting or change eligibility. |
| Role multiplier, if any | Use only the current contest’s stated captain or other role rule. |
| Calculation time and final status | A live score can change while an event or scorecard is being corrected. |
Calculate with verified inputs, not remembered values
Once the applicable rules are identified, list eligible events, their counts and the referenced value for each. Keep threshold bonuses, exclusions and role adjustments as separate lines so that another reader can reproduce the calculation.
Arithmetic illustration using only the selected T20 catch rule above: two eligible catches have a base catch contribution of 2 × 8 = 16 points. If the applicable T20 captain rule covers that contribution and the player is captain, its multiplied contribution is 16 × 2 = 32. These are hypothetical counts, not a real player’s score or a complete fielding total; all other events, bonuses and exclusions need separate rule checks.
When your calculation differs from the app
First compare the same match, format, player and update time. Then check exclusions, thresholds, role selection and whether the displayed points are still provisional. Keep the rule and scorecard references alongside your calculation.
If the difference remains, send that record through verified support. Installing an old app does not establish that server-side scoring should use old rules.
For a remaining difference, use the scoring-reconciliation record. If the player or captain assignment differs from what you intended, check the saved-team record first. If your actual question is ‘yesterday winner points’, start with the date, match and final-standings checks; a correctly calculated player score does not identify the winning entry.