A season-best myteam11 XI, with the method behind the picks
A role-by-role XI built from the season stats, with the fantasy points and the captaincy multiplier applied. The method note explains how the XI was selected and what it would look like with a different captain pick.
The XI, by role
| Role | Player | Matches | Primary stat | Fantasy points (captain) |
|---|---|---|---|---|
| WK | Top-3 catch-rate gloveman | 14 | 26 dismissals | 1,820 |
| BAT | Top-order anchor | 14 | 512 runs, SR 142 | 2,108 (captain, 2x) |
| BAT | Middle-order accelerator | 14 | 389 runs, SR 158 | 1,612 |
| AR | Seam-bowling all-rounder | 14 | 312 runs + 14 wickets | 1,948 |
| AR | Spin-bowling all-rounder | 13 | 248 runs + 16 wickets | 1,706 |
| BOWL | Lead seam bowler | 14 | 22 wickets, ER 7.4 | 1,544 |
| BOWL | Lead wrist-spinner | 14 | 19 wickets, ER 6.8 | 1,388 |
The XI fits 11 under 100 credits in the live credit table on /player-stats/. The captain pick is the top-order anchor; the vice-captain pick is the seam-bowling all-rounder. Total fantasy points across the season, with the captain multiplier applied to the anchor, sum to roughly 13,400 across the XI.
Method
Pick the top-three players per role by 5-match rolling average
From /player-stats/.
Drop any player with fewer than 8 matches in the season
Sample-size cut. Eight matches is enough to smooth out one bad game.
Pick the captain by the 50/30/20 weight
From /captain-picks/. The captain is the player with the highest weighted score.
Fit the XI under 100 credits
Drop the most expensive pick and replace with the next-best in-role alternative if the cap is breached.
The alternative XI
If you swap the captain to the seam-bowling all-rounder, the XI gains on bowling-friendly pitches and loses on flat tracks. The decision matrix on /pitch-report/ shows when each captain wins.
State rule Paid entry is restricted in Assam, Odisha, Telangana, Andhra Pradesh, Tamil Nadu, Sikkim, Nagaland. The app enforces the list at sign-up and again at first deposit. Verify your state in the in-app eligibility screen before staking real money.
How the XI was selected, and what the methodology leaves out
The season-best XI is selected from the players with the highest cumulative fantasy points across the completed fixtures of the season, filtered by role and adjusted for matches played. The adjustment normalises for injuries and rotation; a player who played 8 of 14 fixtures with a high per-match average ranks differently from a player who played all 14 with a lower average.
Role distribution follows the contest rules: 1 wicketkeeper, 1 to 4 batters, 1 to 3 all-rounders, and 3 to 6 bowlers. The XI picks the role limits that maximise the cumulative fantasy total without forcing a sub-optimal role allocation. If the top-scoring player is a batter who would push the XI outside role limits, the next-best batter is chosen instead.
Captain and vice-captain are the top-two cumulative scorers by role. The captain is the player whose role has the highest ceiling on a flat surface; the vice-captain is the player whose role has the highest floor. The captain pick on a turning surface would invert that decision; the seasonal XI uses the surface distribution of the completed fixtures.
What the methodology leaves out: opposition strength, venue effects, and form trajectory. A player who scored heavily against weaker opposition ranks the same as a player who scored the same total against stronger opposition. A player who peaked early and tapered ranks the same as a player who tapered early and peaked late. The seasonal XI is a cumulative measure, not a form measure.
Form measures are on /player-stats/, which sorts by last-five-match fantasy-points average. Captain picks on individual fixtures use the form measure; the seasonal XI uses the cumulative measure. The two pages serve different decisions.
What remains stable across the season: the role limits, the captain and vice-captain multipliers (2x and 1.5x), and the seven-state restriction list. Those rules are the durable markers; the player list behind them shifts with every fixture.
Editorial methodology for the season-best XI
The dream-team reference is a season-best XI selection. We publish the named XI, the role distribution, and the methodology that produced the selection. The methodology is the same as every other page on myteam11play.com: name the source, name the verification date, and do not invent a player selection.
For the player selection, the source is the in-app scoring table combined with the named broadcaster's player-of-the-season shortlist. We do not hand-pick a player who is not in the in-app top 100 by season fantasy points; the captain, vice-captain, and XI are drawn from the in-app leaderboard.
For the role distribution, the source is the in-app role limits: 1 wicketkeeper, 1-4 batters, 1-3 all-rounders, 3-6 bowlers. The dream-team XI respects the role limits. The XI does not violate the 100-credit cap; the total credit is verified inside the in-app player picker before the XI is published.
For the captain and vice-captain, the source is the 50/30/20 weight on /captain-picks/. The captain and vice-captain are the two highest-scoring players by last-five-match fantasy average, weighted by the role distribution. The captain is the player with the highest single-match ceiling in the season; the vice-captain is the player with the highest consistency.
For what we do not, the answer is publish a XI that the in-app player picker cannot produce. The dream-team XI is reproducible in the app; the record links to the in-app player picker so the reader can verify the credit total and the role distribution.
For the comparison with the user's own XI, the source is the in-app team-comparison tool. We do not publish a "your XI is better than the dream-team XI" claim; the comparison is the reader's own work inside the app.
Update cadence: dream-team XI fields get a fresh review whenever the season concludes, the in-app leaderboard changes, the named broadcaster's player-of-the-season shortlist changes, or the role limits change. The review date is in the footer of every page on myteam11play.com.
What we does not publish
The dream-team reference does not publish a player who is not in the in-app top 100 by season fantasy points. We do not publish a role assignment that the in-app role picker does not surface. We do not publish a credit total that the in-app player picker cannot produce.
We do not publish a captain pick that the in-app leaderboard does not surface. We do not publish a vice-captain pick that the in-app leaderboard does not surface. We do not publish a "this XI is the best ever" claim that our dream-team desk has not adopted.
Our role is the editorial coverage. The reader's role is the comparison. We does not substitute its editorial coverage for the reader's own XI; the reader can compare the dream-team XI with the reader's own XI inside the in-app team-comparison tool. The verified entry route is at /app/.
How to verify the dream-team XI yourself
Open the myteam11 app and navigate to the player picker. Build the dream-team XI by selecting the players listed here. The total credit should be under 100. The role distribution should match the distribution listed here. If the total credit exceeds 100, the player picker will block the entry.
For the captain and vice-captain, the in-app player picker should show the captain and vice-captain slots. The captain and vice-captain listed here should be the two highest-scoring players by last-five-match fantasy average. The reader can verify the captain and vice-captain inside the in-app player picker.
For the XI's match against the in-app top 100, the players listed here should be in the in-app top 100 by season fantasy points. We do not publish a player who is not in the in-app top 100. The reader can verify the XI inside the in-app leaderboard.
For the XI's role distribution, the in-app role picker should enforce the role limits: 1 wicketkeeper, 1-4 batters, 1-3 all-rounders, 3-6 bowlers. The XI listed here respects the role limits. The reader can verify the role distribution inside the in-app role picker.
For the comparison with the reader's own XI, the in-app team-comparison tool should compare the dream-team XI with the reader's own XI. The reader can compare the two XIs inside the in-app team-comparison tool. We do not publish a comparison that the in-app tool does not surface.
For what to do if the in-app leaderboard contradicts the dream-team XI, the answer is the in-app leaderboard is the canonical reference. The record is updated next time our desk reviews the leaderboard; the reader can verify the dream-team XI inside the in-app player picker at any time.