Consider11 fantasy cricket managers tend to treat the wicketkeeper slot as an afterthought — pick the gloveman with the highest batting position, set and forget. That worked in 2023 when keepers averaged 30-40 fantasy points per match and captaincy rarely went to the slot. In 2026, with catch bonus at 8 points, stumping at 12, and three platform-specific scoring systems diverging on wicketkeeper weight, the slot is now the second-most-influential pick on your Consider11 roster behind the captain.
This guide walks through the math Consider11 managers are using to pick keepers on Dream11, MyTeam11, Gamezy, and My11Circle. We cover the bonus structure, the catch-rate filter that separates premium keepers from average ones, the ownership cap that turns a 12% selection into a 28-point swing, the wk-bat vs wk-only class trade-off, the spin-bowling-side stumping multipliers that almost nobody prices in, and the captain-pair decision framework that decides whether your keeper plays as captain, vice-captain, or bench piece. Read this once before the IPL 2026 mega-auction and you will save a week of recalibration mid-season.
Consider11 reader primer: The catch-and-stumping bonus math that decides keeper value
On every Consider11-format fantasy cricket platform, wicketkeeper points stack across three components: batting points, dismissal points, and a bonus tier. For IPL 2026 the headline numbers look like this on the four platforms most Consider11 managers cross-play on:
- Catch: 8 points per dismissal across Dream11, MyTeam11, Gamezy, My11Circle.
- Stumping: 12 points on Dream11 and MyTeam11; 10 on Gamezy; 8 on My11Circle (My11Circle under-weights stumpings to balance the volume of left-arm spin in their scoring pool).
- Run-out direct hit: 12 points flat across all four platforms.
Stacking matters. A keeper who takes 2 catches and 1 stumping in a single innings scores 28 bonus points on Dream11 before a single batting run is added. On My11Circle that same performance is 24 points. Across 14 league matches, the gap between a high-volume dismissal keeper and an average one is 60-80 fantasy points — roughly equivalent to a 25-run cameo with a captain multiplier on top.
Consider11 catch-rate filter: The 1.4 dismissals per innings threshold
Not every keeper is created equal on Consider11 contests. The premium tier is defined by a single number: dismissals per innings completed behind the stumps. Anything above 1.4 puts a keeper into the top-8 fantasy scorers at the slot across a 14-match IPL window. Anything below 1.0 puts them into the bench-or-bust category regardless of batting position.
How to apply the filter: take the keeper's last two IPL seasons, count total dismissals (catches + stumpings) divided by innings kept, and rank. The top-4 keepers in IPL 2026 by this metric — based on the last 28 matches of IPL 2024 and 2025 — all average 1.6+ dismissals per innings. The next 4 average 1.2-1.4. Below 1.0 you have batting-only keepers who contribute almost nothing from the gloves.
Consider11 managers who default to the India-captain keeper (the obvious pick on most days) often miss the volume edge of a backup keeper who keeps against spin-dominant attacks. The 1.4 threshold catches this.
Consider11 ownership cap rules: The 18% differential that decides grand-league payouts
On Consider11 mega contests, ownership percentage is the lever that decides whether your wicketkeeper pick pushes you into the top 1% or holds you at median. The standard rule across all four major platforms is that any player with ownership above 18% caps your upside on a big score — because if they go big, half the field also goes big, and you tie instead of leapfrogging.
The math: if your keeper is at 22% ownership and scores 80 fantasy points (a strong day), you finish at the 70th percentile. If your keeper is at 11% ownership and scores 80, you finish at the 92nd percentile. The 11-point ownership gap is worth 22 percentile ranks. In a Consider11 grand league with Rs 1 Crore in prize money, that is the difference between a payout and a free entry.
The trade-off: low-ownership keepers are low-ownership for a reason — they are riskier picks, possibly out of form, possibly facing a tough opposition. Do not blindly chase sub-10% ownership. The sweet spot for differential captaincy is 8-15% ownership. For non-captain picks, 12-22% ownership is the band that gives you upside without ruining the team shape.
Consider11 wk-bat vs wk-only: The class math that decides when to ignore batting
Consider11 managers split keepers into three classes, and the choice between them is the second-biggest decision after captain selection. The three classes are:
- Wk-bat (top-order): Keeps wickets AND bats in the top 4. Highest ceiling, highest floor. Premium picks. Most expensive on the credit budget.
- Wk-bat (middle-order): Keeps wickets AND bats at 5-7. Medium ceiling, medium floor. Mid-range picks.
- Wk-only: Keeps wickets, bats at 8 or lower. Low ceiling, low floor on batting — but can be elite on dismissals.
The class math on Consider11 contests: a wk-bat top-order keeper averaging 35 runs and 1.5 dismissals scores 47 fantasy points per match. A wk-only elite dismissal keeper averaging 8 runs and 2.0 dismissals scores 36 fantasy points per match. On a 100-credit budget, the wk-bat costs 11 credits and the wk-only costs 8 — the wk-bat gives you 11 more points for 3 more credits, a 3.7 points-per-credit return vs 4.5 for the wk-only.
Translation: on balanced Consider11 contests, the wk-only elite dismissal keeper is better value for your budget. On captain-heavy contests where you need a backup batting option, the wk-bat top-order keeper is the right call. Match the class to the contest format.
Consider11 spin-bowling-side stumping multipliers: The angle almost nobody prices in
Stumpings happen off spin bowling more than pace — about 65% of IPL stumpings come off spinners, and the rate jumps to 78% in the middle overs (7-15) where left-arm spin and leg-spin dominate. Consider11 managers who pick a keeper without checking the opposition spin attack are leaving 8-12 points per match on the table.
The framework: before locking your keeper, check the opposition's likely spin combination. If the opponent plays two quality spinners (a wrist-spinner AND a left-arm orthodox), the keeper has a 60%+ chance of a stumping in that innings. If the opponent plays only one spinner and bowls pace-dominant, the stumping probability drops to 30-35%.
The flip side: pace-bowling attacks produce more catches at the keeper position because edges fly wider. So a pace-heavy opposition boosts catch volume, a spin-heavy opposition boosts stumping volume. Both score the same on Consider11 (8 vs 12 is the gap, but the volume difference compensates). The trick is identifying matches where one or the other dominates and biasing your keeper pick accordingly.
Consider11 captain-pair framework: When to captain the keeper and when to bench
The captain slot on Consider11 contests gives a 2x multiplier, the vice-captain gives 1.5x. With a 100-credit budget and 11 picks, only 1-2 of your players can take an armband. The keeper usually plays vice-captain, occasionally captain, almost never bench — but the rules have shifted in IPL 2026.
Captain the keeper when: the keeper is wk-bat top-order AND batting first AND the opposition is spin-heavy AND ownership is sub-15%. That combination occurred 4 times in IPL 2025 — each instance produced 80+ fantasy points after the 2x multiplier.
Vice-captain the keeper when: the keeper is wk-bat top-order AND the match is balanced (no obvious spin or pace dominance) AND ownership is 15-25%. This is the safer default for Consider11 mega contests.
Bench the keeper (don't armband) when: the keeper is wk-only AND ownership is above 25%. The math rarely works — the upside is bounded by dismissal volume and the ownership is too high for differential gain.
Consider11 IPL 2026 wicketkeeper tier list and platform-by-platform rotation
For the IPL 2026 season on Consider11 contests, the wicketkeeper tier list breaks into four buckets. Tier 1 (captain-eligible, 11+ credits) is reserved for the India-captain gloveman and one or two franchise-staple wk-bats. Tier 2 (vice-captain-eligible, 9-10 credits) covers the next 4-5 keepers who bat in the top 6. Tier 3 (specialist differential, 7-8 credits) is the elite wk-only dismissal volume picks. Tier 4 (bench fodder, 6-7 credits) is for keepers to avoid except in extreme matchups.
Platform rotation strategy: on Dream11, where stumping is 12 points and ownership caps at 18%, lean Tier 1 with the India-captain keeper. On MyTeam11, where stumping is also 12 and ownership caps at 20%, lean Tier 2 with a wk-bat middle-order option. On Gamezy, where stumping is 10, lean Tier 3 with the elite wk-only for the differential push. On My11Circle, where stumping is 8 and ownership caps at 22%, lean Tier 1 — the bonus structure does not reward wk-only volume, so you need the batting.
The rotation across platforms matters because Consider11 managers who cross-play maximize edge when each platform gets a different keeper type. Four teams, four keepers, four different paths to a payout.
Consider11 closing notes: Building the keeper slot into your IPL 2026 plan
The wicketkeeper slot is now the second-most-decision-heavy pick on your Consider11 roster. Build a watchlist of 8-10 keepers before the season starts. Track their catch-rate, their likely batting position, the opposition spin attack for each match, and their ownership on each platform. Re-rank the watchlist weekly. Lock in your pick the morning of each match once the toss confirms batting order.
The framework above is the system Consider11 managers who finished top-1% in IPL 2025 grand leagues used consistently. It is not a one-week trick — it is a 14-match discipline. Start the watchlist this week, apply the filters from match 1, and your Consider11 wicketkeeper slot will outscore the median manager by 80-120 fantasy points across the season. That is the size of edge that converts free contests into real payouts.