BatBall11 Points System — Complete Scoring Reference
Every event-by-event scoring rule, captain multiplier, deduction and abandoned-match handling — in one readable reference.
How to read this page
The Points System is the single most-read page on the desk. Every event your players earn or lose points for is listed below with the value, the qualifying conditions, and any edge cases (abandoned matches, super over, DLS).
Where the exact values differ between platforms, the desk notes the variation rather than picking a single number. Always cross-check against the operator's published scoring rules before joining a paid contest.
Batting events
Points awarded for batting actions during a match.
| Event | Points | Condition | Edge case |
|---|---|---|---|
| Run scored | 1 pt | Per run | Counted on legal delivery only |
| Boundary bonus | 4 pts | Hit reaches boundary on full | Allotted on top of run value |
| Six bonus | 6 pts | Hit crosses boundary without bounce | Replaces boundary bonus |
| 30-run milestone | 4 pts | Reached 30+ runs | One-off bonus |
| 50-run milestone | 8 pts | Reached 50+ runs (half-century) | One-off bonus |
| 100-run milestone | 16 pts | Reached 100+ runs (century) | One-off bonus |
| Duck dismissal | −2 pts | Batsman out for 0 (batter only, not tail-enders) | Definition varies by platform |
| Strike rate ≥ 130 | 4 pts | T20 only, ≥30 balls faced | Some platforms use ≥150 |
| Strike rate ≤ 50 | −2 pts | T20 only, ≥15 balls faced | Not all platforms apply this |
Bowling events
Points awarded for bowling actions during a match.
| Event | Points | Condition | Edge case |
|---|---|---|---|
| Wicket | 25 pts | Bowler takes a wicket | Run-outs not credited to bowler |
| LBW / Bowled bonus | 8 pts | Mode of dismissal is bowled or LBW | On top of wicket points |
| Maiden over | 4 pts | Over completed with 0 runs (incl. wides/no-balls) | Some platforms exclude wides |
| 3-wicket haul | 4 pts | 3 wickets in the match | One-off bonus |
| 4-wicket haul | 8 pts | 4 wickets in the match | One-off bonus |
| 5-wicket haul | 16 pts | 5 wickets in the match | One-off bonus |
| Economy rate ≤ 5 | 6 pts | T20 only, ≥2 overs bowled | Some platforms use ≤6 |
| Economy rate ≥ 10 | −2 pts | T20 only, ≥2 overs bowled | Some platforms use ≥11 |
Fielding events
Points awarded for catches, stumpings and run-outs in the field.
Catch
8 points per catch. The fielder takes the catch cleanly. Outfield and slip catches both qualify.
Stumping
12 points for the wicket-keeper. The batsman is out of his crease when the ball is gathered by the keeper.
Run-out (direct)
12 points for the fielder who effects the run-out with a direct hit. Shared run-outs typically split the points.
Captain 2× and vice-captain 1.5×
On most fantasy platforms the captain earns 2× the points scored and the vice-captain 1.5×. Together those two choices usually account for 30-40% of your final score. Treat the captain choice as a probability call, not a popularity vote.
If your captain scores 50 and your vice-captain scores 40, your effective points from those two players are 50×2 + 40×1.5 = 160. If you had picked differently and got 60 + 30, the effective total would be 60×2 + 30×1.5 = 165 — almost identical.
Edge cases & special situations
What happens when the match doesn't follow the standard script.
Abandoned match
If the match is abandoned without a result, all contests are typically voided and entry fees refunded. Some platforms apply a minimum-overs rule (e.g. 5 overs in T20) for partial results.
Super Over
Super Over scores usually count toward fantasy totals. If the operator treats the Super Over as a separate match, scores from it may not count — check the platform's published rules.
DLS / rain-affected matches
Where the match is shortened due to rain or light, the contest typically runs on whatever overs are bowled. Fantasy totals are calculated on the actual events, not the projected full match.
Player substituted out of the XI
If a player in your XI is not in the playing eleven when the match starts, most platforms substitute the next-best player from your bench (if you selected one) or from the overall bench.
Concussion substitute
ICC concussion substitute rules may allow a like-for-like replacement during the match. Whether the substitute's points count depends on the operator's published rules.
Tie / Super Over win
Where the match is tied and decided by Super Over, the result counts as a win for the team batting second (in most formats). Fantasy contests score the events as bowled.
Captain-multiplier worked example
When does a 2× captain beat a safer 1.5× vice-captain?
Scenario A — Star captain, safe vice-captain. Player X (captain) scores 75 (effective 150). Player Y (vice-captain) scores 35 (effective 52.5). Combined: 202.5 points from two players.
Scenario B — Two safe picks. Player X scores 50 (effective 100). Player Y scores 40 (effective 60). Combined: 160 points from two players.
Scenario C — Differential captain. Player Z (low-ownership captain) scores 90 (effective 180). Player W scores 25 (effective 37.5). Combined: 217.5 points from two players — the highest, but also the highest variance.
The best strategy depends on the contest size. Small contests reward consistency; large contests reward differentiation.
Variations across platforms
Where platforms differ on exact scoring values, the desk notes the variation.
The reference values on this page are representative of major Indian fantasy cricket platforms. Exact values vary: some platforms award 0.5 points per run, others 1 point. Boundary bonuses range from 4 to 8 points. Strike rate thresholds differ (≥ 130 vs ≥ 150 in T20). Economy rate thresholds differ (≤ 5 vs ≤ 6).
Captain multipliers also vary: most platforms use 2× captain and 1.5× vice-captain, but some offer 2.5× captain or 1× captain with a different vice-captain structure. Triple-captain variants exist but are less common.
The desk's recommendation: read the operator's published scoring rules page before joining any paid contest. The five minutes spent reading saves hundreds of contest points of avoidable scoring-rule mistakes.
Why captain choice dominates scoring
The math behind why captain is half your score.
Consider a typical 11-player fantasy team with average score 30 points per player (a generous average). Total team score: 330 points. The captain's 2× multiplier adds the captain's base score on top — so if the captain scored 50, the effective contribution is 100 (50 base + 50 multiplier bonus). Vice-captain adds 50% of the vice-captain's score.
Together, the captain and vice-captain typically contribute 30-40% of the final team score. This is why the captain pick dominates contest outcomes — a poor captain choice can sink an otherwise well-built team, while a great captain pick can lift a mediocre team.
The desk's captain selection framework (overs remaining, match-up, batting position) is built to reduce the variance of the captain pick. It does not eliminate variance — fantasy is entertainment, not investing — but it tilts the odds in your favour.
Reading the scorecard mid-match
How to interpret your fantasy team's live score during a match.
Captain multiplier updates in real time
Most platforms update the score live as events occur. The captain's contribution updates with the 2× multiplier applied instantly.
Bonus stacking
Boundary bonus (4 pts) and six bonus (6 pts) are awarded on top of the run value. A 4 counts as 1 + 4 = 5. A 6 counts as 1 + 6 = 7.
Milestone bonuses are one-off
The 30/50/100 run bonuses are awarded once when the milestone is reached, not per delivery. The 3/4/5 wicket bonuses are similar.
Deductions are real
A duck dismissal costs 2 points. A sub-economy-rate over costs 2 points. These deductions can swing a close contest.
Apply the scoring to your team
Predictions desk uses the scoring reference to identify captain picks, differential picks and value picks for every upcoming match.
Why this topic matters for adult fantasy-cricket readers
How this page fits into the desk's broader coverage and where it connects to other guides.
Fantasy cricket is a knowledge-intensive hobby. The desk's role is to surface verified information that helps readers make their own decisions — not to promise outcomes or push a single strategy. Each page on the desk is a building block in the larger editorial coverage of the topic.
This page in particular addresses one specific aspect of the broader topic. The desk recommends pairing it with the related coverage linked at the bottom of the page. The pairing gives readers both the narrow (this page) and the broader (the related hubs) view.
Editorial pages are not marketing pages. The desk labels unverifiable claims as such, refreshes time-sensitive facts on a 14-day cycle, and logs corrections visibly. If a fact looks out of date, the desk wants to know — send a note to the customer-care channel.
How the editorial team keeps this page current
The verification cycle and what triggers an update.
14-day refresh cycle
Time-sensitive pages (state eligibility, app version, withdrawal timelines, bonus offers) are re-checked every 14 days. The last-reviewed date at the top of the page reflects the latest cycle.
30-day refresh cycle
Reference material (glossary terms, scoring rules, role definitions) is re-checked every 30 days. Material changes are logged visibly; minor copy edits are not.
Triggered updates
If the operator announces a material change (new app version, scoring rule update, state eligibility change), the desk updates the affected pages within 48 hours of the announcement.
Reader-driven updates
Reader notes sent to the customer-care channel are read and triaged. If a note flags a discrepancy that the desk can confirm against first-party sources, the desk updates the page and credits the note (if requested).
Correction log
Material corrections are logged at the top of the affected page with the date and the change. Silent corrections are not used — if the date is silent, the correction did not happen.
Editorial verdict independence
The desk's editorial verdicts (the review, the captain framework, the venue notes) are independent of the operator's commercial interests. Where the desk disagrees with operator marketing claims, the disagreement is stated with reasoning.