Practical reading for anyone who wants to build a team, understand the rules, and verify the app before committing time or money. Every page is dated, sourced and rewritten when facts change.
These are the routes most visitors open in the first week. Each one answers a single, distinct question — verify the app, learn the rules, build a smarter team, and keep your money safe.
Source checks, package name signals, permission requests, and the safer install path on Android and iOS.
Read the app guide → 02 GameplayCredits, role limits, captain multipliers, contest types, deadlines and abandoned-match rules explained.
Read the rules → 03 ScoringRun, boundary, wicket, catch and fielding points with worked examples for batters, bowlers and all-rounders.
See the table → 04 SelectionUse a repeatable method instead of a vibe. Templates, ownership splits and post-toss pivots.
See the templates → 05 PredictionsProbable XIs, conditions, matchup notes and a clear “confirmed” vs “pending” label on every pick.
Open the index → 06 SafetyAge rules, state restrictions, deposit limits, cooling-off periods and where to find help if play stops being fun.
Review the guardrails →Use this as a pre-toss checklist. A factor only earns weight when you can point to a verified signal; the rest of the time, ignore the noise.
| Factor | Evidence to inspect | When it actually matters |
|---|---|---|
| Toss & elected innings | Verified toss update from the league broadcaster, not a tweet or a screenshot. | Always. Captain and death-over bowler choice depend on it. Re-check 15 minutes before deadline. |
| Pitch & venue | Surface history for the venue, square turnover, recent subcontinent Tests and ODIs. | When two spinners or a finger-spin all-rounder are in form. Wickets in India often slow from the 10th over. |
| Weather & DLS | Hour-by-hour forecast, humidity, and the operator's DLS policy. | Rain threats in the monsoon window. Confirm Duckworth–Lewis rules for the format before picking a bowler-heavy side. |
| Confirmed XI | Operator’s playing-XI notification or broadcaster’s announcement. | Always. Never lock a team on a probable XI after the toss. |
| Player workload | Recent matches in the calendar week, injury updates, franchise rotation. | Back-to-back fixtures, all-format schedules, return from injury. Multi-format players can be rested without warning. |
| Ownership & differentials | Contest size, prize pool, captaincy ownership split. | Large GPPs where unique picks matter more than a popular captain. Head-to-head and small leagues reward the safer captain. |
Each piece is dated, reviewed, and rewritten when the source data changes. If a fact is uncertain, the page says so in plain language.
Floor, ceiling and role certainty — a method you can reuse on every matchday, with a worked example for an India–Australia ODI.
Five-bowler, four-batter, one all-rounder, one wicketkeeper — and what to flex when conditions change.
RulesWhy the operator applies DLS to your batting points and how to pick bowlers for shortened games.
EligibilityA short map of where real-money fantasy contests are restricted, with cautious pointers to verify locally.
PracticalSymptom, likely cause, safe next step and the evidence to keep before you contact customer care.
Selection models are not predictions. They’re a way to log the evidence you used — so you can review it after the match, not just when you win.
If your captaincy choice can’t be explained in one sentence after the toss, you’re gambling on identity, not evidence. The job of a method is to make the captain pick reversible when the conditions change.
Every tile opens a curated set of pages on one subject. We keep the rail narrow on purpose — the goal is depth on the topics that change your next contest, not a list of every match.
Real-money fantasy contests are regulated in India. The rules below are not legal advice — they are the editorial guardrails this site will not cross.
Anyone can write a team. The difference between a hobby and a problem is whether you set the rules before you start. We recommend writing them down.
You must be 18 or older. Some Indian states restrict real-money contests — verify the operator’s list before you deposit.
Set a weekly cap you can afford to lose. Most operators expose this in the wallet section; if it’s hidden, that’s a signal.
Complete KYC before your first deposit. Withdraw a small amount early to confirm the route works for you.
If two sessions in a row end in frustration, take a 72-hour break. Self-exclusion tools are listed in the responsible-play guide.
Short answers. If you need a deeper read, every question points to a dedicated page.
Real-money fantasy contests are regulated state by state. Some states restrict or prohibit paid entries. The legality depends on where you live and which operator you use. See the is Fan2Play legal guide for cautious pointers and a verification checklist.
Always use the operator’s verified link, not a third-party APK mirror. The download guide explains the safer install path, the permissions to expect, and how to confirm the package name on Android.
18 or older in every state where real-money fantasy contests are permitted. The operator is required to verify age during KYC.
Each action on the field — run, boundary, wicket, catch, stumping — maps to a point value. The exact values change with format and operator. See the versioned points system page for the current table.
Yes. Account deletion is usually available in the profile or settings section. If you can’t find it, the customer-care guide explains the evidence to collect and the safest escalation path.
The operator’s terms live on the official app and on the verified web login. The about page lists the editorial policy used on this site, including how we label affiliate links and corrections.
If you’re new, start with the app verification and the beginner’s guide. If you’re returning, the latest analysis and decision table above are the best place to anchor your next matchday.