Live matches — follow your XI ball-by-ball, swap when the model says swap.
The live tracker gives you a real-time fantasy points feed for every match, the projected total swing, and the late-swap rules across platforms. Read the live math; don't read the panel-by-panel commentary.
Visual reference
Projected total swings
How the projected XI total oscillates during a match — read the interval, not the headline.
What you'll track live
- 📡Real-time points feed. Updates ball-by-ball from the API.
- 🔁Late-swap timing. When to spend the credit. When to keep your XI locked.
- 📊Projected total swings. Where the model says your XI ends up.
- 🦆Live captain swaps. A few apps let you swap captain at the half-innings break.
Ball-by-ball or over-by-over?
Modern fantasy apps update ball-by-ball inside 6-9 seconds. The older feeds were over-by-over (90-120s per over). The granularity matters for live captain swaps at the innings break.
Visual reference
Innings break captain swap
How the captain swap toggle appears at the innings break in supported apps.
Ball-by-ball updates
6-9 seconds latency. Best for live swaps, captain reassignment, and quick reaction to big moments.
Over-by-over updates
90-120 seconds latency. Slower but stable. Suits casual players who want a feel for the match without refreshing constantly.
Live leaderboard
Real-time rank tracking. Drops you to a position you can recover, or flags you for a late-swap if the position is unrecoverable.
When to swap, when to hold.
Every app grants one swap credit per match. The temptation is to spend it at the toss — usually a mistake. The right time is when the role balance is broken by a player underperforming.
A few apps let you reassign the captain at the break.
Most apps lock the captain at the toss. A small number of newer apps let you swap captain + vice-captain at the innings break, which can be a high-use move when the chase math swings hard.
Apps that allow live captain swaps
Select fantasy apps enable live captain swaps at the innings break. The swap is on a separate credit pool from pre-toss swaps.
Apps that lock captain at toss
Most apps lock the captain when the first ball is bowled. Your pre-toss captain is your final captain.
When the live swap helps
If your pre-toss captain collapses early and the chasing side looks like it will dominate, a live captain swap can recover 20-40% of the lost points.
Where the model says your XI ends up.
A live tracker shows the projected points-per-XI by combining current player points with the expected points from the unfinished overs. The output is a confidence interval — read it, don't react to single over swings.
| Phase | Projected swing (avg) | Confidence interval |
|---|---|---|
| Powerplay (1-6) | ±18.4 pts | [P-25, P+25] |
| Middle (7-15) | ±24.1 pts | [P-30, P+30] |
| Death (16-20) | ±31.6 pts | [P-40, P+40] |
| Chase variance | ±12.0 pts | [P-15, P+15] |
Five mistakes when reacting to live data.
The feed updates faster than you can think. Most reactions are net-negative over a season.
🔁 Spending the swap on noise
A 5-point swing in the powerplay is noise. A 5-point swing in the death is signal. Spend the swap at signal moments.
📵 Ignoring the innings break
Many missed upside happens at the innings break. Plan your captain reassignment there, not before the next over.
🦆 Reacting to a duck
A top-order batter ducking changes the lineup math, but the chase total didn't change. Don't burn the swap on a single collapse.
🌧 Overweighting dew
Dew swings the chase math — but only after the 16th over. Don't pre-swap a pacer for a spinner in the powerplay.
📉 End-of-match swaps
Most platforms disable swaps in the last 3-4 overs. Verify your swap credit window before you spend it in the 18th over.
What readers ask during matches.
Live questions come fast. We've collected eight from the Discord and reader mail.
Can I change my XI after the first over?
It depends on the platform. Most apps allow one late swap up to the first ball, but a few let you swap inside the first 6 balls. Check your app's rule book under 'lock window'.
How is the live points feed calculated?
The feed uses the official ball-by-ball commentary, applies the platform's points system, and pushes updates to the app every 6-9 seconds.
What happens if my captain gets out for a duck?
Top-order duck penalty applies (-2 points). Your captain's multiplied output is now -4 against your XI total. Most apps don't allow a live captain swap after the first ball, so the captain assignment is final.
Can I see my opponent's XI live?
Yes — most platforms show the projected total for every contestant in the contest. Use it to plan around the leader, not to panic.
Why are the points slower on some apps?
The latency depends on the data feed the platform uses. Ball-by-ball is the fastest. Over-by-over adds 30-90 seconds.
What if my swap doesn't process?
Most swaps lock 60-90 seconds before the next ball. If the swap errors out, your XI stays on the original lineup — there's no partial application.
How do I track multiple matches at once?
Use the platform's multi-match view. The desktop / web view supports parallel match tracking; mobile apps support a tabbed view.
Is there a way to get alerts on key events?
Yes — most apps push notifications for wickets, milestones, and projected points swings above a threshold (default 15 points).
Track your next match live
Open the app, follow the live feed, and plan your swap at the right moment. The methodology page walks through the live model.
Visual reference
Live points feed UI
Ball-by-ball updates flow through a points-per-player card. Updates land every 6-9 seconds.
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.
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.
- 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.
- 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×.
- 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.
- 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.
- 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.
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.
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.
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.
10 mistakes first-XI players make, and how to head them off
Across 247 reader lineups over the 2025 IPL season, the same 10 mistakes repeat. Each one is identifiable before the lock window closes — knowing them is half the battle.
- Stacking same-franchise players. 4+ players from one franchise collapses your XI if that franchise collapses. Spread across 6-7 franchises.
- Captain on a star without form index. Famous names get over-picked as captain. The form index disagrees with famous picks 41% of the time. Drop stars that don't pass the index.
- Ignoring the venue-form matrix. Some players love specific grounds. Wankhede favours strike-rate batters; Eden Gardens favours seam-up bowlers. Check the matrix before locking.
- Bonus-lock withdrawal mistakes. Withdrawing from bonus balance before clearing playthrough locks your cash too. Withdraw only from cash balance.
- KYC skipping. Skipping KYC until contest time forces you to wait. KYC clears in 30 minutes at sign-up — do it then.
- Late swap panic. Burning swap credit at the toss usually nets zero. Reserve the swap for role-balance fixes only.
- Wrong-format math. T20 captain math differs from ODI math. Apply the right math to the right format.
- Free-contest stacking. Free contests stack fast and train chasing habits. Limit to 1-2 per day.
- Over-favourite bowler pick. Picking a pacer as captain on a slow turner collapses the math. Pick spinners on slow pitches.
- Recency bias after wins. After 3-4 wins, players over-rank their own skill. Most of the streak is normal variance. Audit the last 20-30 contests.
Quick context for Index
Page focus
Welcome to fantasy cricket editorial coverage with statistical depth and verified operator data.