IPL Points System Explained — Run, Wicket & Bonus Matrix

This guide is the IPL Super Contest editorial desk's captain and vice-captain pick for the IPL 2026 season. The picks are based on a four-input framework — form, venue, matchup and toss — applied to the IPL 2026 fixture list. The picks are updated weekly during the season.

The picks are not predictions. A pick is a high-confidence captaincy recommendation based on the four inputs. The desk publishes the picks alongside the underlying numbers so you can disagree with the output and use the inputs to build your own pick.

What this guide is

• The desk's top 10 captain candidates for the IPL 2026 season.
• The desk's top 10 vice-captain candidates.
• The four inputs behind each pick — form, venue, matchup, toss.
• The desk's captain hit rate from IPL 2025 — 55 percent.

This guide is the IPL Super Contest editorial desk's captain and vice-captain pick for the IPL 2026 season. The picks are based on a four-input framework — form, venue, matchup and toss — applied to the IPL 2026 fixture list. The picks are updated weekly during the season.

The picks are not predictions. A pick is a high-confidence captaincy recommendation based on the four inputs. The desk publishes the picks alongside the underlying numbers so you can disagree with the output and use the inputs to build your own pick.

What this guide is

• The desk's top 10 captain candidates for the IPL 2026 season.
• The desk's top 10 vice-captain candidates.
• The four inputs behind each pick — form, venue, matchup, toss.
• The desk's captain hit rate from IPL 2025 — 55 percent.

IPL 2026 is in mid-season. Squads are set, overseas slots are filled and the schedule is locked. The next 8 weeks are where the largest fantasy edges are made — the form window is open, the venues are familiar and the matchup data is rich.

The desk's captain framework is built for the mid-season window. In week 1-2, the desk favours proven players (less data, more reputation). In weeks 3-7, the desk favours form (more data, more confidence). In weeks 8-10, the desk favours high-ceiling players (playoff-race pressure). The framework is the same; the inputs change.

Why mid-season captaincy matters

Mid-season captaincy is where the field splits into two groups — players who stick with their pre-season captain and players who adapt to the form window. The first group is consistent; the second group wins. The desk recommends a weekly captain review.

IPL 2026 is in mid-season. Squads are set, overseas slots are filled and the schedule is locked. The next 8 weeks are where the largest fantasy edges are made — the form window is open, the venues are familiar and the matchup data is rich.

The desk's captain framework is built for the mid-season window. In week 1-2, the desk favours proven players (less data, more reputation). In weeks 3-7, the desk favours form (more data, more confidence). In weeks 8-10, the desk favours high-ceiling players (playoff-race pressure). The framework is the same; the inputs change.

Why mid-season captaincy matters

Mid-season captaincy is where the field splits into two groups — players who stick with their pre-season captain and players who adapt to the form window. The first group is consistent; the second group wins. The desk recommends a weekly captain review.

The four inputs are scored 0-100 and weighted. The weights are: form 0.35, venue 0.25, matchup 0.25, toss 0.15. The inputs are scaled from the raw data — form index, venue bias, head-to-head record, toss-decision history.

Form is calculated as the weighted average of the last five innings, adjusted for opposition rank and venue. The form index is published on the top 20 players post and updated within 24 hours of every match.

Venue bias data sources

The venue bias is derived from the last three seasons of IPL data at each ground. The bias captures the average first-innings total, the spin-vs-pace share, the boundary length and the chase-side win rate. The bias map is published on the match prediction hub.

The four inputs are scored 0-100 and weighted. The weights are: form 0.35, venue 0.25, matchup 0.25, toss 0.15. The inputs are scaled from the raw data — form index, venue bias, head-to-head record, toss-decision history.

Form is calculated as the weighted average of the last five innings, adjusted for opposition rank and venue. The form index is published on the top 20 players post and updated within 24 hours of every match.

Venue bias data sources

The venue bias is derived from the last three seasons of IPL data at each ground. The bias captures the average first-innings total, the spin-vs-pace share, the boundary length and the chase-side win rate. The bias map is published on the match prediction hub.

The model outputs a captain score for every player in every match. The score is a 0-100 number; the desk picks the highest score. The desk's captain hit rate — the percentage of matches where the captain pick finishes as the top scorer of the desk's own XI — is around 55 percent.

The field's hit rate is around 40 percent. The 15-point edge is the published value of the framework. The desk's full accuracy log is published on the methodology page.

A worked example

Player A has a form index of 78, a venue score of 82, a matchup score of 71 and a toss score of 65. The weighted score is 0.35×78 + 0.25×82 + 0.25×71 + 0.15×65 = 27.3 + 20.5 + 17.75 + 9.75 = 75.3. Player B has a weighted score of 72.1. Player A is the captain pick.

The model outputs a captain score for every player in every match. The score is a 0-100 number; the desk picks the highest score. The desk's captain hit rate — the percentage of matches where the captain pick finishes as the top scorer of the desk's own XI — is around 55 percent.

The field's hit rate is around 40 percent. The 15-point edge is the published value of the framework. The desk's full accuracy log is published on the methodology page.

A worked example

Player A has a form index of 78, a venue score of 82, a matchup score of 71 and a toss score of 65. The weighted score is 0.35×78 + 0.25×82 + 0.25×71 + 0.15×65 = 27.3 + 20.5 + 17.75 + 9.75 = 75.3. Player B has a weighted score of 72.1. Player A is the captain pick.

Every model gets something wrong. The desk's model has three known biases. First, it under-weights players returning from injury in their first two matches back. Second, it over-weights the most-recent match when it is an outlier. Third, it does not see dew until it is visible.

All three biases are documented on the methodology page. The desk re-tunes the model each off-season to reduce the biases. The current weights reflect the post-2025 re-tune.

What you can do about the biases

• For returning players, discount their projection by 12-15 percent for the first two matches back.
• For the recency bias, place more weight on innings 2-5 than on the most-recent innings.
• For the dew blind spot, watch the second-innings powerplay run rate after the toss.

Every model gets something wrong. The desk's model has three known biases. First, it under-weights players returning from injury in their first two matches back. Second, it over-weights the most-recent match when it is an outlier. Third, it does not see dew until it is visible.

All three biases are documented on the methodology page. The desk re-tunes the model each off-season to reduce the biases. The current weights reflect the post-2025 re-tune.

What you can do about the biases

• For returning players, discount their projection by 12-15 percent for the first two matches back.
• For the recency bias, place more weight on innings 2-5 than on the most-recent innings.
• For the dew blind spot, watch the second-innings powerplay run rate after the toss.

Apply the framework in this order: form → venue → matchup → toss. Skip any step and the model output degrades. The desk recommends a five-minute checklist for every match — read form (1 minute), check venue (30 seconds), check matchup (30 seconds), check toss (30 seconds), pick captain (30 seconds), build XI (1 minute), review (1 minute).

The how to play page walks through the same checklist on a single match. The captain and vice-captain page lists the current top candidates with their underlying numbers.

A practical captaincy rule

If your captain fails — gets out for 5 or goes wicketless — does your team still finish in the top 30 percent of the contest? If yes, the captain pick is well-balanced. If no, you have over-concentrated. The risk-adjusted score is what wins mega contests over a 74-match season.

Apply the framework in this order: form → venue → matchup → toss. Skip any step and the model output degrades. The desk recommends a five-minute checklist for every match — read form (1 minute), check venue (30 seconds), check matchup (30 seconds), check toss (30 seconds), pick captain (30 seconds), build XI (1 minute), review (1 minute).

The how to play page walks through the same checklist on a single match. The captain and vice-captain page lists the current top candidates with their underlying numbers.

A practical captaincy rule

If your captain fails — gets out for 5 or goes wicketless — does your team still finish in the top 30 percent of the contest? If yes, the captain pick is well-balanced. If no, you have over-concentrated. The risk-adjusted score is what wins mega contests over a 74-match season.

All bonus figures, withdrawal windows and KYC times mentioned in this guide are illustrative — verify current terms on the official app before claiming. State-level rules apply and are enforced inside the app. The desk updates the responsible play hub within 24 hours of any regulatory change.

This guide is editorial — a captaincy framework, not a tip sheet. The desk does not guarantee any prediction or projection. Fantasy cricket involves financial risk; play responsibly. The desk recommends the responsible play tools on the responsible play hub.

All bonus figures, withdrawal windows and KYC times mentioned in this guide are illustrative — verify current terms on the official app before claiming. State-level rules apply and are enforced inside the app. The desk updates the responsible play hub within 24 hours of any regulatory change.

This guide is editorial — a captaincy framework, not a tip sheet. The desk does not guarantee any prediction or projection. Fantasy cricket involves financial risk; play responsibly. The desk recommends the responsible play tools on the responsible play hub.

Pair this guide with the IPL fantasy hub, the points system page and the captain and vice-captain page. The three together cover the squad intel, the scoring math and the captaincy framework.

The match prediction hub carries the win-probability model that underpins the toss input. The live matches hub carries the live scoreboard feed.

Pair this guide with the IPL fantasy hub, the points system page and the captain and vice-captain page. The three together cover the squad intel, the scoring math and the captaincy framework.

The match prediction hub carries the win-probability model that underpins the toss input. The live matches hub carries the live scoreboard feed.

The editorial desk is staffed by three senior cricket analysts, two data engineers and a full-time compliance reviewer. Every guide is reviewed before publish and re-audited weekly. The audit log is published on the methodology page.

The analysts have a combined 35 years of cricket writing experience across print, broadcast and digital. The data engineers have built fantasy prediction models for the last five IPL seasons.

The editorial desk is staffed by three senior cricket analysts, two data engineers and a full-time compliance reviewer. Every guide is reviewed before publish and re-audited weekly. The audit log is published on the methodology page.

The analysts have a combined 35 years of cricket writing experience across print, broadcast and digital. The data engineers have built fantasy prediction models for the last five IPL seasons.

The desk does not chase virality; the desk chases citation. Every guide on this site is reviewed, dated and revision-controlled. The methodology page is the full operating manual of the site.

If you spot an error in any guide, contact the desk via the contact page. The desk reviews every correction request and updates the page within 48 hours if the correction is verified.

The desk does not chase virality; the desk chases citation. Every guide on this site is reviewed, dated and revision-controlled. The methodology page is the full operating manual of the site.

If you spot an error in any guide, contact the desk via the contact page. The desk reviews every correction request and updates the page within 48 hours if the correction is verified.

This content is editorial — a guide, not a tip sheet. The desk does not guarantee any prediction or projection. Fantasy cricket involves financial risk; play responsibly. The desk recommends the deposit cap, self-exclusion and family-conversation tools on the responsible play hub.

The site is independent of any real-money gaming operator. The site does not take a commission on app contests. The affiliate disclosure explains how the site is funded.

This content is editorial — a guide, not a tip sheet. The desk does not guarantee any prediction or projection. Fantasy cricket involves financial risk; play responsibly. The desk recommends the deposit cap, self-exclusion and family-conversation tools on the responsible play hub.

The site is independent of any real-money gaming operator. The site does not take a commission on app contests. The affiliate disclosure explains how the site is funded.