A working archive of recent Jeeto11 contest winners, with their pick rationale and the contest format they played. We publish only after the contest is settled.
A winner is a contestant whose XI outscored the field. The desk publishes winners with the contest format they played, the size of the contest, and the headline pick that drove their score. We do not publish the contestant’s identity beyond their handle; the wallet settlement is between the contestant and the operator.
The desk reads winners for two things: which selection patterns reward the contest format, and which contest formats reward the captaincy method. The archive on this hub is sorted by week; the format-wise read is below.
Five recent contests, with the format, the headline pick and a one-line note on what drove the score.
| Week | Contest | Format | Headline pick | What drove the score |
|---|---|---|---|---|
| Week 11 | Chennai vs Mumbai | League | Finger-spinner (C) | 3-wicket haul + powerplay wickets |
| Week 10 | Bengaluru vs Hyderabad | 50/50 | Top-order batter (VC) | 1.5x multiplier on a steady 60 |
| Week 9 | Kolkata vs Delhi | League | Death pacer (C) | Yorker bonus on the final over |
| Week 8 | Rajasthan vs Punjab | Head-to-head | All-rounder (C) | 2x multiplier on a fifty + 2 wickets |
| Week 7 | Lucknow vs Gujarat | Marquee | Power-hitter (C) | Six-bonus compound across the round |
The leaderboard teaches the same lesson over and over: the captain pick matters more than the rest of the XI combined. A 2x on a player who outscores the field by 30 points is worth more than a steady XI across eleven players. The desk reads this as a strong argument for high-conviction captaincy picks in low-variance formats and conservative picks in high-variance formats.
Three patterns we see in the archive:
No. The desk publishes the handle, the contest format and the headline pick. The wallet settlement is between the contestant and the operator.
The desk publishes winners from contests with at least 100 entries. Smaller contests are settled, but the archive focuses on the patterns the desk reads across the field.
Yes. Each archive entry carries the contest size alongside the format.
Yes. The desk takes removal requests through the customer-care channel.
The desk republishes the archive weekly, with a “Last updated” timestamp on the page.
Set the wallet, pick the contest, lock the XI. The desk does the reading.