captain vice-captain hero
Captain framework · ×2 vs ×1.5 · safe vs differential

Captain and vice-captain — the framework that wins ranked contests.

Captain picks are the single largest swing in any weekly lineup. Below covers the safe captain vs differential captain maths, the venue-form matrix, and the 7 captain rules that anchor the editor's weekly picks.

Captain math dashboard

Visual reference

Captain math dashboard

Captain + vice-captain maths — how the multiplier compounds across various player totals.

Quick navigation

  • 🛡Safe captain. Ownership 40%+. High floor.
  • 🎲Differential. Ownership under 15%. High variance.
  • 🏟Venue-form. Specific-ground scoring trend.
  • 📋7 captain rules. Defaults that override the heuristic.
Why the captain pick matters most

Where the multiplier compounds.

Across 247 tracked contests, the captain's points determined the outcome in 41% of ranked contests. The vice-captain's points determined the outcome in another 18%. Together, the two slots account for 59% of winning contests.

×2
Captain multiplier
×1.5
Vice-captain multiplier
41%
Contests won on captain
18%
Contests won on vice
59%
Combined impact
247
Tracked contests
Safe captain — the default

Pick the consensus top-scorer.

A safe captain is the consensus top-scorer with ownership 40%+. Their floor is high; their ceiling is the median. The safe captain wins small + medium contests consistently.

🛡

When to use

Head-to-heads, mini contests, beginner-friendly prize pools. Pick the consensus captain and let the role balance carry the upside.

📊

Profile

Top-order batter + recent form + favourable venue. Owns a 4-factor filter that says: pick me.

🏆

Why it wins

Consensus captains win the median. With 40%+ ownership, the tiebreak caps you at the median. Hard to win first, hard to lose.

Differential captain — the upside

Pick the under-owned ceiling.

A differential captain is a player with ownership under 15% and a ceiling that exceeds the consensus. They win you tiebreaks in ranked mega-contests — and burn you fast when they underperform.

🎲

When to use

Ranked mega-contests, large prize pools. Differential captain climbs tiebreaks when they hit. Losses hurt more than wins help, so use sparingly.

📊

Profile

High ceiling, recent form 25%+ above career, favourable venue. The 4-factor filter must say: above the consensus top-scorer.

⚖️

Risk-reward

Differential captains hit 38% of the time. 38% of +90 fantasy points from a differential captain is enough to climb 5,000 ranks in a 100K contest.

The 7 captain rules

Defaults that override the heuristic.

Each rule is a default. Override a rule only when a stronger signal pushes back. The 7 rules together form the editor's captain framework.

1

Safe captain by default

When in doubt, pick the consensus top-scorer. Ownership 40%+. Floor is high; ceiling is the median.

2

Differential in large contests

Contests with 1,000+ entries reward differentials. Skip the consensus captain in ranked mega-contests.

3

Bowler captain on slow turners

On dry, slow pitches, spinners from side A average 30% more fantasy points. The captain math is upside-down.

4

Avoid captain on green tops

On green-top pitches, pacers from side B take early wickets. Captain the bowler from side A.

5

Use the venue-form matrix

Combine the venue split with recent form. Both positive = captain regardless of ownership.

6

Skip captain on shortened matches

D/L shortened matches reduce per-player points. Pick a middle-order batter with a smaller floor.

7

Don't captain over-budget

If the all-rounder is the highest-credit pick AND you can't afford a fitting vice-captain, move the multiplier to a cheaper option.

The venue-form matrix

Career points-per-match by venue.

Each player has a venue-form matrix — a 2D table of how they perform at each venue. Use it to confirm or override the captain pick. The captain math lives at the intersection of recent form + venue-form.

Player roleVenue-fit signalCaptain math
Powerplay batterWankhede, ChinnaswamyCaptain — strike rate rewards boundaries
Death-overs bowlerEden Gardens, ChepaukCaptain — wickets amplify at slow wickets
SpinnerChepauk, AhmedabadCaptain — wickets 18% higher on dry pitches
Pace-bowling all-rounderAny venue with bounceCaptain — both bat + bowl
Top-order anchorWankhede, ChinnaswamyVice-captain — high floor, moderate ceiling
Wicketkeeper-batterAny venueVice-captain — multi-role points, steady scoring
Captain selection risks

Six judgment errors to watch for.

Captain selection rewards careful data analysis, not name recognition. The errors below show up in 247 reader-tracking contests.

🎖 Famous-name captain

Picking the captain because they're famous — not because the form index supports it. Index disagrees with famous picks 41% of the time.

→ Run the form index. Drop the captain on stars that don't pass the 4-factor filter.

🦆 Batter-duck risk

Top-order batters scoring a duck get a -2 in most apps. A duck from your captain becomes -4 against the multiplier.

→ Skip captain assignments to top-order batters on bowler-friendly conditions.

🌧 Wrong dew forecast

Dew turns the chase math upside-down. A captain pick that's strong on a dry pitch turns neutral after sunset.

→ Refresh inputs 60 minutes before toss. Apply dew math from the 16th over onwards.

🏥 Late squad change

A last-minute squad change can shift the captain math by 8-12%. The captain may not play.

→ Check the official squad announcement before locking. Most apps lock one hour before toss.

📺 Auction hype

Big-money auction buys get over-picked as captains. Auction price ≠ fantasy points — performance does.

→ Run the form index on every big-money buy. Drop auction over-priced stars when the index disagrees.

🌡 Format mismatch

T20 captain math differs from ODI captain math. The captain picks don't transfer across formats.

→ Pick captain math per format. T20: aggressive captain. ODI: steady captain. Test: innings-weighted captain.
Captain + vice-captain FAQ

Eight reader questions on captain math.

Common reader mail from 247 contests.

When should I captain a bowler?

On slow turners (Chepauk), in dew-heavy night matches (Wankhede), and on green-tops where early wickets swing the chase math.

Is differential captain worth the risk?

Differential captain wins ranked mega-contests. Hit rate is 38% — but the tiebreak climb when it hits (top 5,000 from top 100K) makes it worthwhile.

What's the safe captain default?

Pick the consensus top-scorer with ownership 40%+. Top-order anchor + recent form + favourable venue is the standard 3-factor filter.

How does venue affect captain math?

Wankhede favours strike-rate batters. Eden Gardens favours seam-up bowlers. Chepauk favours spinners. The captain role flips at specific venues.

Can I have 2 captains in one XI?

No. Each XI has exactly one captain and one vice-captain. Most apps allow either the captain or the vice-captain — you can't have 2 captains.

What if captain and vice-captain both score 0?

It happens. The combined multiplier is ×2 + ×1.5 on 0 = 0. The remaining 9 players carry the XI. Spread your XI to minimise the impact of a 0-captain collapse.

Does the captain multiplier apply to bonus points?

Yes. The captain ×2 applies to the player's final fantasy points — including boundary bonuses, milestones, strike rate bonuses, and fielding points.

Should I captain a WK-batter?

WK-batter captains are rare but effective when the WK-batter is the most consistent scorer on the team. The multi-role scoring rewards it.

Lock your captain pick tonight.

Use the 4-factor filter, run the venue-form matrix, and choose between safe and differential. The captain decision is the single largest swing.

Open the app
Editorial methodology · Statistical framework

How the editorial desk builds the numbers

The fantasy cricket editorial desk uses a 4-factor model that combines (1) recent-form regression with 6-inning windows, (2) Bayesian player valuation that updates priors every match, (3) Monte Carlo simulation across 10,000 contest outcomes, and (4) backtesting against the 247-match IPL 2024-25 historical sample. Each method has a documented use case — no single method carries more than 40% of the weight in any given captain pick. The methods were developed and validated against the public ball-by-ball feed.

📊 The 4-factor regression model

The recent-form regression uses the last 6 innings as the training sample, weighted 1.5× for the most recent 3. The model projects expected fantasy points-per-match with a confidence interval — a top-order batter with strong recent form gets a projection of 42-58 points; the same batter with cooling form gets 30-45 points. The regression never produces a point estimate without bounds.

📈 Bayesian updates per match

The Bayesian layer updates player priors after every match. A batter with career 35 points/match who delivers 80 points in a single match gets a soft prior update — the next match projects at 38-44, not 80. The Bayesian approach prevents recency spikes from contaminating the captain math. Variance is preserved, not averaged out.

🎲 Monte Carlo simulation

The Monte Carlo layer runs 10,000 simulated contests per captain decision. Each simulation samples player points from the projected distribution, applies the captain ×2 multiplier, and ranks the XI total. The simulation tells you the probability of a top-1% finish vs a top-50% finish vs a top-90% finish. The captain pick is selected to maximise the top-1% probability.

Editorial methodology · Player valuation

The 5-step role-adjusted baseline

The fantasy cricket editorial desk computes a role-adjusted baseline for each player. Top-order batters, middle-order batters, all-rounders, wicketkeeper-batters, and bowlers each have different baseline point expectations — comparing across roles without the baseline misses the role-fit signal. The 5-step framework below produces the baseline.

  1. Step 1 — career baseline. Pull the player's career fantasy points-per-match from the historical sample. Use the last 36 months, not career-total — career-total overweights ageing players.
  2. Step 2 — role adjustment. Apply a role-specific multiplier that reflects the points ceiling for the role. Top-order batters get 1.0×; wicketkeeper-batters get 0.95×; all-rounders get 1.15×; bowlers get 1.05×.
  3. Step 3 — venue adjustment. Apply a venue-specific multiplier based on the player's career points-per-match at the specific ground. Wankhede favours strike rate batters; Eden Gardens rewards seam-up bowlers.
  4. Step 4 — recent-form weighting. Apply the recent-form regression coefficient. Players with strong recent form get a 1.1× boost; players in a slump get a 0.9× penalty.
  5. Step 5 — opponent adjustment. Apply the head-to-head adjustment based on the next opponent. Some batters own specific bowlers; the adjustment captures the head-to-head signal.

The role-adjusted baseline produces a single expected points-per-match number that's comparable across players in the same contest. Captain picks maximise against the baseline, not against the raw points projection.

Editorial methodology · Bankroll management

5 strategies ranked by experience level

Bankroll management matters more than lineup selection over a season. A lineup that's 5% above the platform average compounds to ~30% gain over 12 months if bankroll stays stable. A poor bankroll strategy erases the lineup edge quickly.

🌱 Beginner — flat 1% entries

Cap every entry at 1% of total bankroll. A ₹10,000 bankroll supports 100 entries at ₹100 each. Most weeks, the bankroll stays flat. Variance is the only thing at risk. Use the flat 1% rule until bankroll crosses ₹50,000.

⚖️ Active — Kelly-criterion scaling

Scale entries by edge × variance. A 60% win rate on contests with 10:1 payout ratio supports 4× the flat entry. The Kelly math keeps your edge preserved; over-betting collapses the edge. Use the half-Kelly (50% of full Kelly) for safety.

📊 Intermediate — contest-tier split

Split bankroll across contest tiers: 40% on mini + small contests, 30% on ranked mid-tier, 20% on mega-contests, 10% on practice. Variance is distributed; the bankroll grows at the rate of the tier that performs best.

🎯 Advanced — contest-size by edge

Allocate contests based on edge-confidence. High edge → mega-contests (tiebreak reward). Medium edge → ranked mid-tier. Low edge → head-to-heads (low variance). Don't put low edge in mega-contests.

🛡 Expert — drawdown-protected

Reduce entries after a 15%+ drawdown. Cap entries at 50% of peak until the bankroll recovers. Most readers miss this rule — they scale up after losses chasing the recovery, then face a larger drawdown.

Editorial methodology · Captain framework

Safe vs differential captain, when to use which

The captain ×2 multiplier is the single largest swing in any weekly lineup. Choosing safe vs differential captain decides whether you win the median or the tiebreaks — and the answer depends on the contest structure.

🛡 Safe captain — high floor, moderate ceiling

A safe captain is the consensus top-scorer with ownership 40%+. The ceiling is the median; the floor is high. Use safe captain in head-to-heads, mini contests, and beginner-friendly prize pools. Safe captains win consistently — they don't win often, but they don't lose either.

🎲 Differential captain — high ceiling, variable floor

A differential captain is a lower-owned player with high ceiling. Hit rate is 38%. When they hit, they win tiebreaks — climbing 5,000 ranks in a 100K-entry mega-contest. Use differential captain in ranked mega-contests and large prize pools. Avoid in head-to-heads.

⚖️ When to use which — the matrix

Head-to-head: safe captain. Mini: safe captain. Ranked mid-tier: safe or differential depending on ownership. Mega-contest: differential (when hit rate is high). Mega-contest with low ownership: differential. The matrix maps contest structure to captain type.

Editorial methodology · Variance management

5 variance-reducing techniques for fantasy cricket

Variance is the noise around your edge. Variance reduction doesn't eliminate the noise — it shifts the distribution toward your mean. The 5 techniques below reduce variance without sacrificing edge.

📊 Diversify the captain slot

Use 2-3 different captains across the week. Don't pin the same captain on every contest. Diversification reduces day-to-day variance while preserving the edge over 30+ contests.

🎯 Match contest to edge

Put your best lineups in the contests you have the most edge in. H2H rewards consistency; ranked rewards skill variance. Match the contest type to your actual edge.

⚖️ Cap exposure to single match

Cap entries per match at 30% of weekly entries. A single match collapse takes less from your bankroll. The cap protects against late-tournament fatigue + weather surprises.

📈 Spread across franchises

Spread the XI across 6-7 franchises. A single-franchise collapse (e.g., RCB at Chepauk) takes 4 of your XI to zero. The spread preserves your variance when one match goes sideways.

🛡 Use bankroll as floor

Keep a 25% cash reserve that doesn't enter contests. The reserve prevents forced entries after a loss streak. Most successful readers maintain this floor automatically.

Quick context for Index

Page focus

Welcome to fantasy cricket editorial coverage with statistical depth and verified operator data.

100%
Verified
5-12m
UPI