Home · Points system
Method desk

Points system — the standard scoring rules and how to read them

The most widely used fantasy scoring system in India, plus a phase-by-phase read on which actions move most points and which ones quietly eat into your total.

A scoring table overlay on a cricket action photograph, illustrating the points system.
Standard scoring

The most widely used fantasy points table

ActionPoints
Run scored+1
Boundary bonus+4
Six bonus+6
Half-century+4
Century+8
Wicket (pace)+25
Wicket (spin)+25
Wicket (LBW / bowled bonus)+8
Maiden over+4
Duck (batter, top-3)-3
Duck (batter, lower order)-1
Catch+8
Stumping+12
Run out (direct)+12
Run out (catcher)+6
Strike rate bonus (run rate 12+)+4
Strike rate bonus (run rate 14+)+8
Economy bonus (≤ 6 RPO)+4
Economy bonus (≤ 5 RPO)+6

Verify against your platform's table. The captain matrix on this desk assumes the most widely used scoring system. Other systems have different strike-rate / economy thresholds.

Where the points are

The four moves that move most fantasy points

1 · Captain multiplier

The captain doubles all other points. A captain pick on a 70-point performance becomes 140 points with the multiplier. The captain pick is the single biggest lever on your team. Read the captain matrix on the predictions hub before you lock.

3 · Strike-rate bonus

A batter with a strike rate above the run-rate threshold earns a bonus. On a 12-RPO chase the bonus is +4; on a 14-RPO chase the bonus is +8. The bonus rewards acceleration. Read the run-rate forecast and the deck before you choose the captain.

3 · Wicket bonus

A bowler takes 25 points per wicket. With the LBW / bowled bonus, the wicket value goes to 33. The captain multiplier on a wicket-taking bowler is the highest-leverage single decision on a turning deck. Read the venue and the deck.

4 · Economy bonus

A bowler with an economy under 6 RPO earns a bonus. The bonus rewards control. On flat decks where wickets are scarce, the economy bonus is the differentiator. Read the conditions and the workload before you lock.

Reading the points

What a typical fantasy points distribution looks like

A typical 11-player fantasy team scores between 280-450 points in a match where no captain gets a 50-point+ performance. The distribution is roughly 30% batting, 30% bowling, 20% fielding and 20% bonuses. Captain picks are responsible for a large share of the variance — the captain multiplier widens the spread on the leaderboard.

Which players score most

The role that moves most points on a typical fixture

Powerplay bowlers

A powerplay bowler with two wickets and an economy under 6 can score 60-80 points before bonuses. With the captain multiplier, that becomes 120-160. The desk reads the powerplay bowler as a high-leverage captain pick on overcast conditions.

Middle-overs spinners

A middle-overs spinner with two wickets and an economy under 7 can score 55-70 points before bonuses. On a turning deck the differential between a Tier-1 captain and a Tier-3 captain is the spinner's wicket-share.

Top-order anchors

A top-order anchor with 60-80 runs on a flat deck scores 70-90 points before the captain multiplier. The captain multiplier on a 90-point top-order becomes 180, which moves grand-league ranks significantly.

Death-overs finishers

A death-overs finisher with 35-50 runs on a strike rate above 200 scores 55-80 points before the captain multiplier. The captain multiplier on a 70-point finisher becomes 140, which is the highest leverage on a flat deck in a chase role.

Frequently asked

Questions our readers ask

No. Each platform publishes its own scoring rules. The numbers on this page are the most widely used system in India and what the desk references. Verify against your specific platform's published rules before locking your team.

A captain pick. The captain earns double; the vice-captain only if the captain doesn't play. A captain pick with a 70-point innings on 35 actual points becomes 140 points with the multiplier; a captain pick with a 200-point allrounder performance becomes 400+ points.

Strike-rate bonuses and economy bonuses. Some platforms apply strike-rate bonuses more aggressively; others apply economy bonuses more aggressively. Read your platform's table before you lock.

Reading support

How this page relates to the rest of the desk

The desk's coverage is interconnected

Every page on this site connects to the editorial graph — captain matrices link to predictions, predictions link to fantasy tips, fantasy tips link to player profiles, player profiles link to team desks, team desks link to venue reads. Reading the desk's coverage weekly keeps your calibration of the framework current.

This page is one node in the graph. When the inputs on this page change, the related coverage is updated. The change log is published in the editor's monthly note; readers can see the run of changes across the desk.

What to read next

From this page, the most useful next reads are: (1) the predictions hub for today's captain matrix; (2) the fantasy-tips hub for the decision framework; (3) the team desks for the squad-level reads; (4) the verification pages for safety guidance on third-party products.

Each of those is one click away from this page — the link is in the page footer, in the navigation bar, or in the related-coverage section of this page. Bookmark the desk-level landing pages for fast access; bookmark the article-level pages for deep reads.

Editor note

How an editor works this page

1

Inputs

The editor reads every input before the page publishes. Inputs include public sources, the desk's previous reads, and any source-tip submissions. The editor labels every input as confirmed, reported, or projected.

2

Verification

The editor runs the verification ladder on every claim. Confirmed (verified, on the record), reported (single-source, on the record), projected (analyst inference), editorial lean (weighted view across inputs).

3

Read

The editor writes the desk's read with a confidence tag (high, moderate, cautious, no call). The confidence tag is published at the top of the read; readers can size their own calls against the tag.

4

Audit

The editor signs off on the captain matrix and the audit ladder. The audit ladder feeds the desk confidence score; the score is published quarterly with its limitations named.

Limitations

What this desk cannot do

Outcome certainty

The desk cannot guarantee fantasy outcomes. Fantasy is uncertain by nature; the desk's reads are probabilities, not certainties. We label every read with a confidence tag and never use certainty language.

Source limitation

The desk is limited to public sources. We don't have access to private net sessions, undisclosed injuries, or unreleased squad information. When the inputs are not public, the read is held.

Editorial bias

The desk writes with humans and carries implicit biases. We minimise bias by anchoring to named inputs and a named verification ladder. We publish the editor's monthly note so readers can see the bias and the track record.

Time lag

A read at 09:00 IST may be obsolete by 17:00 IST. The desk updates the captain matrix as soon as the inputs change. Freshness of any single page is bounded by the freshness of the inputs it depends on.

Reading cadence

How often to read this page

A

Daily readers

If you build fantasy teams daily, this page is in your morning reading. The captain matrix updates throughout the day; reading it before locking your team is the highest-leverage single action you can take.

B

Weekly readers

If you build fantasy teams weekly, this page anchors your week. The desk publishes weekly recaps that summarise the reads from the previous seven days. The recap is the cheapest way to catch up if you missed the week.

C

Tournament readers

If you read for tournament-level context, this page is one node in the editorial graph. The desk's quarterly audit aggregates the reads across the whole season; the publication is on the desk dashboard.

D

Casual readers

If you read occasionally, this page is the entry point to the desk. Bookmark the homepage or the predictions hub; come back when there's a specific question. The desk's coverage is free to read at any time.

Editorial commitment

What this page commits to the reader

Confirmation

Every claim on this page is labelled confirmed, reported or projected. We do not publish composite statements without naming the data window; we do not publish any framing that implies certainty without verification.

Correction

If this page is wrong, the correction is published at the top with a dated note. The note explains what changed, when, and why. Corrections are not deletable.

Verification

Every input on this page is cross-checked against at least one independent source where possible. Single-source stories are tagged reported; we do not publish anonymous tips.

Editor

An editor reads this page before publication. The editor signs off on the captain matrix, the audit ladder, and the verification tags. The editor's note is published monthly.

Play now