Build your first myteam11 XI in five steps

The five steps, in the order you actually use them

1. Install the verified APK

   The walk-through on /download/ covers Android and iOS. Sideload once, revoke the toggle, and the next install is one tap.

2. Pick the next match

   The home tab shows the next 24 hours of fixtures. Pick a match where you have at least one strong pitch read from /pitch-report/.

3. Build the XI under 100 credits

   Role limits: 1 WK, 1 to 4 BAT, 1 to 3 AR, 3 to 6 BOWL. Total credits must not exceed 100. The captain costs the same credit as a regular pick; the multiplier applies to the points total.

4. Pick captain (2x) and vice-captain (1.5x)

   Pick the player you expect to score the most fantasy points in this match as captain. Pick the second-best as vice-captain. See /captain-picks/ for the decision matrix.

5. Lock the team before the toss

   Once the toss lands, the team is locked. Late changes are not possible. The match then scores per /points-system/.

The 100-credit cap, in plain language

Every player has a credit cost based on recent form and match-up. The XI as a whole must total 100 credits or fewer. The app warns you when you are over; you can drop a player or pick a cheaper alternative. The captain pick costs the same credit; the multiplier applies after the match.

Captain and vice-captain multipliers

Captain's points are doubled (2x). Vice-captain's points are multiplied by 1.5x. The same player cannot be captain and vice-captain. A captain who scores 80 fantasy points returns 160 to your team; a vice-captain at the same 80 returns 120. The 40-point gap is the difference between winning and finishing mid-table in most Head-to-Head contests.

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.

A worked example: one boundary, one wicket

Suppose your captain hits a four (boundary: +4 runs and +1 bonus = +5) and your bowler takes a wicket (+25). The captain returns 10; the bowler returns 25. Your vice-captain holds a catch (+8 catch, +4 if a stunning one = +8 to +12). The team delta is 25 to 35 fantasy points from those three events alone. Add a maiden over (+4) and a fifty bonus (+8) and the ledger crosses 50 points for the contest.

What to read next

The /points-system/ reference is the canonical scoring table. The /captain-picks/ page is the decision matrix for the two multiplier slots. The /contest-types/ reference lists the four contest formats with entry range and payout structure.

The five steps, with the questions that come up at each step

Step one is install. The verified APK is on /app/; the iOS TestFlight link is requested from the in-app Help tab. App Store and Google Play are not the install route for this brand at the last verification.

Step two is verify your phone. One-time OTP to the registered mobile number. If you change devices, the OTP goes to the new number and the wallet, KYC, and team draft travel with the verified account, not with the device.

Step three is pick a match. The home tab lists upcoming fixtures with start time, contest pool size, and entry fee tier from ₹3 to ₹10,000. New accounts default to ₹11 entry until the slider is moved.

Step four is build your XI. The salary cap is 100 credits. Role limits are 1 wicketkeeper, 1 to 4 batters, 1 to 3 all-rounders, and 3 to 6 bowlers, with team-specific variants. Pick the captain (2x) and vice-captain (1.5x) last, because the multiplier decision is the one that changes the leaderboard.

Step five is join a contest. Practice contests are free and pay no real money; they exist to rehearse. Head-to-head contests are short-field duels against one opponent. Mega contests are large-field with a top-cut payout structure. Beginner contests are entry-capped and exclude experienced players.

After the contest, withdrawals route through UPI to your verified bank account after the first KYC pass. The /wallet-kyc/ page covers the documents and the timeline. The seven-state restriction list is enforced at sign-up and at first deposit; the full table is on /is-legal/.

What remains stable across the five steps: the verified publisher name, the 100-credit salary cap, the captain (2x) and vice-captain (1.5x) multipliers, and the seven-state restriction list. Those four are the durable markers; the rest is implementation detail.

Editorial methodology for the beginner contest walk-through

The how-to-play page is a beginner contest walk-through. The desk publishes the credit salary cap, the role limits, the captain and vice-captain multipliers, and the role-by-role fantasy role description. The methodology is the same as every other page on myteam11play.com: name the source, name the verification date, and do not invent a rule.

For the credit salary cap, the source is the in-app player picker's credit counter. The desk does not publish a credit cap that the in-app player picker does not surface. The credit cap is the canonical reference; the desk does not invent a cap.

For the role limits, the source is the in-app player picker's role-picker flow. The desk does not publish a role limit that the in-app role picker does not surface. The role limits are the canonical reference; the desk does not invent a limit.

For the captain and vice-captain multipliers, the source is the in-app scoring table on /points-system/. The 2x captain and 1.5x vice-captain multipliers are the canonical reference; the desk does not project a multiplier.

For the role-by-role fantasy role description, the source is the in-app player picker's role labels. The desk does not publish a fantasy role description that the in-app player picker does not surface. The role description is the canonical reference; the desk does not invent a description.

For the worked scoring example, the source is the in-app scoring table plus a single-match player score. The desk does not publish a worked example that the in-app scoring table does not surface. The worked example is the canonical reference; the reader can re-check inside the app.

For what the desk does not do, the answer is publish a rule that the in-app player picker does not surface. The desk is a reference, not a projection. The decision to enter a contest is the reader's own work inside the app.

Update cadence: reviewed when the in-app player picker changes, when the credit salary cap changes, when the role limits change, when the captain multiplier changes, or when the vice-captain multiplier changes. The review date is in the footer of every page in this guide.

What this desk does not publish

The how-to-play page does not publish a credit salary cap that the in-app player picker does not surface. The desk does not publish a role limit that the in-app role picker does not surface. The desk does not publish a captain multiplier that the in-app scoring table does not surface.

The desk does not publish a vice-captain multiplier that the in-app scoring table does not surface. The desk does not publish a fantasy role description that the in-app player picker does not surface. The desk does not publish a worked scoring example that the in-app scoring table contradicts.

The desk's role is the editorial coverage. The reader's role is the contest-entry decision. The desk does not substitute its editorial coverage for the reader's own decision; the reader can apply the credit cap and the role limits inside the in-app player picker. The verified entry route is at /app/.