Skip to content
Dream11 AppDream11App · India
Fantasy cricket points

Dream11 App points: batting, bowling, fielding, captain bonus

Fantasy cricket points are a provider’s conversion of match events into a team score. This Dream11 App guide explains how to build a usable event ledger, interpret cricket rate notation and diagnose a mismatch. Use the provider-specific reference for actual point values; runs alone are not the final fantasy total.

Fantasy cricket points

Separate a cricket event from its fantasy award

A scorecard records runs, deliveries, dismissals and fielding contributions. The provider decides which of those earn points and which need an extra condition. Record the rule version and format beside each event. Runs from a boundary and a separately awarded boundary bonus can both count, but adding the boundary runs twice creates an error.

Fantasy cricket points

Build a ledger you can recalculate

Give each selected player separate columns for event count, rule value, eligible bonus, deduction, base total and captain role. Keep wickets and run-outs separate. Add balls faced and legal balls bowled so rate eligibility can be checked before applying a rate award. Keep a zero value distinct from an event that has not yet been confirmed.

Fantasy cricket points

Convert overs before calculating a rate

In six-ball cricket, 3.2 overs is 20 legal balls. Thirty runs conceded in that spell gives 30 ÷ (20/6) = 9 runs per over, not 30 ÷ 3.2. Batting strike rate uses runs ÷ balls faced × 100. Check the provider’s minimum workload and published threshold endpoints before converting either rate into fantasy points.

Fantasy cricket points

Identify the cause of a different total

First compare the player list and actual participation, then event attribution, eligibility conditions, bonuses and captain roles. A score still under review can change. Use the match’s final breakdown and describe the disputed event rather than assuming a difference proves an error in the app. The detailed reference explains substitutes, corrections and special formats.

Fantasy cricket points

Check rate eligibility before awarding rate points

For a concrete reference, Sporta Dream11’s public T20 tab checked on 7 November 2026 requires at least 10 balls faced for its strike-rate award and at least 2 overs bowled for its economy-rate award; the strike-rate category excludes bowlers. Use these conditions only when they match the rules attached to your contest. In a hypothetical batting example, 18 runs from 9 balls gives a strike rate of 200, but the 10-ball condition is not met. Twenty from 10 also gives 200 and meets that workload condition; the applicable band and player category still need checking. In a six-ball bowling example, 1.5 overs means 11 legal balls, so the 2-over condition is not yet met. At 2.0 overs it is met, but the credited runs conceded and published band determine the rate award. The detailed T20 scoring reference supplies the values and exceptions. Keep ordinary run or wicket points in separate ledger rows: failing a rate condition does not itself erase other eligible events.

Your total still differs

Record the selected format, player category, balls faced or legal balls bowled, runs used in the rate calculation, eligibility decision and band. Compare that row with the provider’s event breakdown before applying the captain multiplier. Leave an unconfirmed event unresolved instead of assigning it a made-up value.

common questions

What to check before you play

Are cricket runs the same as fantasy points?+

No. Runs are one input; bonuses, wickets, fielding, deductions and multipliers can change the total.

Do IPL and international cricket always use different scoring?+

Not inherently. The fantasy provider and contest rules determine scoring, not the tournament label alone.

sources

Sources and editorial review