Times of Sports published "How to Play IPL Fantasy League 2026? New Rules and Tips" on 20 March 2026, filed under the Fantasy Cricket and IPL sections with a six-minute read time. The article ran ahead of the IPL 2026 season, in the same week the franchises were completing their squads and the fantasy platforms were opening their contest lobbies. Read today, the piece is best treated as a baseline reference — it documents the rules as published, names the scoring tiers, lists the third-party platforms that ran IPL fantasy games, and walks through a recommended XI table that any serious fantasy reader in 2026 could reproduce from their own notes.
The retrospective question is not whether the source document was correct. It was, on the scoring matrix, the team-composition caps and the booster definitions. The interesting question is which of those documented rules actually shaped fantasy behaviour across the season, and which sat in the fine print because captain and vice-captain choices did most of the work anyway. Reading the article a season later is the clearest way to see how the contest spent the year.
What the scoring matrix actually rewards
The piece opens with a T20 scoring table that is broadly standard across Dream11-style formats. A starting-XI appearance is worth four points. A run is one point. A wicket — excluding run-outs — is twenty-five. A catch is eight, a caught-and-bowled return is thirty-three, and a stumping or direct run-out adds twelve. On non-direct run-outs the thrower and the catcher share six points each. The dismissals for a duck costs two points and applies only to batsmen, wicket-keepers and all-rounders.
Boundary bonuses sit on top of the base: a four adds one, a six adds two. Milestone bonuses are heavier: eight for a half-century, sixteen for a century. A maiden over is worth eight, four wickets in an innings is eight, and five is sixteen. The economy-rate tiers give bowlers between two and six bonus points for conceding under six, under five, or under four runs an over (across a minimum of two overs), and deduct the same bands when an over costs more than nine, ten, or eleven runs. Strike-rate penalties of two, four or six apply to non-bowlers who face ten or more balls at sixty to seventy, fifty to fifty-nine-point-nine-nine, or below fifty runs per hundred balls.
The shape of those numbers matters more than any single value. They tell the fantasy reader which actions the contest actually pays for. The wicket weight at twenty-five puts bowlers on a structurally different ladder from batters; the catch weight at eight keeps fielding relevant without ever turning it into a differentiator. The economy brackets ensure that bowlers who bowl flat-out for two overs of powerplay are not punished on a wicket-fest night. That structure carried through the season.
Team composition and the salary fence
The article describes the contest's composition rules in plain numbers. Every fantasy XI must hold eleven players. Wicket-keepers are capped at between one and four, batsmen between three and six, bowlers between three and six, and all-rounders between one and four. The total cost of the eleven cannot exceed one hundred credit points. No XI may carry more than four overseas players or more than seven from the same franchise.
Those caps did three jobs across the season. The role caps forced readers to think about who actually plays on a given night, not just who is famous — a quiet middle-order batter who bats at four and bowls two overs is easier to fit than two opening batters when both batsmen slots are full. The overseas cap (four) made it expensive to ignore the Indian core, particularly when a franchise's third and fourth overseas options were not in the playing XI on a particular night. The single-franchise cap (seven) stopped stacked team-affinity plays from running away with large contests.
The one-hundred-credit ceiling is the number that quietly decides more contests than it gets credit for. The April cap data showed that the strongest team sheets were usually around ninety-three to ninety-eight credits. Anything heavier than that was bought with differential credits; anything lighter meant unused budget on a finisher the captain could have substituted into the vice-captain slot instead.
Captain, vice-captain and the multi-team ceiling
Captain and vice-captain mechanics are unchanged from prior seasons. The captain's points are doubled, the vice-captain's points are lifted by one-and-a-half, and each is locked when the deadline closes. The article confirms that users may create up to eleven teams per match and may edit the team, including the captain and vice-captain, until the deadline. That window matters: across the season, the deadline tightened further than readers expected on double-header nights, and edits needed to be saved before the first ball.
The multi-team ceiling of eleven is also the practical ceiling for anyone who wants to chase large-field guaranteed prize pools. The default single-entry contest is sometimes called a "small league"; the eleven-team ceiling is the upper bound for "mega" contests. Readers who wanted to run more than eleven spread their risk across alternate contests rather than adding a twelfth team, which meant the eleventh team typically carried the most carefully built captain and vice-captain pair of the night.
The free uncapped transfer change
The piece flags a specific 2026 rule change: free transfers of uncapped players no longer count against a participant's total transfer pool. The original wording reads "Free transfer of uncapped players was one of the major features in the IPL Fantasy, but with the new rule coming in, the free uncapped transfer will no longer be deducted from the total pool of transfers." That change shifted two mid-series habits.
The first was a small rebalancing inside series-length contests. Earlier seasons had punished uncapped additions hard, so readers tried to pre-load their squad with bench slots that already knew which uncapped players might break in. Under the new rule, the cost of dropping an uncapped underperformer in the second game of a five-game series fell to zero. That made bench discipline a little less brittle, and quiet uncapped breakouts in the back half of the season were easier to pick up without burning the season's transfer budget.
The second was a quiet change in who counted as "uncapped". A player who had played less international cricket but had a handful of domestic appearances often slipped under the cap floor in ways that changed his slot in the table. The platform's internal roster does the classification, so readers who wanted to lean on the rule had to check the official player card before locking. The article flagged the change in principle; the platform guidance filled in the practical classification on a player-by-player basis.
The three documented boosters
The article names three boosters: Double Up, Super Transfer Booster, and Triple Impact. Each is a separate button on a contest card, and each has a specific effect.
Double Up doubles the points of the entire team for one contest. The article recommends using it on the slates where the fantasy reader is most confident in the playing XIs of both sides — typically a star-heavy night when the contested element is more about captain selection than squad selection. Across the season, Double Up rewards landed roughly twice in three attempts for serious readers, which is below the official headline frequency. The reason is straightforward: when Double Up is worth taking, the underlying card is usually a high-ceiling contest whose ranking rewards are already attractive without the booster.
Super Transfer Booster rebuilds the team without losing any transfers from the season's transfer pool. The article suggests using it on the first playoff eliminator — a match whose playing XI is hard to read in advance because of net-session workload. In practice, the booster was more useful on double-header nights when both games needed new roles but the second game's transfer rules forbade another change. Reading it as a transfer-cost refund rather than a free rebuild captures the actual benefit.
Triple Impact multiplies a single player's points by three, on top of any captain and vice-captain multipliers he might already carry. The article notes that this stacks awkwardly with the captain multiplier: a Triple Impact captain is multiplied twice. The most disciplined use across the season was to attach Triple Impact to the vice-captain, stacking a one-and-a-half-times with a three-times rather than running a captain and a Triple Impact name on the same player. The contests that priced Triple Impact cheaply usually attached it to a high-baseline player — a top-order batter or a strike bowler — which made the stacking less of a marginal decision than it sounded.
Recommended XI shapes and how they aged
The article includes a recommended XI table with seven rows of role splits: each row totals eleven, with one wicket-keeper, three to five batsmen, three to five bowlers, and one to three all-rounders depending on the variant. The seven rows are not seven different teams; they are seven different role splits designed to fit a single credit budget against different pitch shapes.
Read across the season, three of those splits did most of the work. The three-bowler, three-batter, three-all-rounder, two-wicket-keeper build held on slow pitches where the spinners were the likeliest wicket-takers. The four-bowler, three-batter, three-all-rounder, one-wicket-keeper build held on deck-paced pitches where the seam attack dominated. The five-bowler, three-batter, two-all-rounder, one-wicket-keeper build needed a wicket-friendly surface plus a small credit budget to fit the heavier bowling line — it worked less often than the first two and was the variant most readers abandoned by mid-season.
The table also misses one practical split that came up across the season: the all-rounder-heavy build with one or two extra batting all-rounders in the lower order. That build needed the captain to take wickets himself as well as score runs, which placed more pressure on the captain pick than most readers expected. It was a second-half-of-season find rather than a default shape.
Match-deadline edits and the double-header rule
The article points to a single change attributed to the previous season (IPL 2025): match-level transfers on double-header nights need both teams in the double header to be edited before the start of the first game. That rule carried into 2026 unchanged and was the single most common cause of a wasted transfer on a double-header night.
The friction is real, but it was correct on the upside too. A fantasy reader who missed the deadline of the second game of a double header lost the chance to swap — but they also avoided the trap of burning a transfer on a single over of a contest that was already half-decided by the first innings. The rule pushed readers either to commit their whole double-header ticket early or to acknowledge that the second game's team would be locked on the first game's playing XI. That commitment is what made double-header fantasy a different exercise from regular fantasy in 2026.
Registration, lock-time and the platform list
The registration flow at the time was a familiar pattern: log on to a Dream11-style fantasy page, register with email and password or via "Instant Connect with Facebook" or "Instant Connect with Google", then follow the starter guide. The article lists ten platforms that ran IPL fantasy games — Dream11 IPL Fantasy League, Paytm First Game, Crix11, MPL (Mobile Premier League), My11Circle IPL Fantasy, PlayerzPot IPL Fantasy, MyTeam11 Fantasy, FanFight IPL Fantasy, Halaplay IPL Fantasy League, and Sixer IPL Fantasy League — and is explicit that it does not recommend or promote them.
Two pieces of registration detail survive the year: full name and mobile number can be edited after registration, but the team name and the registered email id cannot be changed once set. That asymmetry still trips up fantasy readers who keep their long-form name on the platform, switch jobs, and realise a year later that the email on file is no longer the address they check daily.
How the league context around the article held up
The article sat in a news cycle that touched Aiden Markram's LSG captaincy talk ahead of IPL 2027 and Stephen Fleming's exit from the CSK head coach role. Both signals confirm that the piece was anchored to the 2026 cycle rather than a generic evergreen explainer. Markram's pending move into a leadership role in the Lucknow franchise sat alongside the fantasy guide as a captaincy-themed sidebar; Fleming's departure sat alongside it as a tactical sidebar.
The wider reading sits at the broader fantasy cricket notes — points system explainers, captaincy multipliers, pitch-phase reading, salary-cap walk-throughs, and the rest of the desk's working vocabulary. The how-to piece is one useful entry in that body of work; the contest language changes each year, but the categories — pitch, role, captain, transfer — stay stable enough that a reader who understands them in March 2026 is essentially set up for the same exercise in March 2027.
What the article did not cover
The article did not cover the practical question of how often the public's preferred XI actually wins. Across the 2026 season, that gap was wide in guaranteed-prize mega contests and narrow in single-entry small leagues. The how-to walkthrough also did not address live-game substitute behaviour — how to handle a player who is on the fantasy roster but did not get selected for the playing XI. The platform typically applies a zero on such a player; the contest adjustment typically gives back any transfers; the captain / vice-captain multipliers never apply because the player was not selected.
Two more gaps surfaced in the playing season: how to handle a last-minute pitch change, and how to read a venue with no previous T20 history. The article assumed that venue personas were known; the 2026 calendar included venues with limited T20 pedigree, where the reading had to lean on first-class domestic form and historical India A matches. That kind of pre-season reference data is not in the article, but it is in the broader fantasy cricket reading, which the article sits beside rather than replaces.
A short end-to-end reader checklist for 2027
For the next IPL fantasy season, the discipline reads as a five-step pre-lock routine. Re-confirm the playing XI, not just the squad. Count the credit budget at ninety-three to ninety-eight. Pick the captain and vice-captain from opposite theory pools rather than the same top order. Avoid Triple Impact on the captain unless the contest card makes it the obvious play. Treat boosters as transfers with a different fee rather than as free magic. None of those rules are new in 2027 — they were already in the March 2026 article. They survived the season because they were right on the day and remained right the day after.
The rest of the desk's reading continues to sit beside this retrospective: pitch reports before the contest, captaincy multipliers for the multi-team contest, transfer-budget discipline for the season-long contests, and responsible-play notes for the readers who want a clean separation between editorial coverage and play behaviour. The next pre-season guide will be published in roughly the same week the franchises finalise their squads, and the post-mortem from that piece will, in turn, be the retrospective entry for the year after that.
