ODI World Cup fantasy on myteam11, fixture by fixture

Schedule (next 7 days)

Captain-pick candidates by venue

• Venue 1 (balanced): top-order anchor, seam-bowling all-rounder
• Venue 2 (slow turner): wrist-spinner, top-order batter who plays spin
• Venue 3 (flat track): top-order anchor, middle-order accelerator

Pitch reports per ground

See /pitch-report/ for the live read on each venue. ODI scoring thresholds are slightly more lenient than T20; the table on /points-system/ applies with the ODI cut-offs.

Latest fixture note

The latest editorial note is published on . Player-watch items live on .

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.

The /t20-world-cup/ hub is the parallel read for the ICC T20 World Cup. The /ipl-2026/ hub is the IPL read.

Fixtures, captain picks, and the rules of the tournament

The ODI World Cup is a 50-over tournament with squad sizes of 15 and a league-stage format followed by knockouts. The fantasy captain picks on /captain-picks/ follow the same three-input rule, with the surface reads on /pitch-report/ weighted heavier in ODI cricket because the format rewards patience over aggression.

ODI captain picks reward batters who can build an innings across the powerplay, the middle overs, and the death. The top-order batter with three of the last four fifties is the obvious captain on a flat surface; the middle-order batter with a strong record against spin is the differential captain on a turning surface.

ODI bowler captain picks are rare but possible. A pace bowler on a green surface with a strong new-ball record can captain a low-scoring fixture; the captain pick on a high-scoring chase is almost always a batter. The differential captain on a turning surface can be a spinner with a strong middle-overs record.

Fixture density matters in ODI World Cup fantasy. Back-to-back fixtures compress the form window; the last-five-match form average is more reliable than the last-five-innings form average in a tournament context. The form measure on /player-stats/ uses matches, not innings, which is the right unit for ODI fantasy.

The team news on /team-news/ tracks squad announcements, injury updates, and last-minute changes for the ODI World Cup. The pitch report on /pitch-report/ tracks the surface and the dew expectation at each named venue.

What remains stable across the ODI World Cup: the seven-state restriction list for paid entry, the 100-credit salary cap, the captain (2x) and vice-captain (1.5x) multipliers, and the KYC trigger at first withdrawal. Those four rules apply to every fixture of the tournament; the captain pick framework is the variable that shifts between fixtures.

Editorial methodology for the ODI World Cup hub

The ODI World Cup hub is a tournament landing page. The fixture list, the captain pick candidates, and the pitch reports are verified against the in-app schedule and the in-app credit values once the tournament begins. The methodology is the same as every other page on myteam11play.com: name the source, name the verification date, and do not invent a number.

For fixtures, the source is the ICC's published ODI World Cup schedule, cross-referenced against the in-app transmission of the same fixtures. The desk does not project group-stage stage-of-elimination; the actual standings are visible in-app and this guide links to the in-app schedule rather than re-publishing it.

For captain picks, the source is the in-app credit value plus the last-five-match fantasy average, plus the pitch report for the venue. The captain-pick decision matrix on /captain-picks/ is the canonical reference; the ODI World Cup hub applies the matrix to the named tournament rather than reinventing it.

For pitch reports, the source is the venue's most recent ODI result plus the named broadcaster's pre-match pitch note. The /pitch-report/ page is the canonical reference; this hub applies the framework to the tournament's named venues.

For why the ODI format matters for fantasy, the answer is the longer innings. In an ODI, a top-order batter who faces 30+ balls has more time to score boundary points than in a T20. The 50-over format favours the patient accumulator; the 20-over format favours the boundary hitter. The desk reflects this in the captain picks and the role distribution rather than treating every match as the same.

For team news, the source is the squad announcement plus the in-app likely-XI status. The /team-news/ page is the canonical reference; this hub links to it rather than re-publishing squad updates.

Update cadence: this guide is reviewed weekly during the tournament, on the day of every team announcement, and on the day the tournament schedule is finalized. The review date is in the footer of every page in this guide.

What this desk does not publish

The ODI World Cup hub does not publish a stage-of-elimination projection, does not publish a tournament winner prediction, and does not publish a "must-pick" player for the upcoming match. The desk ranks zero teams. The desk predicts zero matches. The desk publishes references the reader can reproduce in the in-app player picker.

The desk does not publish a fixture result that the named broadcaster has not published. The desk does not publish a player-pool claim that the in-app player picker does not support. The desk does not publish a captain-pick ranking that the in-app leaderboard does not surface.

The desk's role is the editorial coverage. The ICC's role is the operational coverage. The two roles are separate; the desk does not overlap with the ICC's official tournament schedule, the broadcaster's match coverage, or the in-app live scoring. The desk waits for the in-app schedule to update.

How to verify the ODI World Cup hub yourself

Open the myteam11 app and navigate to the schedule. The schedule should show the ICC ODI World Cup fixtures. Compare the fixtures below with the in-app schedule; the fixtures should match our reading.

For the upcoming fixtures, the in-app schedule should show the next fixture, the venue, and the start time. The fixture below should match the in-app schedule. The reader can verify the fixture inside the in-app schedule.

For the captain picks, the in-app player picker should show the credit value and the recent-form average for the named captain. The captain pick below should be reproducible inside the in-app player picker. The reader can verify the captain pick inside the in-app player picker.

For the pitch reports, the named broadcaster should have a pre-match pitch note for the fixture. The pitch report below should be the named broadcaster's pitch note. The reader can verify the pitch report by re-checking the named broadcaster's pre-match coverage.

For the team news, the in-app squad list should be the canonical reference. The team news below should match the in-app squad list. The reader can verify the team news inside the in-app squad list.

For what to do if the in-app schedule contradicts our fixture list, the answer is the in-app schedule is the canonical reference. We update it next time we review the fixtures; the reader can verify the fixtures inside the in-app schedule at any time.