Headingley, Tuesday 28 July 2026, 11:00 PM IST — a Dream11 preview of Match 10 of The Hundred Men's 2026 between Sunrisers Leeds and Manchester Super Giants, with probable XIs, the 158/148 pitch band, head-to-head form, captain and vice-captain picks, and a grand-league XI.
Fresh match notes, squad context, and the lineup math that shapes tonight’s contest build.
Headingley, Tuesday 28 July 2026, 11:00 PM IST — probable XIs, the 158/148 band, head-to-head form, captain and vice-captain picks and a grand-league XI for SUL vs MSG.
Read the full brief →Series locked 1-1 after Cardiff — Sundar's injury, predicted XIs, Lord's slope and the fantasy process that still travels.
Read the full brief →From warmup order to press-conference hints, the signals that tell you who actually plays — and who is just a rumour.
Open teams desk →A framework for spending the last 5% of your cap on a player who actually moves the projection — not the most popular name.
Open fantasy tips →Every guide is written by analysts who watch the ball, the pitch, and the numbers. We publish what the data supports, flag what it doesn't, and keep the writing useful for players at any level.
Pitch report, toss angle, and form context for every scheduled fixture — written for fantasy teams, not for headlines.
Read tonight's calls →How the points system actually rewards different roles — and where fantasy value hides when ownership is high.
See the playbook →Recent minutes, venue splits, matchup data, and what to expect when the player walks out tonight.
Browse the player desk →Two names, one differential call. The desk's pick sits alongside a contrarian option for larger contests.
With dew expected in the second innings, our model favours the anchor who can bat through the chase and the spinner who controls the middle phase. Both bring captaincy-grade ceiling with relatively contained downside.
Most fantasy players over-weight the obvious events. Here's the full points map and the role-by-role split that wins contests over a season.
| Action | Points | Why it matters |
|---|---|---|
| Run scored | +1 | Floor for any batter |
| Boundary bonus | +4 | Compounds on strike rotation |
| Six bonus | +6 | Highest ceiling per ball |
| Wicket (bowler) | +25 | Dominant single event |
| Maiden over | +4 | Pressure premium |
| Catch | +8 | Reliable for fielders |
| Captain multiplier | 2x | The single biggest decision |
Quick read: wickets and sixes swing contests more than singles, so bowlers with strike potential and batters with boundary intent outscore accumulators on a points-per-credit basis.
Each match card shows venue, format, projected XIs, and the desk's lean — updated as team news arrives.
A short watchlist of names whose fantasy projection is moving up — based on form, role, and upcoming fixtures.
All-rounder · IND. Middle-order anchor with boundary intent. Role security, growing ceiling.
Top-order left-hander, strong against spin. Differential when ownership drops.
Wrist-spinner with powerplay usage expanding. Wicket ceiling rising.
Wicketkeeper-batter, powerplay multiplier. Strong recent run rate.
The desk's repeatable process for going from a fixture list to a submitted lineup — without panicking into a popular captain.
Decide contest type, salary cap, and risk profile (cash vs GPP) before you look at player names.
Pitch report, dew forecast, and boundary dimensions tell you which roles gain value tonight.
Lock 4-5 high-floor players first, then spend the remaining credits on a captain and a differential.
Re-rank the lineup by likely outcome range. A team that wins a 30/70 split beats one that wins a 50/50.
Projected XIs, role balance, and bench depth — the things that decide a long-format contest over a season.
Most submitted teams are top-heavy. The desk's principle is to spread ceiling across roles, so a single failure doesn't sink the day.
Auction reactions, squad analysis, captaincy logs, and venue-by-venue cheat sheets for the world's most-watched T20 league.
Where each squad's salary was spent — and which players project as fantasy value at their auction price.
Match-by-match captain picks with results — updated throughout the season, not just the playoffs.
Surface, dimensions, dew history, and pace-vs-spin tilt for every IPL venue on the calendar.
This site is editorial. For any operational, bonus, or policy detail, always confirm directly with the brand through its official channels.
Direct link to the operator's current iOS and Android build, plus the device requirements list.
App guide →Web installer and the most common install path on Android and desktop, with security notes.
Download guide →How to install the APK safely, what permissions to expect, and how to verify the file before opening.
APK guide →Where to enter a welcome code, the verification flow, and what changes once a code is applied.
Bonus code guide →The desk's standing rule: never play with money you can't afford to lose, never chase a loss, and use the operator's own deposit and session controls.
Fantasy cricket rewards players who plan across formats, not just for the next match. The seven-stage walkthrough below is what the desk applies to every contest we cover.
Match contest, mega contest, head-to-head, or season-long. Your risk profile and captain decision change with each.
Surface, dimensions, dew forecast, and wind. These decide whether to load pace, spin, or all-rounders.
Select from the projected XI rather than the squad list. The captain is only valuable if the player plays.
Two top-order batters, an anchor, two all-rounders, a death bowler, and a wicketkeeper covers most formats.
The last 5% is where contests are won. Spend on differential upside, not on a player who is 90% selected.
Vice-captaincy is not just a backup. It is the second-biggest point swing in your lineup.
Pre-toss pick, confirmed-XI change, and post-match lesson. The miss log is more durable than a winners feed.
Captaincy is the highest-leverage decision in any fantasy lineup. The desk's framework below is what we apply to every predictions card.
The single biggest mistake fantasy players make is captaincy by reputation. Captain a player who is secure in his role at this venue, not the most famous name on the team sheet.
Operator scoring systems differ. The desk publishes a reference table for the most common formats so you can compare — not a universal map.
| Action | Common range | Notes |
|---|---|---|
| Run scored | 0.5 to 1 point | Lower in T20 leagues, higher in Tests and ODIs. |
| Boundary bonus | +4 points | Common in T20 formats; rarer in longer formats. |
| Six bonus | +6 points | Often stacks with boundary bonus on some operators. |
| Wicket | 10 to 25 points | Varies sharply by format and operator. |
| Maiden over | +4 to +6 points | T20 and ODI only; usually capped at 4 overs per bowler. |
| Catch | +4 to +8 points | Slip catchers and fielding all-rounders benefit most. |
| Captain multiplier | 2x | Standard across most operators; confirm on the operator's page. |
| Vice-captain multiplier | 1.5x | Standard across most operators; confirm on the operator's page. |
How to read this table. The numbers above are illustrative ranges drawn from major fantasy cricket operators. Always confirm the current scoring system on the operator's own page before any contest — bonus stacking, strike-rate bonuses, and dot-ball points are not universal.
The format of the contest changes the right lineup. A 50% lineup with low ownership is the right play in some contests, a near-consensus lineup is right in others.
Smallest field, lowest variance, lowest payout. Best for early-season bankroll testing.
Skill matters more than variance. Best place to learn the contest's scoring rhythm.
Largest payout, largest variance. Differential captaincy pays off; consensus captaincy rarely does.
Patience pays. Selection accuracy over weeks matters more than a single contest's luck.
The players desk tracks role security, expected overs, phase usage, and recent form for the cricketers the desk covers. Every profile carries a four-match sample window and a date — and is honest about when the sample is too small to lean on.
Every prediction the desk publishes is built from the same four inputs, in this order: venue and weather, projected XI, role security, and recent form. The captain pick and the avoid pick are then stress-tested against ownership before publication.
Surface, dimensions, dew forecast, and how the conditions have shaped recent results at this ground.
Built from team-news reports, warmup order, and the most recent press conference. Cross-checked against any late fitness update.
Where in the batting order? How many overs with the ball? Is the player rotating with someone else for the same role?
Four-match sample window — and an explicit note when the sample is too small. Reputation is not form.
Two candidates — the consensus pick and a contrarian option. Each is stress-tested for role security and venue fit.
The player whose projection exceeds ownership by the largest margin. Always with a clear reason; never on name value.
The high-profile selection to leave out, with a clear reason. Avoid picks are the desk's most-cited predictions.
What the desk got right and what the desk got wrong. The miss log is more durable than a winners feed.
The live matches desk tracks scheduled fixtures, projected XIs, and weather for every international and franchise match the desk covers. Each fixture carries a state: scheduled, preview published, toss updated, or completed.
Predictions age quickly. The desk's standing rule: a wrong pick gets a correction note on the same page within 24 hours, and the post-match review is published whether the pick was right or wrong.
If a published pick is invalidated by a confirmed-XI change, the desk posts the correction on the same card before the toss.
Every prediction card carries a post-match review once the contest closes. Wins and misses are both published.
When a player profile, points system, or team-sheet update changes a prior analysis, the desk logs the change with the time and source.
The desk does not invent ownership percentages, captaincy records, or venue averages. Where the data is not available, the desk says so.
This site is not affiliated with any operator. Editorial analysis is independent of the Betwinner brand and any other commercial relationship.
Operator terms > official team sheet > board announcement > venue report > press conference > verified reporter. The desk cites the highest available source.
Fantasy cricket has a vocabulary that operators occasionally invent to suit their own scoring. The glossary below is what the desk means when it uses each term.
A player's certainty of holding his batting position or bowling overs for the contest. Low role security is the desk's biggest de-selection signal.
Which phase of the innings a bowler or batter is used in: powerplay, middle, or death. Phase determines expected points as much as skill.
A selection whose projection exceeds ownership by a meaningful margin. The desk publishes a differential pick on every prediction card.
The percentage of contest entries that select a given player. Public ownership feeds are useful — but the desk does not rely on a single source.
How many overs a bowler is projected to bowl, given the match situation and the bowler's role. Drives wicket-point expectations.
The window between lineups locking and the toss where some operators allow one or two swaps based on confirmed XI. Use sparingly.
The diminishing return of spending the last 5% of the salary cap. The desk writes the framework on the tools page.
Where a single action credits more than one bonus (for example a six that also credits a boundary bonus). Operator-specific.
Three pages cover most of what a new reader needs. Each is a 1,500+ word read with examples, FAQs, and a clear next step.
Captaincy math, salary-cap discipline, role balance, and common selection errors — evergreen strategy that survives a season.
Read the tips →Match calls with reasoning, not guesswork — pitch report, expected XI, role security, captain angle, differential, and avoid pick.
Read the predictions →Captain scorecards, salary allocation tables, scoring comparisons, and form-window logs for repeatable decisions.
Open the tools →This desk is not affiliated with the Betwinner operator or any other sportsbook. Where the site links to the operator's pages, the link is for reader convenience, not for compensation. The editorial team does not run contests, take deposits, or process payments.
If a question isn't here, the contact page is the fastest way to reach the desk.
Editorial fantasy-cricket analysis: captain picks, points-system guides, tournament coverage, player projections, and Betwinner-related operational guides (app, download, APK, bonus code, login). We do not run contests, take deposits, or process payments.
No. This desk is editorial. Betwinner is a separate operator. Always verify any account, payment, or policy detail directly with the brand through its official channels before participating.
Tonight's picks and live-match cards are updated daily. Predictions, tips, teams, players, and IPL pages are refreshed whenever team news, weather, or the points system changes.
Fantasy cricket is treated as a game of skill in most Indian states, but state-level rules differ. The desk publishes a state-by-state eligibility guide and recommends checking the local regulator's current position before playing.
Each pick is built from the venue, the dew forecast, the recent minutes/overs, and the role — then stress-tested against ownership so a contrarian option is always alongside the consensus pick.
Short quoted excerpts with attribution are welcome. For longer republication or syndication, please contact the desk first so we can review the use and any time-sensitive figures.
Editorial work ages fast. The decision audit below captures the changes the desk has made — corrections, updates, and the moments where the desk's prior view was wrong. The miss log is more credible than an unbroken winners feed.
The desk moved to a slate-blue night newsroom palette to differentiate the visual language from generic sports blogs. Mint accents now mark verification frames; indigo carries the editorial voice.
Added seven new pages: customer care, referral code, legal status, company, wallet and KYC, withdrawal, and delete account. The brand SERP cluster now reaches the twelve-page minimum.
The desk's eight-step prediction methodology is now published on the homepage. Every prediction card carries a post-match review whether the pick was right or wrong.
Roadmap is editorial guidance, not a delivery promise. The desk does not commit to specific match calls before the team sheets are confirmed.
The desk is publishing a comparison of scoring systems across major fantasy operators, so readers can see what changes when they move between platforms.
Every prediction card will carry short source labels — official team sheet, board announcement, venue report, weather provider — visible at a glance.
The desk is expanding the inline glossary above into standalone pages for role security, phase usage, differential, ownership, and expected overs.
Two captain picks, the points math, and the venue read — all in one place. No login, no deposit, no noise.
