Treating one operator's table as universal
Operators use different scoring structures. The operator's published points table is the binding source for any contest.
Points system
Fantasy cricket points system: how scoring really works.
Fantasy cricket scoring looks similar across operators until you read the small print. Captain multipliers, strike-rate bonuses, economy bonuses and fielding points all vary. This page walks through the common structures and the fields that change platform to platform.
Batting
The points a batter typically earns.
| Event | Common points | Notes |
|---|---|---|
| Run | 1 pt / run | Standard across operators |
| Boundary (4) | +4 bonus | Most operators add 4 pts on top of the runs |
| Six | +6 bonus | Most operators add 6 pts on top of the runs |
| Half-century | +4 or +8 | Bonus varies: 4 pts or 8 pts depending on platform |
| Century | +8 or +16 | Rare in T20; rarely relevant |
| Dismissal (duck) | −2 | Some operators exempt opening batters; some deduct more |
| Strike rate (≥ 170 in T20) | +4 to +6 | Threshold and bonus differ — verify on the operator's page |
| Strike rate (< 50 in T20) | −2 to −6 | Penalty threshold differs — penalty depth differs |
Bowling
The points a bowler typically earns.
| Event | Common points | Notes |
|---|---|---|
| Wicket | 25 pts (varies 20–31) | The biggest single-event swing in a lineup |
| LBW / Bowled bonus | +8 | Some operators reward skill dismissals |
| Maiden over | +4 to +8 | Rare in T20; relevant in longer formats |
| 3-wicket haul | +4 to +8 | Threshold and bonus differ by operator |
| 5-wicket haul | +8 to +16 | Rare in T20 |
| Economy (≤ 5 rpo in T20) | +6 | Threshold and bonus differ |
| Economy (≥ 11 rpo in T20) | −2 to −6 | Penalty threshold differs |
Fielding
Catches, run-outs, stumpings.
| Event | Common points | Notes |
|---|---|---|
| Catch | 8 pts (varies 4–10) | Most operators add for each catch |
| 3-catch bonus | +4 | Some operators stack a 3-catch bonus |
| Stumping | 12 pts (varies 8–12) | Wicketkeeper-only |
| Run-out (direct) | 12 pts | Direct-hit run-out |
| Run-out (catcher) | 6 pts | Thrower credit |
Captaincy
How multipliers change the math.
Most operators apply a 2× multiplier to captain points and 1.5× to vice-captain points. A handful run 3× / 2× or a tiered multiplier for "leader" picks. The multiplier is the single biggest reason a captain pick swings a contest outcome — verify the multiplier before you lock your pick.
Treat the captain pick as a risk-allocation call, not a prediction. Cricuru's captaincy framework uses opportunity, role security and downside — not a confidence rating.
What changes platform to platform
Five fields to verify on the operator's page.
01
Strike-rate thresholds
Most operators use a 170-runs-per-100-balls threshold for the batting bonus, but the exact number and the bonus depth both vary.
02
Economy thresholds
Economy bonuses in T20 use 5-runs-per-over or 6-runs-per-over depending on the platform. Verify on the operator's published page.
03
Captain multiplier
2× is most common, but 3× captain and 2× vice-captain are not. Some operators also run a separate "leader" or "triple-captain" multiplier.
04
Wicket value
Wicket points range from 20 to 31. A four-over spell that takes two wickets can swing by 20+ points depending on the platform.
05
Fielding stacking
3-catch bonuses, direct-hit run-out bonuses and stumping credits differ. Fielding is often the underrated swing factor in T20.
Worked example
Read a worked scoring walkthrough.
The how-to-play hub has a step-by-step worked example using a named operator's published rules. Cross-reference the points table above with the operator's verification page.
Points FAQ
Five questions about fantasy points scoring.
Is there one universal fantasy points system?
No. Operators use different scoring structures. Common fields include run points, boundary bonuses, dot-ball bonuses, wicket points, economy-rate bonuses and catch/stumping points. The exact values and bonuses vary.
What is a typical batting scoring band?
A common pattern: 1 point per run, 4 bonus for a boundary, 6 bonus for a six, 4 bonus for a thirty, 8 bonus for a fifty, 16 bonus for a hundred. Some operators add strike-rate bonuses above 170.
What is a typical bowling scoring band?
A common pattern: 25 points per wicket, 8 bonus for three wickets, 16 bonus for four wickets, 4 bonus for a maiden, plus economy-rate bonuses for runs-per-over bands. Some operators add dot-ball bonuses.
What about captain and vice-captain multipliers?
Most operators apply a 2x captain multiplier and a 1.5x vice-captain multiplier. Some operators have introduced a 3x / 2x scheme. The multiplier is always operator-specific.
Does Cricuru publish a points table to copy?
No. Cricuru publishes an explainer of common structures and flags the fields that change platform to platform. The operator's published points table is the binding source.
Do fielding points really matter?
Catches, stumpings and run-outs can swing a fantasy week, especially in tight contests. Fielding points vary widely across operators, and that variance is one reason Cricuru does not publish a single 'universal' points table.
More pitfalls
Five more pitfalls worth flagging on this topic.
Ignoring the captain multiplier
A captain pick without reading the multiplier is a guess. Read the multiplier before locking the lineup.
Trusting a single bonus field
Boundary bonuses, strike-rate bonuses and dot-ball bonuses vary by operator. The points table is the only document that decides who wins.
Skipping fielding points
Fielding points — catches, stumpings, run-outs — can swing a fantasy week. The variance is one reason Cricuru does not publish a universal points table.
Reading a points table without dates
Points tables change. A points table without a date is not a binding source. Use the operator's current published table.
Common pitfalls
Six pitfalls the Cricuru desk flags on this topic.
Treating one operator's table as universal
Operators use different scoring structures. The operator's published points table is the binding source for any contest.
Ignoring the captain multiplier
A captain pick without reading the multiplier is a guess. Read the multiplier before locking the lineup.
Trusting a single bonus field
Boundary bonuses, strike-rate bonuses and dot-ball bonuses vary by operator. The points table is the only document that decides who wins.
Skipping fielding points
Fielding points — catches, stumpings, run-outs — can swing a fantasy week. The variance is one reason Cricuru does not publish a universal points table.
Reading a points table without dates
Points tables change. A points table without a date is not a binding source. Use the operator's current published table.
Forgetting the economy-rate bonus
Economy-rate bonuses reward bowlers in the 4–6 runs-per-over band. A points table that hides the band is incomplete.
How Cricuru covers points scoring.
Cricuru's points-system page is an explainer, not a copy-able table. We describe the common structures and flag the fields that change platform to platform, because there is no single universal points table.
Our sources: the operator's published points table; the operator's help-centre explainer; named public references for common scoring bands. Where a bonus field — boundary bonus, strike-rate bonus, dot-ball bonus — varies, the page notes the variance.
What Cricuru does not publish: a copy-able points table, a paid points-table generator, or any output that frames one operator's points as a universal rule. The operator's published points table is the binding source.
Verification cadence: monthly review of operator-side scoring changes; per-feature refresh on a published points-table update; an editor's note when a scoring change materially affects the explainer.
What changes when an operator updates scoring: the explainer on this page flags the field that changed; the operator's published points table remains the binding source. Cricuru publishes an editor's note when a scoring change is material.
What to watch next: a published operator-side points-table change; a reader-reported scoring question; a methodology update that adds a new field. The next points-reference refresh carries the update.
Why this matters: the points table is the only document that decides who wins a contest. A captaincy read built from a points table you have not read is a guess. Read the operator's points table before the lineup lock.
How to use this page: (1) read the operator's published points table; (2) read the common-fields explainer for the operator's variance; (3) build the captaincy read with the operator's multiplier. The points table is the only document that decides who wins.
Related guides
Where to read next.
Guide
Fantasy Cricket
Selection logic across the squad.
Guide
How to Play
Beginner process guide.
Guide
Fantasy Tools
Lineup builder and captain matrix.
Guide
Match Predictions
Captaincy frameworks with post-toss tables.
Guide
Cricuru App
Operator-side entry point with a safety-first read.
Guide
Wallet & KYC
Withdrawal and identity verification.