Five steps

Five steps from sign-up to your first contest

The beginner walkthrough covers five steps: sign up, complete KYC, build your first squad, join a contest, and review the result. Each step is calibrated for utility.

The five steps are: (1) sign up on the official site or app, (2) complete KYC verification (PAN, Aadhaar, bank account), (3) build your first squad within the salary cap, (4) join a free-to-play or low-stakes contest, (5) review the result and adjust your approach for the next fixture.

The picks desk recommends starting with free-to-play contests for the first 2-3 weeks. The points math is the same; the only difference is that the prize pool is small or non-existent. Use the free contests to build confidence before depositing.

First squad

The first-squad checklist

Your first squad follows the role split and the salary cap. The checklist below covers the seven decisions.

01

Pick 1 wicketkeeper

Choose the keeper with the best glovework first, batting second. Wicketkeeper is the highest points-per-credit role.

02

Pick 3-5 top-order batters

Anchors who bat in the powerplay. Two anchors + one aggressive opener is a typical split.

03

Pick 1-3 middle-order batters

Accumulator role for the middle overs. Look for batters with 25+ ball innings history in the role.

04

Pick 1-3 all-rounders

Pick all-rounders with confirmed 4-over bowling quotas, not part-timers.

05

Pick 3-5 specialist bowlers

Death-overs specialists and powerplay wicket-takers score heavily.

06

Set captain (2x) and vice-captain (1.5x)

Captain from the role with the highest expected points-per-credit. VC from a role-stable accumulator.

07

Stay within the salary cap

Total credits must be at or under the cap. If you are over, drop credits from the role with the lowest points-per-credit.

Contest types

Five contest types you will encounter

The contest types below are the standard formats. Pick the contest that matches your confidence and your squad shape.

Free contests

Real contests with real points math, but no entry fee. Best for beginners. Prize pool is small or non-existent.

Head-to-head

Two entries compete. Rewards consistency. Best for pickers with high confidence in a specific captain call.

Small contests (10-50 entries)

Multiple entries compete. Rewards balanced squads. Best for moderate-confidence picks.

Large contests (100-1,000 entries)

Larger fields, larger prizes. Rewards disciplined picks. Best for pickers with strong reads.

Mega contests (10,000+ entries)

Huge fields, huge prizes. Rewards differentials. Best for pickers with low-ownership captain calls.

An overhead view of a selection table
Common mistakes

Five common mistakes new pickers make

The five mistakes below account for most rookie losses. Avoid them and you are already ahead of the median first-season picker.

  • Spending 50%+ of credits on three big names. Cap by role first, then fill names into roles.
  • Captain the most-owned player. Only in head-to-heads. In mega contests, captain the differential.
  • Skipping KYC until the first withdrawal. Complete KYC at sign-up so the first withdrawal is fast.
  • Ignoring the surface read. The pitch sets the role priorities. Read it before the team sheet.
  • Chasing losses. Halve your contest size for a week after a losing streak. Review the reasoning log.
Points reference →
Fantasy cricket squad selection notes arranged on a table
Rule source

Begin with the current written rules

For starting fantasy cricket, the operator’s own current instructions must outrank screenshots, social posts, and memory. Read the exact language for account checks, squad rules, credits, contest choice, and result review, then record the date. Product rules, limits, and scoring bands can change without matching an older explainer.

If a condition affects identity, deposits, rewards, entry, or withdrawals, verify on the operator’s official site. We have not independently verified operator-specific values unless a dated source is stated. Do not treat a typical industry practice as a promise.

Bitstarz treats the result as conditional, not guaranteed. Recheck official information whenever a lineup, rule, status, offer, legal position, or payment detail can change.

All-round cricketer practising batting and bowling skills
Before acting

Complete a five-minute pre-action check

Confirm the verified domain, the account name, current eligibility, and the exact action you intend to take. For starting fantasy cricket, decide in advance what a successful outcome should look like and where the confirmation will appear.

Save non-sensitive evidence such as a transaction ID, rules timestamp, or ticket number. Never save an OTP, password, full card number, or unmasked identity document in casual notes. Good records help without creating a second security risk.

Bitstarz treats the result as conditional, not guaranteed. Recheck official information whenever a lineup, rule, status, offer, legal position, or payment detail can change.

Cricket team discussing a captaincy decision before play
Worked scenario

Use a small scenario before committing

Imagine a picker facing starting fantasy cricket for the first time. The sensible route is to use official platform instructions, confirmed teams, points rules, and a first-match log, test the smallest practical action where relevant, and stop if any detail conflicts with the published rules. A small test exposes process problems before they become expensive.

The decision is not whether the interface looks polished. It is whether whether a beginner is ready to submit a legal, role-balanced squad. When evidence is incomplete, pause and ask verified support for a written answer instead of filling the gap with an assumption.

Bitstarz treats the result as conditional, not guaranteed. Recheck official information whenever a lineup, rule, status, offer, legal position, or payment detail can change.

Indian cricket reader checking a match guide on a mobile phone
Timing and status

Separate normal processing from a real problem

Many account actions move through several states: submitted, under review, accepted, processed, and completed. A status still inside the operator’s published window is different from a rejected or reversed action. Track the stage before sending repeated requests.

If the published window passes, send one clear ticket containing the account identifier, timestamp, transaction or contest reference, and a concise description. Repeated attempts can create duplicate cases and make the timeline harder to reconstruct.

Bitstarz treats the result as conditional, not guaranteed. Recheck official information whenever a lineup, rule, status, offer, legal position, or payment detail can change.

Cost and risk

Count the full downside, not only the visible amount

The visible fee or credit cost is only one part of starting fantasy cricket. Also consider time, locked funds, missed deadlines, variance, identity exposure, and the possibility that an offer or contest condition changes the usable value.

Set a fixed limit before the event. A limit chosen after a loss is usually not a limit; it is a reaction. Never borrow to participate, never chase a result, and take a break if the activity creates stress or secrecy.

Bitstarz treats the result as conditional, not guaranteed. Recheck official information whenever a lineup, rule, status, offer, legal position, or payment detail can change.

Evidence file

Keep a clean record without oversharing

Useful records include dates, rule versions, non-sensitive screenshots, ticket numbers, and the exact wording of a support reply. They help distinguish a product issue from user error and support a focused escalation.

EvidenceCheck recency and source.
OpportunityTranslate the update into volume.
RiskWrite what could invalidate it.

Redact PAN, Aadhaar, bank details, addresses, QR codes, and balances before sharing any image. Verified support should not ask for a password or OTP. A request for either is a reason to stop the conversation.

Bitstarz treats the result as conditional, not guaranteed. Recheck official information whenever a lineup, rule, status, offer, legal position, or payment detail can change.

Support path

Escalate through verified channels

Use contact details shown inside the signed-in product or on the operator’s official site. Explain starting fantasy cricket in chronological order and state the resolution requested. A short factual ticket is easier to investigate than several emotional messages.

If the first answer does not address the evidence, reply within the same case and ask for the relevant rule or status. Avoid numbers copied from search listings. We have not independently verified third-party support contacts.

Bitstarz treats the result as conditional, not guaranteed. Recheck official information whenever a lineup, rule, status, offer, legal position, or payment detail can change.

How-to-play FAQ

Six questions about starting

Plain answers to recurring beginner questions.

30-60 minutes once you know the role math. The picks desk’s workflow is designed for repeatability — the second squad takes half the time.

No. Start with free contests for the first 2-3 weeks. The points math is the same; the only difference is the prize pool.

Check the playing XI. If your players did not play, the contest counts as a forfeit. Use the late-swap window next time.

Keep a log of every captain call, the reasoning, and the result. Review weekly. The picks desk’s methodology page describes the log structure.

See our points system reference for the typical T20 points table.

In the app or on the official site under Contests or Matches. The contest type is usually shown next to the entry fee.

Read the points system reference

The points system is the foundation. Read it before your second squad.

Points system
Sign in Get Started