Pick the right wicketkeeper on CricArena. Compare catch and stumping bonus math, ownership cap rules, and captain-pair frameworks across Dream11, MyTeam11, Gamezy, and My11Circle for IPL 2026.
· CricArena Fantasy Desk
Most fantasy managers treat the wicketkeeper slot as a one-dimensional pick: choose the gloveman with the best batting position, ignore the fielding math, move on. That works for casual contests. For sharper contests on CricArena, the keeper slot is where league-winning edge hides, because no other role combines a guaranteed batting opportunity with a stumping multiplier that almost no team-build spreadsheet accounts for. A captain-grade keeper can outscore a captain-grade all-rounder by 8 to 14 fantasy points per match purely from behind-the-stumps contributions, and the field rarely prices it in.
Across the four big Indian fantasy apps, the keeper scoring matrix differs in two specific ways: catch bonus (per catch behind the stumps or in the outfield) and stumping bonus (direct hit on a batsman stepping out of the crease). Dream11 awards 8 points per catch and 12 per stumping. MyTeam11 matches Dream11 on catches (8) but pays 12 per stumping with a 1.5x captain multiplier stacking. Gamezy runs lighter — 6 per catch, 10 per stumping. My11Circle uses a 4/8/12 stumping ladder tied to dismissal difficulty. If you captain a gloveman who takes 2 catches and 1 stumping on a turning track, the platform-level points range from 22 (Gamezy) to 38 (My11Circle captain at 2x). That is a 16-point swing for the same player, same match.
Batting average for a keeper is misleading because it conflates finishing-innings cameos with new-ball dismissals. A more useful filter is catches + stumpings per innings. On CricArena, the public profile data shows that high-volume glovemen average 1.4 to 2.1 dismissals per T20 innings. The threshold we use across platforms: a keeper averaging below 1.0 dismissals per innings is a batting-only pick, and a keeper averaging 1.4+ is a captain-grade gloveman. The 1.4+ bracket is small — typically 5 to 7 players per IPL season — and the field is slow to adjust when a new keeper enters the bracket mid-tournament.
The platform's player profile card shows per-match dismissal count. Cross-reference it with the bowling-side matchup: a keeper standing up to the stumps against a leg-spinner has a meaningfully higher stumping probability per delivery than one standing back to a pacer. We suggest you set a 1.4+ dismissals-per-innings filter for captain consideration and a 0.8+ filter for vice-captain consideration. Anyone below 0.8 is a punt, not a pick — pick the all-rounder in that slot instead.
Wicketkeepers tend to be over-owned relative to their ceiling because casual players copy the most-batted gloveman. On a 1-lakh-entry mega contest, a top-order keeper can be 30 to 45 percent owned. Captaincy at that ownership level caps your upside at the field's median, which is roughly the 50th percentile of the leaderboard. To outscore the field in a mega, you want a captain-grade keeper at 18 percent ownership or less — the differential sweet spot.
The 18 percent cap is a heuristic that emerged from the 2024 and 2025 IPL seasons. Below 18 percent, you get the upside of a captaincy pick without fading the entire field. Above 35 percent, you are paying the field's median for your captain slot. The platform's team-reveal feature after lock shows you ownership; some third-party tools project ownership before lock based on selection-rate trends. We suggest you set a personal rule: any keeper captain pick must be under 18 percent owned in a mega, and under 25 percent in a small league. If your keeper captain is owned higher than that, swap to the vice-captain.
Stumpings are the keeper equivalent of a wicket on a green seamer — a high-skill, low-frequency event that swings captaincy picks. On a Chepauk or Lucknow surface where spinners dominate, a keeper who stands up to the stumps turns 1.2 to 1.8 percent of deliveries into stumping opportunities. Across a 20-over T20 with 4 overs of spin from one end, that is 0.05 to 0.07 stumpings per match for a top-tier gloveman, or roughly 1 stumping every 14 to 20 matches. The math gets interesting when you stack it with catch probability: a keeper who takes 2 catches and 1 stumping on a turning track scores 28 to 36 points before batting is added, depending on platform.
Cross-platform math: on My11Circle's 4/8/12 ladder, a stumping dismissal on a 5-star difficulty delivery (e.g. leg-spinner with batsman charging) pays 12 points. On Dream11, the same dismissal pays 12 flat. On Gamezy, 10. On MyTeam11, 12 plus captain multiplier if you captain the keeper. Differential captaincy at a stumping-prone venue is the sharpest single-axis play in keeper selection, because the field's ownership data is least accurate on it.
Fantasy apps split keepers into two classes on the platform: WK-Bat (wicketkeeper-batsman, who bats in the top 7) and WK-Only (wicketkeeper-only, who bats 8 or lower). The class math matters because Dream11 and MyTeam11 give 4 bonus points for every 30-run boundary milestone (30/50/100), but a WK-Only rarely reaches those milestones. A WK-Bat who finishes on 35 not-out scores 4 extra points that a WK-Only cannot reach. The captain multiplier on a 35-no match: 4 × 2 = 8 points of platform bonus that you do not get on a lower-order gloveman.
On CricArena, the public salary data shows WK-Bat picks typically cost 1.2 to 1.8x more than WK-Only picks of comparable ownership. The question is whether the extra 8 to 14 points per match from batting milestones justify the salary burn. Across an IPL season, the breakeven is roughly: if your WK-Only scores 25 percent more dismissals per match than your WK-Bat, the WK-Only is the right pick. If dismissals are equal, the WK-Bat is the right pick. We use 1.4+ dismissals per innings as the threshold for switching the heuristic.
Pairing your captain with the keeper is a 4-step framework. First, identify the keeper with the highest expected dismissals on the specific matchup (spin-friendly pitch, weak batting opposition, dew factor all matter). Second, check ownership — if your keeper is over 18 percent owned in a mega, drop them to vice-captain. Third, check the venue profile: on a Chepauk/Lucknow/Ahmedabad surface, the keeper's stumping probability doubles. Fourth, cross-reference with bowling matchups: a pace-heavy opposition means more catches at the keeper's end; a spin-heavy opposition means more stumpings at the keeper's end.
The captain-pair rule: if your keeper is the captain, your vice-captain should be a top-order batsman with high boundary count, not a bowler. Bowlers' captain points are tied to wickets, which are lower-frequency than dismissals-per-innings. If your keeper is the vice-captain, your captain should be the tournament's top run-scorer, who is a near-certain pick for 1.5x or 2x multiplier stacking. The keeper-captain + top-run-scorer-vice-captain pair is the highest-EV combination across the four platforms for 2026.
The 30-minute pre-toss window is where sharp managers separate themselves. The platform allows 1 to 3 player swaps depending on contest type, and the keeper slot is the most valuable swap target. We suggest keeping a backup keeper slot open until toss for exactly this reason. If the announced XI has a different gloveman than expected, swap in the actual XI's keeper at lower ownership. If a key batsman is rested and the batting order shifts, the new keeper's batting position may improve — the swap target updates accordingly.
The cross-platform swap math: Dream11 and MyTeam11 allow 1 free swap in the pre-toss window for premium contests; Gamezy allows 2; My11Circle allows 1 plus a "pro" unlimited tier. The cost-benefit: a 1-swap window means you can adjust exactly one slot to actual playing XI. Use it on the keeper, not on a batsman. Batsmen's fantasy points are roughly correlated with public projection, so a small swap there gives small edge. The keeper swap, by contrast, swings ownership and dismissal probability in one move.
The IPL calendar has three keeper-relevant phases. The first 10 matches (March-April) feature squads finding their batting order; the keeper's batting position can shift week-to-week, so favor WK-Bat picks with strong T20 numbers. Mid-season (April-May) is when the tournament's top glovemen have established ownership and dismissal patterns; differential captaincy gets harder because ownership is more accurate. The final 4 weeks (May) are when playoff-bound teams rest fast-bowlers and play two spinners, raising stumping probability; favor WK-Bat picks on spin-friendly tracks.
After 20 matchdays, log your keeper picks' ROI by phase. The platform's profile page shows net points, but a finer weekly log is more useful. Anyone serious about the keeper slot tracks dismissals-per-innings, ownership percentage, and captain multiplier realized points. The pattern is clear after 30 matches: high-volume glovemen on turning tracks, captained at 18 percent ownership or less, return 12 to 18 percent above the field median. Anyone playing the slot as a single-axis pick leaves 8 to 14 points per match on the table. CricArena's contest lobby shows the data if you choose to look.
