Fantasy cricket, edited daily.
PlayerzPot's fantasy-cricket format is the familiar pick-11-within-a-credit-cap game, but the edges the lobby hides are where the desk earns its keep. This page is the daily routine: walk the squads, compare credit cost, lock the captain and confirm the state eligibility before the contest join screen.
Pick 11. Mark a captain. Read the credit cap.
A standard PlayerzPot contest asks you to pick eleven players from the announced squads within a fixed credit budget, mark one player as captain (2× points) and one as vice-captain (1.5×). The leaderboard settles at the end of the live match — your work happens before the toss.
How the credit cap works
Every player on the squad sheet has a credit cost set by the operator. The total credit you spend on eleven players must be at or below the cap. Marquee all-rounders cost the most credit; uncapped debutants cost the least. The cap is the same for every team in a contest — your job is to allocate it well.
The desk's read: spreading credit across three or four in-form all-rounders typically outscores stacking the cap on two marquee players. The all-rounder's bowling points are the cushion when the batting falls early.
How the captain (2×) and vice-captain (1.5×) work
The captain's total fantasy points are multiplied by 2 at the end of the match; the vice-captain's by 1.5. The multiplier applies to the total fantasy score, not to individual events. Worked example: a 60-ball 78 with two sixes and the captain (×2) lands at roughly 158 fantasy points. The full table lives on the points system desk.
The captain pick is the single highest-leverage decision in a fantasy team. Picking the marquee batsman who opens and falls in the powerplay is a common trap — the death-overs finisher usually scores more fantasy points, even with a smaller base.
How match type changes the read
T20, ODI and Test matches all run on the same PlayerzPot format, but the captain logic shifts by length. In T20, a death-overs finisher is the safest captain pick. In ODI, the bowler who completes a full quota is the cushion. In Test, the all-rounder with the longest batting position is the play. The captain desk walks the math for each format.
What our desk checks before lock-in
- Predicted XI cross-referenced with the team's social channels when available.
- Credit allocation balanced across roles rather than stacked on marquee players.
- Captain pick aligned to the death-overs read, not the headline form.
- Contest entry fee from the in-app lobby, never a number we cannot back up.
- State-wise eligibility check before the contest join screen.
If the data isn't in the public domain, we say so. The daily bonus amount rotates by campaign; the in-app Refer & Earn screen is the only place to read the current number. We do not invent figures.
Reading the squad announcement
The squad is announced roughly an hour before the toss. The change to watch is the batting order: a player moved up to four or five is worth more credit than the same player at seven. The change that matters most is who is left out — the in-form player dropped from the XI is the biggest signal in the announcement.
To verify: the predicted XI, the credit cost of each player and the contest entry fee all live inside the in-app lobby. The desk reads them once, locks the team, then walks away from the lineup until the next match card.
The five-step pre-lock checklist.
- Open the in-app lobby at the squad announcement, not at the toss.
- Compare the predicted XI to the team's social channels for last-minute changes.
- Allocate credit across three or four all-rounders before the marquee top-order.
- Pick the captain by death-overs role, not by headline form.
- Confirm state eligibility and contest entry fee inside the lobby before locking.
Build tonight's team on PlayerzPot.
Open the in-app lobby, pick a contest, and lock a team using the points-system cheat sheet from our desk. New users can enter from a practice contest — verify the current entry fee inside the lobby.