Bitstarz Fantasy Cricket Picks
Sign in Get Started

Fantasy cricket glossary — terms, roles, scoring, lingo

A fantasy cricket glossary of the terms, roles, scoring rules, and contest lingo that appear in picks coverage and on the operator’s points table.

Updated14 July 2026 Reading time6 min Editorial deskBitstarz picks desk
Floodlit fantasy cricket match scene
Editorial visual

Match and account context

A visual marker for the evidence-led Bitstarz desk. Verify changing details before acting.

RolesScoringContest lingoOperator termsFAQ
Roles

The five squad roles

A fantasy squad has five roles: wicketkeeper, top-order batter, middle-order batter, all-rounder, and bowler. The role split drives the captain pick and the salary allocation.

The five roles are: wicketkeeper (1), top-order batter (3-5), middle-order batter (1-3), all-rounder (1-3), and bowler (3-5). The exact split depends on the operator’s squad rule. The picks desk uses 1-4-2-1-3 as a baseline, with flexibility for impact-player formats.

Each role scores points differently. Wicketkeeper is highest points-per-credit because of stumpings and catches. All-rounder is second-highest because they deliver in both innings. Bowlers in death overs are third. Top-order anchors have the highest ceiling but also the highest volatility.

Scoring

Scoring terms you will see on the points table

The scoring terms below are the standard T20 fantasy scoring vocabulary. Verify the exact figures on the operator’s published table.

Boundary

A shot that reaches the boundary along the ground or after one bounce. Worth 4 runs + 4 fantasy points.

Six

A shot that clears the boundary without bouncing. Worth 6 runs + 6 fantasy points.

Strike rate (SR)

Runs scored per 100 balls faced. Strike-rate bonuses apply at 130+ and 150+ on most operators.

Economy rate (ER)

Runs conceded per over bowled. Economy bonuses apply at <5 rpo and 5-6 rpo on most operators.

Maiden over

An over in which no runs are conceded. Rare in T20 but worth 4 fantasy points.

Duck

A batter dismissed for zero runs. Typically worth -2 fantasy points on most operators.

Hat-trick

Three wickets in three consecutive balls. Rare in T20 but worth a bonus on most operators.

Captain (C)

The player whose points are multiplied by 2x. The biggest decision in your squad.

Vice-captain (VC)

The player whose points are multiplied by 1.5x. The hedge for the captain pick.

Contest lingo

Contest lingo you will see in the app

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

Head-to-head (H2H)

Two entries compete. The higher score wins the prize pool. Rewards consistency.

Small contest

10-50 entries compete. Balanced fields. Rewards disciplined picks.

Large contest

100-1,000 entries compete. Larger prizes. Rewards strong reads.

Mega contest

10,000+ entries compete. Largest prizes. Rewards differentials.

Free contest

No entry fee. Real points math, small or no prize pool. Best for beginners.

Private contest

Run by a group (friends, work colleagues). Small field. Good for practice.

Practice match

A non-league fixture used for fantasy practice. Some operators offer practice contests during off-season.

Season-long contest

Tracks points across the entire season or tournament. Rewards consistent captain picks.

Leaderboard

A ranking of contestants in a contest or season. Top finishers win prizes.

Operator terms

Operator terms you will see on the official site

The operator terms below are the standard vocabulary for KYC, wallet, and customer-care pages.

KYC (Know Your Customer)

Identity verification required before the first withdrawal. PAN, Aadhaar, and bank account.

Bonus balance

A balance of contest credits received from a welcome offer or promotion. Locked until wagering requirement is met.

Real-money balance

A balance of deposited funds and withdrawable winnings. Available for contest entry or withdrawal.

Wagering requirement

The number of times the bonus must be played through before it converts to withdrawable balance.

Self-exclusion

A tool that locks your account for a fixed period (6 months to 5 years). Cannot be reversed during the exclusion.

Deposit limit

A cap on daily, weekly, or monthly deposits. Decreases take effect immediately; increases have a cooling-off period.

Time-out

A short-term block on sign-in (24 hours to 6 weeks). Useful during a losing streak.

Grievance officer

The operator’s escalation contact for unresolved issues. Published on the official site.

Impact player

A substitute player that can replace one of the starting XI based on toss. Available in some formats.

Fantasy cricket squad selection notes arranged on a table
Rule source

Begin with the current written rules

For fantasy cricket terminology, the operator’s own current instructions must outrank screenshots, social posts, and memory. Read the exact language for plain definitions for roles, scoring, contests, verification, and match phases, 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.

IPL batter preparing to attack during the powerplay
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 fantasy cricket terminology, 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.

Fast bowler training for the final overs of a T20 match
Worked scenario

Use a small scenario before committing

Imagine a picker facing fantasy cricket terminology for the first time. The sensible route is to use current rule tables, official cricket terminology, and short worked examples, 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 how an unfamiliar term changes a squad or account decision. 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.

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 fantasy cricket terminology. 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 fantasy cricket terminology 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.

Glossary FAQ

Six questions about fantasy cricket lingo

Plain answers to recurring glossary questions.

Expected fantasy points divided by salary. A 9-credit batter expected to score 45 has a 5.0 ratio. Spend credits where the ratio is highest.

A player selected by fewer than 20% of contest entries. Low-ownership players are the basis of differential picks.

The number of times the bonus must be played through before it converts to withdrawable balance. A 5x requirement on ₹1,000 means ₹5,000 in eligible contest entries.

A captain pick with low ownership (typically under 20%) that wins mega contests. Captain differentials lose head-to-heads but win mega contests.

The effect of the toss on the match outcome. Under lights with dew, the side batting second gains 5-8% win probability. The captain pick adjusts accordingly.

A one-over-per-side tiebreaker. Super-over runs and wickets are typically counted in fantasy scoring. Verify on the operator’s table.

Read the points system reference

The points table is the foundation. Read it before your next squad.

Points system
Sign in Get Started