Role
Where the player sits in the XI, what they are asked to do, and how that maps to fantasy points.
Every player profile follows the same seven-lens structure so you can compare names on the same axes: role, recent form, venue history, matchup reads, fitness, availability, and risk notes.
Where the player sits in the XI, what they are asked to do, and how that maps to fantasy points.
Last five to ten innings/spells with role context. Numbers without context mislead.
Multi-season read at the player's home ground and key away venues.
Historical performance against specific opposition bowlers or batters.
Injury status, workload trends, and recovery notes where reported.
National duty, franchise release windows, and rotation risk.
Format-specific or squad-specific risks that might override form.
Strike rate of 165 looks excellent until you realise the innings was on a flat deck against a part-time bowler with no field restrictions. Our form reads always include the conditions, the matchup, and the role context so the number tells you what actually happened.

Different roles reward different actions. Read the role category before looking at the player's stats so the numbers tell you something useful.
Powerplay scoring, boundary count, dot-ball minimisation. Strike rate matters more than balls faced.
Middle-overs stability, strike rotation, occasional acceleration. Balls faced matters more than strike rate.
Death-overs scoring, six-hitting, strike rotation under pressure. Highest variance role.
Batting + bowling + fielding points. Often the most weighted role in fantasy.
A bowler's role determines which fantasy points they earn. A powerplay strike bowler earns wickets differently from a death-overs yorker specialist.
New-ball wickets, swing/seam movement. Earns points through wickets and dot balls.
Economy and wickets in overs 7–15. Earns points through economy bonuses.
Final-over wickets, dot balls, boundary prevention. Earns points through wickets and economy.
Middle-overs wicket-taking, sometimes powerplay. Earns points through wickets and dot balls.
Powerplay containment, middle-overs control. Earns points through economy more than wickets.
A perfectly fitting player on paper is useless if they have been released for national duty, dropped for form, or ruled out by injury. We track availability at squad and franchise level alongside the form read.
Most fantasy readers ignore the head-to-head matchup because it takes time to compile. Our player profiles link to the relevant matchup data so you can spot the obvious captain candidates before the toss.
Batters who average above 40 against a specific bowler across at least five meetings. Strong captain signal.
Bowlers with strong records against a specific batter. Strong captain signal in bowling-heavy formats.
A left-handed batter who has struggled against left-arm spin in recent seasons is a captain-risk against a frontline left-arm spinner.
If the opposition plays three spinners, your XI should include at least one specialist batter against spin.
A profile tells you about a single player; a team profile tells you about the structure around them. Use both before your next captain call.
Our player research pulls together recent batting form, bowling economy, role-specific strike rates, opposition matchup history, venue averages, and workload data. We then translate those numbers into role categories that fantasy readers actually use — anchor, accelerator, death-overs specialist, powerplay wicket-taker, middle-overs controller — rather than abstract percentiles.
Player pages on the desk never claim certainty about a future performance. We publish scenarios, not predictions, and we always note the conditions under which a player scenario changes: dew, pitch behaviour, opposition seam/spin mix, batting order shuffling, or a workload-managed rest window.
Where we reference Come's app or contest structure, we only do so in connection with verified facts. We do not invent owner, company, or legal-status claims about Come. If a piece of information cannot be verified through public sources, we mark it as such or omit it.