A fantasy cricket points system reference for T20. Batting points, bowling points, fielding points, captain multiplier, and the role-specific bonuses. Always verify the operator’s published table before lock.
Runs, boundaries, strike-rate bonuses, and milestones. The batting points table rewards both accumulation and acceleration.
Batting points in T20 fantasy consist of: 1 point per run, 4 points per boundary, 6 points per six, strike-rate bonuses at 130+ and 150+, and milestone bonuses at 30 / 50 / 100. The exact figures vary by operator — verify on the official table.
The strike-rate bonus is the most under-read input. A batter who scores 30 off 25 (SR 120) earns fewer points than a batter who scores 30 off 20 (SR 150). Acceleration matters more than accumulation in T20.
Wickets, dot balls, economy bonus, and milestones. The bowling points table rewards wicket-taking and dot-ball pressure.
| Action | Points | Notes |
|---|---|---|
| Wicket | 25 pts | LBW and bowled count |
| LBW / bowled bonus | 8 pts | On top of the wicket |
| Dot ball | 1 pt | Counts every dot |
| Economy < 5 rpo | 6 pts | Min 2 overs |
| Economy 5-6 rpo | 4 pts | Min 2 overs |
| Maiden over | 4 pts | Rare in T20 |
| 3-wicket haul | 4 pts | On top of wickets |
| 5-wicket haul | 8 pts | Very rare |
Catches, stumpings, run-outs, and the wicketkeeper bonus. Fielding points reward glovework and athletic fielding.
8 points per catch. Outfield and slip both count. A fielder with 3 catches adds 24 points before any batting or bowling.
12 points per stumping. Wicketkeeper-specific. A keeper with 2 stumpings adds 24 points — comparable to a top-order batter who makes 30.
12 points for a direct hit. Run-outs at the non-striker’s end are rare but high-value.
6 points for the thrower or the catcher in a run-out. The points split depends on the operator.
Some operators award a bonus for catches and stumpings combined (e.g. 4 catches = +4 bonus). Verify on the operator’s table.
Some operators award 4-8 points for a save at the boundary that prevents a six. Verify on the operator’s table.
The captain and vice-captain multipliers are the single biggest decision in your squad. Pick the captain from the role with the highest expected points; pick the VC from a role-stable accumulator.
The captain’s points are doubled (2x); the vice-captain’s points are multiplied by 1.5x. The captain pick is your headline call. The vice-captain pick is your hedge — pick from a role-stable accumulator so the hedge survives even if your captain fails.
Some operators also offer an impact-player slot or a triple-captain multiplier. Read the operator’s published multipliers before lock.
IPL picks →
For fantasy cricket scoring, the operator’s own current instructions must outrank screenshots, social posts, and memory. Read the exact language for batting, bowling, fielding, economy, strike rate, and captain multipliers, then record the date. Product rules, limits, and scoring bands can change without matching an older explainer.
If a condition affects identity, deposits, rewards, entry, or withdrawals, verify on the operator’s official site. We have not independently verified operator-specific values unless a dated source is stated. Do not treat a typical industry practice as a promise.
Bitstarz treats the result as conditional, not guaranteed. Recheck official information whenever a lineup, rule, status, offer, legal position, or payment detail can change.
Confirm the verified domain, the account name, current eligibility, and the exact action you intend to take. For fantasy cricket scoring, decide in advance what a successful outcome should look like and where the confirmation will appear.
Save non-sensitive evidence such as a transaction ID, rules timestamp, or ticket number. Never save an OTP, password, full card number, or unmasked identity document in casual notes. Good records help without creating a second security risk.
Bitstarz treats the result as conditional, not guaranteed. Recheck official information whenever a lineup, rule, status, offer, legal position, or payment detail can change.
Imagine a picker facing fantasy cricket scoring for the first time. The sensible route is to use the current operator rule table, completed scorecards, and worked examples, test the smallest practical action where relevant, and stop if any detail conflicts with the published rules. A small test exposes process problems before they become expensive.
The decision is not whether the interface looks polished. It is whether which actions create points and how role volume changes expected totals. When evidence is incomplete, pause and ask verified support for a written answer instead of filling the gap with an assumption.
Bitstarz treats the result as conditional, not guaranteed. Recheck official information whenever a lineup, rule, status, offer, legal position, or payment detail can change.
Many account actions move through several states: submitted, under review, accepted, processed, and completed. A status still inside the operator’s published window is different from a rejected or reversed action. Track the stage before sending repeated requests.
If the published window passes, send one clear ticket containing the account identifier, timestamp, transaction or contest reference, and a concise description. Repeated attempts can create duplicate cases and make the timeline harder to reconstruct.
Bitstarz treats the result as conditional, not guaranteed. Recheck official information whenever a lineup, rule, status, offer, legal position, or payment detail can change.
The visible fee or credit cost is only one part of fantasy cricket scoring. Also consider time, locked funds, missed deadlines, variance, identity exposure, and the possibility that an offer or contest condition changes the usable value.
Set a fixed limit before the event. A limit chosen after a loss is usually not a limit; it is a reaction. Never borrow to participate, never chase a result, and take a break if the activity creates stress or secrecy.
Bitstarz treats the result as conditional, not guaranteed. Recheck official information whenever a lineup, rule, status, offer, legal position, or payment detail can change.
Useful records include dates, rule versions, non-sensitive screenshots, ticket numbers, and the exact wording of a support reply. They help distinguish a product issue from user error and support a focused escalation.
Redact PAN, Aadhaar, bank details, addresses, QR codes, and balances before sharing any image. Verified support should not ask for a password or OTP. A request for either is a reason to stop the conversation.
Bitstarz treats the result as conditional, not guaranteed. Recheck official information whenever a lineup, rule, status, offer, legal position, or payment detail can change.
Use contact details shown inside the signed-in product or on the operator’s official site. Explain fantasy cricket scoring in chronological order and state the resolution requested. A short factual ticket is easier to investigate than several emotional messages.
If the first answer does not address the evidence, reply within the same case and ask for the relevant rule or status. Avoid numbers copied from search listings. We have not independently verified third-party support contacts.
Bitstarz treats the result as conditional, not guaranteed. Recheck official information whenever a lineup, rule, status, offer, legal position, or payment detail can change.
Plain answers to recurring points-table questions.
No. Operators publish their own points tables. The major T20 platforms have similar structures, but the exact figures differ. Verify before lock.
Most operators apply the SR bonus only to batters who face a minimum number of balls (typically 10). Batters who face fewer balls get the standard 1 pt/run.
The impact-player slot substitutes into your XI based on toss. Points scored by the impact player count toward your total. The captain and VC multipliers do not apply to the impact player unless explicitly stated.
Most operators count super-over runs and wickets. Verify on the operator’s table — a small number of operators exclude the super over.
Rain-affected matches are typically scored on the actual overs bowled. DLS-adjusted totals do not affect fantasy scoring — the runs and wickets counted are the actual ones.
On the operator’s official site under Help, FAQ, or Points System. We do not host the operator’s points table on this site.
Different contests reward different roles. Read the contest types before you join.