Player credit, recent form, and likely XI status

The reference table

The table above is a working example; the live credit and form numbers move with every match. Treat the structure as the canonical template and refresh the values from the in-app "Player stats" tab before locking the XI.

How to read the form column

The last-5-match fantasy-points average is the rolling mean of the player's fantasy points in the last five contests. A player with a 5-match average of 80 who is yet to play this season averages 80 once they have five matches; until then, the column reads the available matches.

The likely-XI flag

The likely-XI flag is set by the writers using the latest /team-news/. A player flagged "Yes" is expected to start. A player flagged "Rotation risk" may be rested for this fixture; treat them as a vice-captain option only, not as captain. A player flagged "No" is omitted from the table.

Role limits in your XI

1 WK, 1 to 4 BAT, 1 to 3 AR, 3 to 6 BOWL. Total credits must not exceed 100. The role limits are enforced by the app at team lock.

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 /captain-picks/ page applies this shortlist to the captain decision. The /dream-team/ page applies it to a season-best XI.

How the table is sorted, and what the columns mean

The player reference table sorts by credit (the salary cap value) by default, with secondary sorts available by role, last-five-match fantasy-points average, and likely XI status. The table is the source of truth for the form input on the captain picks framework; if a figure on the table conflicts with a figure on a news article, the table wins.

Credit is the salary cap value. The credit reflects the operator's market valuation of the player at the start of the season and adjusts based on form, role, and likely XI status. A high-credit player is not necessarily a high-form player; the captain pick decision uses form, not credit. Credit is the budget constraint, not the captain pick.

Role is the contest role: wicketkeeper, batter, all-rounder, or bowler. Role limits on /how-to-play/ apply to the XI; role limits on this guide apply to the captain pick candidates. A top-order batter is a common captain pick; a lower-order batter is a differential captain pick on a chasing surface.

Last-five-match fantasy-points average is the form input. The average uses matches, not innings, so an ODI player's average covers five ODIs and a T20 player's average covers five T20s. The form average is the most useful single number for the captain pick decision; it is the input that cuts the candidate list first on /captain-picks/.

Likely XI status is the squad-availability input. A player listed as Likely is in the named squad for the next fixture; a player listed as Doubtful is in the squad but may not play; a player listed as Out is not in the squad. The status updates on the day of the fixture; the table reflects the latest status at the verification timestamp.

What remains stable across the table: the credit cap of 100 credits per XI, the role limits (1 WK, 1-4 BAT, 1-3 AR, 3-6 BOWL), and the captain (2x) and vice-captain (1.5x) multipliers. The credit of individual players and the last-five-match averages shift between fixtures; the framework does not.

Editorial methodology for the player reference desk

The player-stats page is a player reference. The desk publishes the credit, the role, the recent form, and the likely-XI status for the named players. The methodology is the same as every other page on myteam11play.com: name the source, name the verification date, and do not invent a statistic.

For the credit value, the source is the in-app transmission of the player credit. The desk does not publish a credit value that the in-app player picker does not show. If the credit value changes (an injury replacement, a player withdrawal), we note the change.

For the role, the source is the in-app role category (wicketkeeper, batter, all-rounder, bowler). The desk does not republish a role assignment that the in-app player picker does not surface. The role drives the captain-pick decision matrix on /captain-picks/.

For the recent form, the source is the in-app last-five-match fantasy average. The desk does not publish a recent-form average that the in-app player picker does not surface. The average is the median of the last-five matches, not the highest single-match score.

For the likely-XI status, the source is the in-app squad-list status (Confirmed, Likely, Doubtful). The desk does not publish a likely-XI status that the in-app squad list does not surface. The likely-XI status is the canonical reference for the captain-pick decision.

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

Update cadence: this guide is reviewed when the in-app credit values change, when the in-app role categories change, when the in-app recent-form averages change, or when the in-app likely-XI status changes. The review date is in the footer of every page in this guide.

What this desk does not publish

The player-stats page does not publish a credit value that the in-app player picker does not surface. The desk does not publish a recent-form average that the in-app player picker does not surface. The desk does not publish a likely-XI status that the in-app squad list does not surface.

The desk does not publish a player ranking that the in-app leaderboard does not surface. The desk does not publish a "must-pick player" line that the in-app player picker cannot produce. The desk does not publish a player 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 decision; the reader can re-check the credit value and the recent-form average inside the in-app player picker. The verified entry route is at /app/.

How to verify the player reference yourself

Open the myteam11 app and navigate to the player picker. Tap a player below. The in-app player picker should show the credit value, the role, the recent-form average, and the likely-XI status. Compare the values below with the in-app values; the values should match our reading.

For the credit value, the in-app player picker should show the credit value next to the player's name. The credit value is the canonical reference; this guide links to the in-app player picker rather than restating the credit value.

For the role, the in-app role picker should show the role category. The role is the canonical reference; this guide links to the in-app role picker rather than restating the role category.

For the recent-form average, the in-app player picker should show the last-five-match fantasy average. The recent-form average is the canonical reference; this guide links to the in-app player picker rather than restating the recent-form average.

For the likely-XI status, the in-app squad list should show the confirmed, likely, or doubtful status. The likely-XI status is the canonical reference; this guide links to the in-app squad list rather than restating the likely-XI status.

For what to do if the in-app values contradict our values, the answer is the in-app values are the canonical reference. We update it next time we review the values; the reader can verify the values inside the in-app player picker at any time.