How to read the table below
Each action has a base score. Some actions also carry bonuses — boundary bonus, strike-rate bonus, economy bonus, dot-ball bonus — that add to the base score. Captain and vice-captain multipliers are applied last. The desk maintains a single source-of-truth table; partner operator deviations are listed at the bottom.
Batting points
| Action | Points | Condition |
|---|---|---|
| Run scored | +1 per run | Standard |
| Boundary (4) | +4 (boundary bonus only) | Run score + bonus |
| Six hit (6) | +6 (six bonus only) | Run score + bonus |
| Half-century (50) | +8 | Adds to run score |
| Century (100) | +16 | Adds to run score |
| Duck | −2 | Batter, wicketkeeper, all-rounder only |
| Strike-rate ≥10 runs/over (≥11 in 10-over chase) | +6 | Balls-faced condition |
| Strike-rate ≥12 runs/over (≥13 in 10-over chase) | +12 | Balls-faced condition |
| Strike-rate ≤5 runs/over (≤5 in 10-over chase) | −6 | Balls-faced condition |
Bowling points
| Action | Points | Condition |
|---|---|---|
| Wicket (any bowler) | +25 base | Wicket alone |
| LBW / Bowled bonus | +8 | No catch between bowler and batter |
| Wicket (3w+ in match) | +4 | Bonus on third and beyond |
| Wicket (4w+ in match) | +8 | Bonus on fourth and beyond |
| Wicket (5w+ in match) | +16 | Bonus on fifth and beyond |
| Maiden over | +4 | T20 rarity; check role |
| Economy ≤5 runs/over | +6 | Minimum 2 overs |
| Economy ≥11 runs/over | −6 | Minimum 2 overs |
| Dot ball bonus | +1 per dot ball | Balls bowled |
Fielding and wicketkeeping
| Action | Points | Condition |
|---|---|---|
| Catch taken | +8 | Wicketkeeper + outfield same |
| 3-catch bonus | +4 | Bonus on the third and beyond |
| Stumping | +12 | Wicketkeeper-only |
| Run-out direct hit | +12 | Single fielder hits stumps |
| Run-out assist | +6 | Misfield reaches stumps via another fielder |
| Run-out (affected fielder) | +2 | Misfield enabled dismissal |
Worked example — a 50-ball scenario
Consider an opener who scores 38 runs off 30 balls and is caught at long-on. The points accumulate as: 38 runs × 1 = 38. One boundary (4) bonus at +4. Strike-rate 7.6 runs/over (just under the bonus threshold), so no strike-rate bonus. Out via catch, so the bowler earns +8 wicket + +8 catch = +16. The captain, if this player is captain, doubles both.
Now consider a wicketkeeper who takes three catches and a stumping behind the stumps: 3 catches at +8 = 24, plus +4 third-catch bonus = 28, plus a stumping at +12 = 40. Wicketkeeping points are consistently the second-highest points category on the team-sheet after the captain’s multiplier.
Impact-player mechanics
The impact-player rule was introduced in IPL 2023 and has carried through unchanged into 2026. Each side may nominate four substitutes before the toss and swap one in during the match. Fantasy implications:
- A captain you pick may be the impact-player swap-out if the bowler comes on.
- A wicketkeeper you pick may be rotated mid-innings — review the franchise deck-rotation announcement.
- Vice-captain becomes your insurance; choose the highest-ceiling differential for the vice slot.
Partner-operator deviations
Each partner operator publishes its own scoring sheet, usually within the help centre or the league rules. Common deviations: bonus tiers for strike-rate thresholds, dot-ball bonus amounts, and the specific value of the duck penalty. The desk audits each partner operator’s published rules weekly; the audit is used as a reference, not a guarantee, and you should always confirm the rules before joining a contest.
The strike-rate bonus math
Strike-rate bonuses reward boundary hitters. A batter at 175+ strike rate in a completed innings picks up +4 bonus on top of the run score. A batter at 200+ strike rate picks up another +4 — total +8 across the two bands. Captain picks on boundary hitters compound this.
The economy-rate bonus math
Economy bonuses reward bowlers who go under 5 runs per over across a minimum two-over spell. A bowler at 4.8 economy picks up +6 bonus. Death-over bowlers who restrict the boundary line amplify captain-cy multiplier wins on top.
Fielding bonuses compound across catches
Three-catch bonuses are +4. Five-catch games are rare but compound quickly. Wicketkeeping bonuses for stumpings are +12 each, and three-catch wicketkeepers can hit 40+ points behind the stumps alone.
How the captaincy multiplier amplifies a captain’s contribution
The captain’s points are doubled at the end. A captain at 80 raw points contributes 160. The desk treats captaincy as a structural decision, not a tip — see the captain-watch frame inside /match-preview/.
What the points system is not
The points system is not a forecast. It is not a tip. It is the scoring reference that the partner operator’s contest engine uses to assign points after the fixture. The desk maintains a working reference; the partner operator publishes the official rules inside the app.
Discrepancy handling between the desk and the partner
When the desk reference and the partner operator published rules disagree, the partner operator wins. The desk publishes a corrections note inside /news/ so readers are aware of the deviation. The corrections note carries a verification date.
Historical tweaks to the points system
The partner operator has tweaked the points system between seasons in the past — typically on the boundary bonus, the duck penalty, and the strike-rate threshold. The desk audits the published rules weekly and notes material changes inside the reference.
The batting points in detail
Run scored = +1 per run. Boundary (4) = +4 bonus over the four runs already scored. Six hit (6) = +6 bonus over the six runs already scored. Half-century (50) = +8 bonus. Century (100) = +16 bonus. Duck = -2 (batter, wicketkeeper, all-rounder only). Strike-rate bonuses apply at thresholds that depend on the innings length.
The bowling points in detail
Wicket = +25 base. LBW / Bowled bonus = +8. Three-wicket bonus = +4. Four-wicket bonus = +8. Five-wicket bonus = +16. Maiden over = +4 (T20 rarity). Economy bonuses apply at thresholds that depend on the bowler’s overs bowled.
Fielding points in detail
Catch = +8. Three-catch bonus = +4. Stumping = +12 (wicketkeeper-only). Run-out direct hit = +12. Run-out assist = +6. Run-out affected fielder = +2.
The points system in detail
The desk publishes a platform-agnostic points reference. The system covers runs scored, boundaries, sixes, half-centuries, centuries, ducks, strike-rate bonuses, wickets, LBW/Bowled bonuses, maiden overs, economy bonuses, dot-ball bonuses, catches, stumpings, run-outs, and impact-player mechanics.
The desk’s three scoring asks
First, verify the partner operator’s published rules before joining a contest. Second, treat the points system as a reference, not a forecast. Third, treat the captaincy multiplier as a structural decision, not a tip.
How the desk treats scoring deviations
When the desk reference and the partner operator published rules disagree, the partner operator wins. The desk publishes a corrections note inside /news/ so readers are aware of the deviation. The corrections note carries a verification date.
What this reference does not cover
This reference covers the platform-agnostic scoring. It does not cover partner-specific deviations; those live inside the partner operator’s app. It does not cover contest product features; those live at /how-to-play/.
The points discipline
The desk publishes a platform-agnostic points reference. The system covers runs scored, boundaries, sixes, half-centuries, centuries, ducks, strike-rate bonuses, wickets, LBW/Bowled bonuses, maiden overs, economy bonuses, dot-ball bonuses, catches, stumpings, run-outs, and impact-player mechanics.
The three scoring asks
First, verify the partner operator’s published rules before joining a contest. Second, treat the points system as a reference, not a forecast. Third, treat the captaincy multiplier as a structural decision, not a tip.
The points audit
The desk audits the published points reference quarterly. The audit verifies each entry against the partner operator’s published rules. The audit notes material changes inside the corrections pathway. The audit cycle is part of the desk’s quality signal.
Closing thoughts on points
The points system is a reference, not a forecast. The desk publishes the reference with a verification reviewer name and a corrections pathway. The desk’s role is editorial reference.
