IND vs ENG · 3rd ODI — 14:30 ISTAUS vs SA · 2nd T20I — 18:00 ISTT20 World Cup · Asia Qualifier — 28 JulIPL 2026 · Mega Auction — 30 Aug Verified feed • refresh 12:08 IST
Points System

Points system - without inventing a scoring rubric

The cleanest way to read scoring is to separate always-on rules from conditional bonuses. We explain both, then point to where your platform publishes its own table.

A wooden editorial desk with handwritten lineup cards beside a coffee mug and a cricket stadium visible through the window
A wooden editorial desk with handwritten lineup cards beside a coffee mug and a cricket stadium visible through the window
Section 1 · Always-on rules

The events that always score

Most platforms award points for these events without any conditional threshold.

Batting
Runs × 1
Per run off the bat. Most platforms use this baseline.
Bowling
Wickets × 25
Per wicket taken by the bowler. Run-outs are typically excluded.
Fielding
Catches × 8
Per catch held. Stumpings count separately on most platforms.
Fielding
Stumpings × 12
Per stumping. Variations exist - verify on the platform.
Batting bonus
Boundary × 4
Per four hit. Sixes typically score × 6 on top of the run value.
Batting bonus
Six × 6
Per six hit. Some platforms use × 6 of the six’s run value, others use a flat bonus.
Section 2 · Conditional bonuses

Bonuses that depend on a threshold

Conditional bonuses are awarded only when the player crosses a platform-defined line.

BonusTriggerTypical value
Strike-rate bonus (batting)Batter scores at ≥ 130 strike rate+4 to +8
Economy bonus (bowling)Bowler finishes at ≤ 7.0 economy+4 to +8
Maiden overBowler bowls a maiden over+4 to +8
Duck penaltyBatter dismissed for 0 (some formats)−2 to −4
Half-century bonusBatter scores 50+4 to +8
Five-wicket haulBowler takes 5 wickets+8 to +16
Section 3 · Multipliers

Captain and vice-captain multipliers

Captain

2× multiplier (typical)

Most platforms use 2×. The exact multiplier is platform-dependent. Verify on the platform’s official rules page.

Vice-captain

1.5× multiplier (typical)

Most platforms use 1.5×. The exact multiplier is platform-dependent.

Stacking

Multipliers do not stack

You cannot apply both captain and vice-captain tags to the same player.

Section 4 · Worked example

35 runs, 2 wickets, 1 catch - labelled calculation

Sample calculation - verified scoring system

One all-rounder contributed 35 runs off 28 balls, took 2 wickets for 28 runs in 4 overs, and held 1 catch in the outfield.

Batting: 35 runs × 1 = 35
Boundary bonus: 4 fours × 4 = 16
Strike-rate bonus (≥ 125): 4
Bowling: 2 wickets × 25 = 50
Economy bonus (≤ 7.0): 4
Fielding: 1 catch × 8 = 8

117 unmultiplied. With a 2× captain multiplier this player would contribute 234 fantasy points - a haul that wins most 3-person contests outright.

Section 5 · Verify on the platform

Why we link to your platform’s rules page

Thresholds for strike rate, economy, ducks and milestones are platform-dependent. We do not invent thresholds.

The exact values for every row in the worked example are platform-specific. We have used the most common pattern, but the captain multiplier on your platform may be 2× or 1.5×. Open your platform’s official rules page before you commit a squad.

Section 6 · Questions

Frequently asked questions

Is the captain multiplier always 2×?
No. Most platforms use 2× but some use 1.5× or 3×. Verify on the platform’s official rules page.
Is the strike-rate bonus threshold always 130?
No. Common thresholds are 130 and 150, and the bonus value varies. Verify on the platform’s official rules page.
Do run-outs count for the bowler?
Typically no. Run-outs are usually excluded from the bowler’s wicket tally and sometimes appear as a separate fielding event.
Section 7 · Read next

Six neighbours from the desk

Topic ribbon

Related reading

01

Captain and vice-captain matrix

The full floor/ceiling comparison.

02

Selection tips

Role security, ownership angle, contest-specific risk.

03

How to play

The beginner walkthrough.

04

Match guides hub

Daily match preparation.

05

Predictions desk

Methodology-led previews.

06

App review methodology

Seven dimensions before we write about an app.

Editor’s pick

Fantasy Cricket Points System - Worked Examples

The desk is open. Pair this page with the match checklist in your hand and the conditions report on a second screen.

Visit partner — affiliate link Open the match checklist Compare captaincy options
Take the next step

Two ways to read more from the desk

Either way, the editorial reading stays the same — what we publish on this page is the same reading we publish everywhere else on CricketChallenge.

Get Started Compare Options Responsible Play
Extended reading · desk notes

Notes the desk keeps while writing this kind of page

A working record of the editorial decisions behind the page. Not a feature. Not a paid placement. Just the way the desk thinks about a page like this one.

Every page on CricketChallenge is written by an editor and reviewed by a second editor. The first editor writes the draft; the second editor checks the sources, the dates and the tone. The review is logged. When the second editor approves the page, it moves to publication. If the second editor asks for revisions, the revisions are logged with the date and the rationale.

The first decision the desk makes for any page is what the page is for. A captaincy page is for a reader who needs to decide between two captain picks before the toss. A points-system page is for a reader who wants to understand what their platform rewards. A responsible-play page is for a reader who has decided to set a deposit limit. Each page has a single job. Pages that try to do two jobs at once tend to do both badly, so we keep each page focused on a single reader need.

The second decision is the evidence key. Every preview on the desk carries a confirmed / probable / unknown tag. Confirmed facts come from the captains' press conference, the playing-card announcement or the league office. Probable facts come from two independent sources or one named beat reporter. Unknown facts are those we cannot verify from any reliable source. We never publish the same confidence for an unverified rumour as for an official squad announcement. The evidence key is on the page; the rule is that the reader can see what kind of evidence we are relying on.

The third decision is the date. Every page carries a last-updated stamp. The stamp is the date the most recent editor reviewed the page. It is not the date the page was first published, and it is not the date the page was created. It is the date a human editor last reviewed the page for accuracy, sourcing and tone. If a reader sees a page with an old date stamp, they should treat the page as one that needs review.

The fourth decision is what we will not publish. We do not publish rumours as news. We do not publish a story that names a player without verifying the source. We do not publish an offer that we cannot verify against the platform's own page. We do not publish a piece of editorial coverage that has been paid for. Each rule is enforced by the desk, not by a separate compliance team. The editor who writes the piece is also the editor who decides whether it stays.

The fifth decision is what we publish when we are uncertain. When the editorial team does not have enough verified information to publish a story, we do not publish the story. When the editorial team has some information but not enough to confirm a fact, we publish the fact with the probable evidence key and we mark the date. When the editorial team has a confirmed fact that contradicts a previously published fact, we update the previously published fact and add a correction note.

The sixth decision is how we work with readers. If a reader writes in with a correction, we review the correction against the primary source and update the page if the correction holds. If a reader writes in with a story tip, we review the tip and decide whether the story is worth writing. If a reader writes in with an editorial enquiry, we reply within five working days. The contact page on this site is the working channel.

The seventh decision is how we maintain editorial independence. Where affiliate links are present on the site, the link is labelled 'Visit partner — affiliate link' and the affiliate disclosure is on the page. Where the partner programme would benefit from a piece of editorial coverage, the editor who writes the piece decides what the piece says. The partner programme does not see the draft before publication. The partner programme does not have a veto over the published piece.

These decisions are the editorial standard we hold ourselves to. They are not negotiable and they are not relaxable. The reader can hold us to them by reading the page, checking the date stamp, checking the evidence key, and writing to us when something is wrong. If you have read this far, you are probably the kind of reader we publish for.