The myteam11 points system, in one printable table

Batting

Bowling

Fielding

Multipliers

• Captain: points multiplied by 2x
• Vice-captain: points multiplied by 1.5x
• The same player cannot hold both slots
• The multiplier applies after the points table, not to the credit cost

Worked example: one innings, one spell

Suppose your captain scores 60 off 38 balls with 7 fours and 2 sixes, and your bowler takes 3/28 in 4 overs with one maiden. Captain batting: 60 (runs) + 28 (boundary) + 12 (sixes) + 8 (fifty) = 108 points. Bowler: 75 (3 wickets) + 24 (LBW/bowled if all three) + 4 (maiden) + 4 (3-fer) = 107 points. Multiplied by captain: 108 × 2 = 216. Vice-captain at the bowler slot: 107 × 1.5 = 160.5. Combined: 376.5 fantasy points from those two players alone.

What changes in T20 vs ODI vs Test

The tables above apply to T20. ODI thresholds are slightly more lenient (strike-rate and economy cut-offs shift). Test matches add bonus points for sessions and innings milestones; the in-app help screen lists the exact thresholds for the current format. The decision matrix on /captain-picks/ shows how the format shifts the captain pick.

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 /how-to-play/ reference walks through one full contest using this table. The /dream-team/ page applies the table to a season-best XI.

The worked examples, and what changes between formats

The scoring system on this product follows the standard fantasy-cricket framework: one run is one point, a boundary is four runs and four points, a six is six runs and six points. The captain pick doubles the player's total; the vice-captain pick multiplies by 1.5. Fielding points (catch, stumping, run-out) add to the total; deductions (duck, run-out for non-striker) subtract.

Worked example one: a top-order batter scores 65 off 52 balls with 8 fours and 1 six. Batting points: 65 runs = 65, 8 boundaries = 32, 1 six = 6, total batting = 103. If the player is the captain, the total is 206. As vice-captain, 154.5. As neither, 103. The captain pick on a 65-run innings is the difference between a top-half finish and a top-decile finish.

Worked example two: a pace bowler returns 4 wickets for 32 runs in 4 overs with 2 maidens. Bowling points: 4 wickets = 100, 2 maidens = 8, total bowling = 108. Economy deduction below the threshold is not applied on this product; the figure 108 is the bowling total. As captain, 216. As vice-captain, 162. As neither, 108.

What changes between formats: ODI cricket rewards patience over aggression, so the dot-ball deduction is lighter and the milestone bonuses (fifty, century) are heavier. T20 cricket rewards aggression, so the boundary bonus is heavier and the dot-ball deduction is heavier. Test cricket rewards consistency, so the milestones are stacked (century, double-century) and the deductions are lighter.

Fielding points: a catch is 8 points, a stumping is 12 points, a run-out direct hit is 12 points, a run-out assist is 6 points. The wicketkeeper-batter on a turning surface can captain on fielding points alone if the bowlers are taking catches in the slips. The differential captain pick on /captain-picks/ often uses this input.

What remains stable across formats: the captain (2x) and vice-captain (1.5x) multipliers, the fielding points table, and the deductions (duck, run-out for non-striker). The batting and bowling point values shift between ODI, T20, and Test formats; the framework does not.

Editorial methodology for the scoring-reference desk

The points-system page is the canonical scoring reference for the myteam11 app. The desk publishes the batting, bowling, and fielding tables, the captain multiplier, and the deductions. The methodology is the same as every other page on myteam11play.com: name the source, name the verification date, and do not invent a point.

For the batting table, the source is the in-app scoring table inside the player picker. The desk does not publish a batting point that the in-app table does not surface. The batting point is the canonical reference; the desk does not paraphrase the table.

For the bowling table, the source is the in-app scoring table. The desk does not publish a bowling point that the in-app table does not surface. The bowling point is the canonical reference; the desk does not paraphrase the table.

For the fielding table, the source is the in-app scoring table. The desk does not publish a fielding point that the in-app table does not surface. The fielding point is the canonical reference; the desk does not paraphrase the table.

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

For what the desk does not do, the answer is publish a scoring value that the in-app scoring table does not surface. The desk is a reference, not a projection. The captain-pick decision is the reader's own work inside the app.

Update cadence: reviewed when the in-app scoring table changes, when the captain multiplier changes, when the vice-captain multiplier changes, or when a new scoring category is added. The review date is in the footer of every page in this guide.

What this desk does not publish

The points-system page does not publish a scoring value that the in-app scoring table 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 deduction that the in-app scoring table does not surface. The desk does not publish a bonus that the in-app scoring table does not surface. The desk does not publish a scoring projection that the test account has not recorded.

The desk's role is the editorial coverage. The reader's role is the captain-pick decision. The desk does not substitute its editorial coverage for the reader's own captain-pick decision; the reader can apply the scoring table inside the in-app player picker. The verified entry route is at /app/.

How to verify the scoring table yourself

Open the myteam11 app and navigate to the player picker. Tap the scoring icon next to a player. The scoring table should be visible. Compare the table below with the in-app scoring table. The values should match; if they do not, the in-app table is the canonical reference.

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 section 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 section links to the in-app scoring table rather than restating the multiplier.

For the deductions, the in-app scoring table should show the deductions for a duck and for a run-out. The deductions are the canonical reference; this section links to the in-app scoring table rather than restating the deduction.

For the bonuses, the in-app scoring table should show the bonuses for fifty, century, and five-wicket haul. The bonuses are the canonical reference; this section links to the in-app scoring table rather than restating the bonus.

For what to do if the in-app scoring table differs from this guide, the answer is the in-app scoring table is the canonical reference. The guide is updated next time we review the table; the reader can verify the table inside the in-app scoring table at any time.