Fantasy cricket points calculator: 22Bet India T20 scoring math and Dream11 reference framework

1. What a fantasy cricket points calculator actually does

A fantasy cricket points calculator is a reference framework that takes player match stats (runs scored, balls faced, wickets taken, overs bowled, catches, stumpings, run-outs) and converts them into the Dream11 / 22Bet India fantasy point total for that player. The calculator does not predict the match — it just applies the scoring matrix consistently so you can compare two players on a like-for-like basis before captain selection.

On the 22Bet India fantasy platform the calculator runs in four passes: (1) base batting points, (2) base bowling points, (3) fielding points, (4) captain and vice-captain multipliers. Each pass adds to the running total; the captain 2x is applied to the final number, not to intermediate values. This is the most common calculator mistake — applying the captain 2x to base points before adding bonuses double-counts the strike-rate and milestone bonuses.

2. T20 batting points matrix used by 22Bet India fantasy

The T20 batting matrix is the longest section of the calculator. Each event has a fixed point value; the calculator sums them up and applies strike-rate bonuses at the end. Use the table below as the canonical reference when running your own projections on the 22Bet India fantasy platform.

• Per run: 1 point. A 50-run innings contributes 50 base batting points before any modifier.
• Boundary bonus (4s): 4 points per four. An innings with 6 fours adds 24 boundary points on top of the per-run base.
• Six bonus: 6 points per six. An innings with 3 sixes adds 18 six points on top of the per-run base.
• 30-run milestone bonus: 4 points. Awarded once when the batsman crosses 30 runs. Adds 4 points on top of everything else.
• 50-run milestone bonus: 8 points (cumulative with 30). Awarded once at 50; the batsman now has 4 (for 30) + 8 (for 50) = 12 milestone bonus points.
• 100-run milestone bonus: 16 points (cumulative). Awarded at 100; total milestone bonus becomes 4 + 8 + 16 = 28 points.
• Duck penalty (batsman / wicket-keeper only): -2 points. Applied when the batsman is dismissed for 0. Bowlers who score 0 are not penalised.
• Strike-rate bonus ≥ 170 runs/100 balls: +6 points. SR 170 is the elite boundary; the calculator awards the full 6 points.
• Strike-rate bonus 150-170: +4 points. SR 150-170 is the strong-positive band.
• Strike-rate bonus 130-150: +2 points. SR 130-150 is the standard positive band.
• Strike-rate penalty 60-70: -2 points. SR 60-70 is a slow-innings penalty on most scoring systems.
• Strike-rate penalty 50-60: -4 points. SR 50-60 is a worse penalty; signals a sub-par T20 innings.
• Strike-rate penalty below 50: -6 points. SR below 50 is the worst band and signals a failed innings.

The strike-rate bonuses and penalties make the batting points matrix non-linear. A batsman scoring 30 off 12 balls (SR 250) earns 30 base + 24 boundary bonus + 8 six bonus (say 1 six) + 4 milestone (30) + 6 SR bonus = 72 points. A batsman scoring 30 off 60 balls (SR 50) earns 30 base + 8 boundary bonus (say 2 fours) + 4 milestone + (-6 SR penalty) = 36 points. Same runs, dramatically different fantasy totals. The calculator is what makes this visible.

3. T20 bowling points matrix used by 22Bet India fantasy

The T20 bowling matrix rewards wicket-taking more than dot-ball containment, but economy bonuses lift the consistent bowlers into fantasy relevance. The calculator applies bowling points in this order: per-wicket base, LBW/bowled bonus, milestone bonuses, then economy modifier at the end.

• Per wicket: 25 points. Every wicket is worth 25 base points before modifiers.
• LBW / bowled bonus: 8 points per wicket. An LBW or bowled dismissal adds 8 points on top of the 25. Note: most platforms do NOT award the LBW bonus for run-outs.
• 3-wicket haul bonus: 4 points. Awarded once when the bowler reaches 3 wickets.
• 4-wicket haul bonus: 8 points (cumulative). Awarded once at 4 wickets; total haul bonus becomes 4 + 8 = 12.
• 5-wicket haul bonus: 16 points (cumulative). At 5 wickets the bowler has 4 + 8 + 16 = 28 haul bonus points on top of the per-wicket base.
• Maiden over: 4 points. Awarded per maiden over bowled. In T20 this is rare but high-value.
• Economy bonus below 5: +6 points. Sub-5 economy in T20 is elite; the calculator awards the full 6 points.
• Economy bonus 5-6: +4 points. Economy 5-6 is strong.
• Economy bonus 6-7: +2 points. Economy 6-7 is standard positive.
• Economy penalty 10-11: -2 points. Economy 10-11 is the mild penalty band.
• Economy penalty 11-12: -4 points. Economy 11-12 is worse.
• Economy penalty above 12: -6 points. Economy above 12 is the worst band.

Notice that the bowling economy modifier mirrors the batting strike-rate modifier in shape — both reward the elite band (sub-5 economy, SR >170) and penalise the worst band (above 12, SR below 50) by 6 points. This symmetry is deliberate: the matrix rewards dominance, not just participation. A bowler taking 2/18 in 4 overs (economy 4.5) earns 50 base + 16 LBW bonus (assuming both LBW) + 0 haul bonus + 6 economy bonus = 72 points. A bowler taking 2/48 in 4 overs (economy 12) earns 50 + 16 + 0 + (-6) = 60 points. Two fewer runs in the wickets column for the second bowler; the calculator shows the real cost.

4. Fielding points and how the calculator sums them

Fielding points are added LAST in the calculator after batting and bowling. The matrix is short but high-leverage: a single catch is 8 points, which can flip a marginal pick into a strong captain pick. Use this table as your fielding reference when projecting a player on the 22Bet India fantasy platform.

• Catch: 8 points per catch. A slip fielder with 2 catches adds 16 points on top of any batting contribution.
• Stumping: 12 points per stumping. Wicket-keepers earn this; the rate is higher than a catch because stumpings require both presence of mind and glove work.
• Run-out (direct hit): 12 points. A direct-hit run-out from the outfield is the highest-value fielding event.
• Run-out (catcher / non-direct): 6 points. Half-credit for the fielder who effects the run-out but did not throw direct.
• 3-catch bonus: 4 points. Some platforms award a 3-catch bonus; the 22Bet India matrix applies this when the fielder takes 3+ catches in an innings.

Fielding is the most under-valued input on the 22Bet India fantasy platform. A player who averages 25 runs but takes 1.2 catches per match is worth ~10 more fantasy points per match than a same-average player with 0.5 catches — purely from fielding. The calculator makes this visible before lock-in. Prioritise slip fielders and wicket-keepers in your team; their fielding floor pushes them up the captain matrix.

5. Captain 2x and vice-captain 1.5x: how the calculator applies multipliers

The captain and vice-captain multipliers are applied LAST, after batting, bowling, and fielding are summed. This ordering matters: the multipliers compound the final tally, not the intermediate values. The 22Bet India fantasy platform uses 2x for captain and 1.5x for vice-captain. Common calculator mistakes to avoid:

• Do NOT apply the multiplier before bonuses. If you captain a batsman who scored 50 with 6 fours, 1 six, and a 30 milestone bonus, the calculator sum is: 50 base + 24 (4s) + 6 (6s) + 4 (30 milestone) = 84 points. The captain 2x is then 84 × 2 = 168. If you mistakenly multiply base points (50 × 2 = 100) and then add bonuses (100 + 24 + 6 + 4 = 134), you under-count by 34 points. The 22Bet India fantasy matrix applies the multiplier at the end.
• Vice-captain 1.5x applies to the FINAL points, not the base. A vice-captain scoring 60 final points gets 90 points after the 1.5x. This is exactly half the captain 2x uplift (which would be 120 points).
• Captain and VC cannot be the same player. The 22Bet India fantasy team-builder rejects a duplicate captain/VC selection. Pick two distinct players; the calculator assumes this constraint.
• Captain and VC multipliers do NOT stack with any other bonus. There is no "super-captain" 3x on standard 22Bet India contests; the multipliers are fixed at 2x and 1.5x.

The captain 2x is the single biggest decision in your team because it doubles the highest-projection player's points. Run the calculator before picking captain — pick the player with the highest projected final points AFTER batting, bowling, and fielding are summed, not the player with the highest runs scored. A bowler who takes 3/24 with a catch often outscores a batsman who scores 45 off 30 balls because the bowler picks up 75 base + bonuses while the batsman picks up 45 base + bonuses.

6. Points-per-ball (PPB): the single best captaincy input

Points-per-ball (PPB) is the cleanest captaincy input because it already factors in dots, boundaries, wickets, and milestone bonuses. The formula: final fantasy points ÷ total balls faced (batting PPB) or total balls bowled (bowling PPB). On the 22Bet India fantasy platform, PPB bands tell you who is hot and who is not.

• Batting PPB above 1.5: Elite. The player is scoring 50+ in 30-35 balls; their innings is concentrated in boundaries. Cap them in small leagues; VC them in grand leagues.
• Batting PPB 1.0-1.5: Good. The player is scoring at run-a-ball or better with at least one boundary per over. Solid captain pick across all contest sizes.
• Batting PPB 0.7-1.0: Average. The player is anchoring, rotating strike, and finding the occasional boundary. VC them or leave the captain slot.
• Batting PPB below 0.7: Poor. The player is struggling against pace or spin. Leave them out of captain / VC entirely.
• Bowling PPB above 1.5: Elite. The bowler is taking a wicket every 8-10 balls and conceding under 6 runs/over. Strong captain pick in small and mid leagues.
• Bowling PPB 1.0-1.5: Good. Wicket-every-over-or-two plus economy under 7. Solid VC pick.

The PPB framework compresses the entire scoring matrix into one number. Use it as the captaincy input on the 22Bet India fantasy platform: project the PPB before the match, sort your team by PPB, captain the top, VC the second. The calculator handles the rest of the matrix when the actual match stats come in.

7. Worked example: 22Bet India IPL 2026 match projection

Run the calculator end-to-end on a real IPL 2026 projection to see how the matrix sums. Suppose Player X scored 56 off 32 balls with 5 fours and 3 sixes, took 1 catch, and bowled 2 overs for 18 runs with 1 wicket (LBW). Their batting points: 56 base + 20 (5 × 4 for fours) + 18 (3 × 6 for sixes) + 4 (30 milestone) + 8 (50 milestone) = 106 batting points. Strike-rate = 56 ÷ 32 × 100 = 175 → +6 SR bonus. Final batting = 112. Bowling points: 25 (wicket) + 8 (LBW bonus) = 33. Economy = 18 ÷ 2 = 9.0 → no economy modifier. Fielding: 8 (1 catch). Total fantasy points: 112 + 33 + 8 = 153. If captained: 153 × 2 = 306. If vice-captained: 153 × 1.5 = 229.5.

Compare to Player Y who scored 72 off 50 balls with 6 fours and 2 sixes, took 0 catches, and did not bowl. Batting: 72 base + 24 (6 fours) + 12 (2 sixes) + 4 (30) + 8 (50) = 120. Strike-rate = 72 ÷ 50 × 100 = 144 → no SR bonus (band is 130-150, +2). Final batting = 122. No bowling, no fielding. Total = 122. Cap: 244. VC: 183. Player X wins on captain 2x even though Player Y scored 16 more runs, because X had 1 catch + 1 wicket and a higher SR. The calculator made the difference visible.

8. Building your own fantasy cricket points calculator on the 22Bet India platform

You do not need a paid tool. The 22Bet India fantasy platform's scoring matrix is published; build your own calculator in a Google Sheet with five columns: Player, Projected Runs, Projected Wickets, Projected Catches, Projected Final Points. Use SUMPRODUCT to apply the matrix in one formula. Pull projected stats from Cricbuzz, ESPNcricinfo, or the previous 5-match averages on the player page. Run the calculator 30 minutes before lock-in; sort by final projected points; captain the top, VC the second.

• Use the previous 5-match average, not the season average. Season averages smooth out the hot streak; 5-match averages capture current form. The 22Bet India fantasy platform rewards recent form heavily.
• Adjust for venue. Flat decks (Mumbai, Bengaluru) inflate batting projections by 10-15%; spinner-friendly decks (Chennai, Lucknow) inflate bowling projections by 10-15%. The calculator's projected-final-points column should reflect the venue, not a neutral venue.
• Adjust for match-up. A right-handed batsman against a left-arm spinner has a 15-20% boost in PPB on average. A tailender against a quality pacer on a green seamer is a -30% projection. Build match-up multipliers into the calculator; the 22Bet India fantasy platform does not do this for you.
• Track your calculator accuracy over 30 matches. Compare projected vs actual fantasy points each match. After 30 matches you will see where your calculator over- or under-projects. The 22Bet India fantasy platform gives you player-by-player actual points post-match; use that as the ground truth.

The fantasy cricket points calculator is a personal tool — your projections reflect your read of form, venue, and match-up. The 22Bet India fantasy platform gives you the matrix; you supply the projections. After 30 matches of disciplined calculator use, your rank distribution will tighten considerably.

9. Common calculator mistakes on 22Bet India fantasy

These mistakes are repeated often enough that they deserve their own list. Avoid them and your rank distribution will outperform 70-80% of 22Bet India fantasy players.

• Multiplying captain 2x before adding bonuses. Already covered above. Captain multiplier applies to the final tally. The most common calculator mistake and the most expensive in points.
• Ignoring fielding. A player who averages 25 runs but takes 1 catch per match is worth more than a player who averages 32 with no catches. The calculator makes fielding visible if you include it; if you skip the fielding column your projections are biased toward bigger-name batsmen.
• Not applying strike-rate / economy modifiers. A 30-ball 50 and a 50-ball 50 score the same in raw runs but very differently in fantasy points. The calculator MUST include the SR and economy modifier columns; without them you are projecting on runs only.
• Forgetting the duck penalty. A batsman dismissed for 0 in a T20 loses 2 fantasy points plus the strike-rate penalty (because 0 off any balls is SR 0, below 50, -6 points). That is -8 total. If your calculator does not code the duck penalty, you will over-project low-order batsmen.
• Double-counting all-rounder points. A player who bats AND bowls accumulates batting AND bowling points independently. The calculator sums both; some platforms cap the all-rounder points, but the 22Bet India fantasy matrix does not.
• Using season averages instead of 5-match rolling averages. Already covered. Season averages smooth out form; 5-match averages capture it.

The fantasy cricket points calculator is not a magic crystal ball — it is a discipline tool. It forces you to apply the matrix consistently so that your captain decision is driven by numbers, not by gut feel or player reputation. The 22Bet India fantasy platform rewards consistency; the calculator is how you build that consistency.

For more granular strategy on team selection, captain math, and venue frameworks across the IPL 2026 window, see our full 22Bet India tools hub and the related fantasy cricket breakdown.