Fantasy cricket on myteam11, in one read
A category overview for readers who searched for fantasy cricket and arrived on myteam11. What a contest is, how the credit cap and captain multiplier work, and where to start.
What a fantasy cricket contest is
A fantasy cricket contest is a points competition built from a real match. You pick 11 players from the two teams playing the match, fit them under a 100-credit cap, name a captain (2x) and a vice-captain (1.5x), and lock the team before the toss. Points are scored per /points-system/; the highest total wins the contest, scaled by the format on /contest-types/.
Where to start
Install the app from /download/
The verified APK and the iOS TestFlight path.
Read the beginner walk-through on /how-to-play/
The five steps from install to first XI.
Read the scoring reference on /points-system/
Batting, bowling, fielding tables, captain multiplier.
Pick a captain by the 50/30/20 weight
From /captain-picks/.
Enter a Practice contest first
Free, no cash payout, full scoring flow.
The rules that bind every contest
- 11 players, 100-credit cap
- 1 WK, 1 to 4 BAT, 1 to 3 AR, 3 to 6 BOWL
- Captain 2x, vice-captain 1.5x
- Lock before the toss; no late changes
- 18+ and not in the seven restricted states. See /is-legal/
The deeper hubs
- /how-to-play/, the five-step walk-through
- /points-system/, the scoring tables
- /captain-picks/, the captain decision matrix
- /contest-types/, the four contest formats
- /beginner-guide/, the ordered beginner path
- /fantasy-tips/, the tips catalogue
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 four canonical guides, and how they fit together
Fantasy cricket on this domain is organised around four canonical guides: how to play, points system, captain picks, and contest types. Each guide has a specific decision it serves; the four together cover the full path from install to settled contest.
/how-to-play/ is the beginner walk-through. It covers the five steps from install to first team and explains the captain multiplier in plain language. New accounts benefit from reading it first; experienced players can skip to the points system and the captain picks pages.
/points-system/ is the scoring reference. It is the canonical source for batting, bowling, and fielding tables. Other pages link to it rather than restating numbers; if a scoring figure appears anywhere else on myteam11play.com, the figure listed at /points-system/ is the one to trust.
/captain-picks/ is the captain decision framework. It covers form, surface, and matchup in that order, and the obvious cases where all three inputs agree. The mega contest strategy page extends the framework with captain-spread and team-differentiation rules for large-field contests.
/contest-types/ is the format reference. It covers Practice, Head-to-Head, Mega, and Beginner, with the bankroll-percentage rule for choosing between formats. The mega contest strategy page extends it with the captain-spread rule.
What remains stable across all four guides: the seven-state restriction list, the 18+ rule, the captain (2x) and vice-captain (1.5x) multipliers, and the salary cap of 100 credits. Those four are the durable markers; the rest is implementation detail that can shift between seasons.
Editorial methodology for the fantasy cricket desk
myteam11play.com is an editorial team, not an operator. The fantasy cricket guides on myteam11play.com are written from a test account plus public match data, not from insider access to the myteam11 product team. The methodology is the same on every page: name the source, name the verification date, and do not invent a number that the live app cannot back up.
For scoring claims, the source is the in-app scoring table on /points-system/, cross-referenced against the public Dream11 and MPL published tables as a sanity check. Where the myteam11 table differs from the public comparators, the in-app value is the canonical source and the difference is noted in the prose. If the in-app scoring value changes between releases, the fantasy-cricket page notes the change and the date observed.
For contest mechanics, the source is the in-app Contest Rules screen inside the Help tab. We do not interview the product team, does not paraphrase customer care responses, and does not draw inferences from screenshots of other users' accounts. When a number is not verifiable inside the live app, the fantasy-cricket methodology says it is not verifiable rather than guess.
For state eligibility, the source is the Public Gambling Act 1867, the state amendments, the most recent High Court rulings on fantasy as a game of skill, and the in-app sign-up flow that enforces the seven-state list at registration and at first deposit. The state list page at /is-legal/ is the canonical reference; the fantasy-cricket reference links to the canonical reference rather than restating it.
For payout and speed claims, the source is the test account, which recorded eight contests across three match days on a single Android device. The 18-second settlement figure is the median, not the best case. We do not call the figure record-breaking because it has not benchmarked every other fantasy app.
For who it suits, our editorial verdict is on /review/. The fantasy cricket category overview below is the entry point; it routes to the four guide pages above. New readers should read in order: how to play, points system, captain picks, contest types. Returning readers can land on any of the four. The deeper pages are self-contained but cross-link to each other where the topic overlaps.
Update cadence: fantasy-cricket reference fields get a fresh review whenever the in-app scoring values change, a new tournament format is verified, the seven-state list changes, or the fantasy-cricket guide library ships a new tier page. The review date is in the footer of every page on myteam11play.com.
What we does not publish
The fantasy cricket category overview does not publish a player ranking, does not publish a daily fantasy cricket lineup, and does not publish a "best fantasy app in India" claim. We rank zero products. We predict zero matches. We publish references the reader can reproduce in the in-app player picker.
We do not publish a captain pick that the in-app player picker cannot produce. We do not publish a probability figure that the underlying match data does not support. We do not publish a payout figure that the in-app Contest Rules screen does not surface.
Our fantasy-cricket desk's role is the editorial coverage. The product brand's role is the operational coverage. The two roles are separate; our desk does not overlap with the product brand's customer support, payment processing, or KYC verification. The verified entry route is at /app/.
How to verify the fantasy cricket overview yourself
Open the myteam11 app and navigate to the player picker. The credit counter should show 100. The role picker should show 1 wicketkeeper, 1-4 batters, 1-3 all-rounders, 3-6 bowlers. The captain slot should show a 2x multiplier. The vice-captain slot should show a 1.5x multiplier.
For the credit cap, the in-app player picker should block any XI that exceeds the 100-credit cap. The credit cap is the canonical reference; this record links to the in-app player picker rather than restating the credit cap.
For the role limits, the in-app role picker should enforce the role limits. The role limits are the canonical reference; this record links to the in-app role picker rather than restating the role limits.
For the captain multiplier, the in-app scoring table should show a 2x multiplier on the captain slot. The 2x multiplier is the canonical reference; this record links to the in-app scoring table rather than restating the multiplier.
For the vice-captain multiplier, the in-app scoring table should show a 1.5x multiplier on the vice-captain slot. The 1.5x multiplier is the canonical reference; this record links to the in-app scoring table rather than restating the multiplier.
For what to do if the in-app values contradict the record's values, the answer is the in-app values are the canonical reference. The record is updated next time our desk reviews the values; the reader can verify the values inside the in-app player picker at any time.