WEF vs TRT Dream11 Prediction — Match 11 The Hundred Men’s 2026 at Sophia Gardens: Captain Picks & MyTeam11 XI

Cricket Addictor’s 29 July fantasy preview of the eleventh match of the English Men’s 100 League 2026 between Welsh Fire and Trent Rockets at Sophia Gardens, Cardiff, with the first ball scheduled for 7:30 PM IST. Ben Duckett is the safe captain pick with Rachin Ravindra as safe vice-captain; Finn Allen takes the differential tag and Phil Salt sits as a top-order anchor; Marco Jansen and Craig Overton are the budget pace options. Here is how a MyTeam11 lineup builder can convert that suggestion into a locked XI before the 7:00 PM IST lineup window closes.

Match card and the lock window

Cricket Addictor’s match card sets the fixture as WEF vs TRT, Match 11 of the English Men’s 100 League 2026, at Sophia Gardens in Cardiff on 29 July 2026, with the first ball at 7:30 PM IST. The Hundred’s 100-ball format compresses a full T20 contest into roughly 65 to 75 minutes of cricket, which compresses the lineup window in the same proportion. MyTeam11 locks fantasy teams 30 minutes before the first ball, which puts the deadline at 7:00 PM IST, and every captaincy and role decision has to be made on the basis of the 29 July published preview rather than on rumours from the nets on the afternoon of the match.

Sophia Gardens is a familiar surface for both squads in mid-summer. The straight boundary sits around 60 metres, the square is a touch shorter on the leg side, and the average first-innings score at the venue in this competition has settled around 146 in the data Cricket Addictor references. Cardiff’s late-July weather is overcast and around 19 degrees Celsius, which historically has helped pace bowlers who can move the ball off the seam in the first six balls of an innings. The Hundred’s 100-ball structure also rewards captains who can produce one big over rather than accumulate steadily across a long T20 — that single-over ceiling is the largest reason Cricket Addictor lands on Ben Duckett at the top of the safe list rather than a death-overs finisher.

Safe captaincy: Ben Duckett and Rachin Ravindra

The safe captain pick on MyTeam11 is Ben Duckett and the safe vice-captain is Rachin Ravindra. The reasoning behind both names is identical and worth spelling out for lineup builders who do not follow this format closely. A captain on MyTeam11 earns 2x on the player’s actual score and a vice-captain earns 1.5x, which together make the captaincy pair responsible for a much larger share of a lineup’s expected return than any other two slots. Naming a top-order left-hander who has scored 124 runs in two innings atop the tournament run charts as captain, and an in-form New Zealand all-rounder with 122 runs including a 98 off 44, hedges the batting ceiling on both sides of the contest.

Duckett’s ownership math is the central plank of the safe call. At a Cardiff 100-ball game where Trent Rockets are slight favourites, captain ownership on the obvious English opener tends to settle in the 45 to 60 percent band when the lineup window opens, and drifts down toward 35 to 50 percent by lock as the field splits between the safe captain and a differential. Picking Duckett at that ownership level captures the 2x multiplier on the most likely strong performer without paying the full-correlated-field penalty, which is the optimal position for head-to-head and small-league contests. For mega contests, the same safe pair is the right anchor in the core lineups but should not be the only captain combination you run across a multi-lineup portfolio.

Ravindra’s fit as vice-captain is the slot first-time MyTeam11 players tend to under-rate. The 98 off 44 he has already produced in this tournament is the largest single-innings ceiling any Welsh Fire batter has shown, and his left-arm spin gives him a second scoring lane on a Cardiff surface that grips a touch in the second half of the innings. Ravindra typically gives you 2 to 4 overs in the middle phase, with catching points on top of any wicket bonus — the dual-category scoring that holds multi-lineup portfolios together when the captain pick goes cold. The 1.5x vice-captain multiplier on a 30 to 45-point all-rounder performance is the single most efficient slot-filling on this XI.

Risky captaincy: Finn Allen and Phil Salt

Cricket Addictor’s risky captain is Finn Allen and the risky vice-captain is Phil Salt. The shape of the pick is a high-variance Kiwi opener paired with a Welsh Fire top-order anchor — a combination you only reach for when chasing top-one-percent finishes in mega contests rather than steady small-league or head-to-head wins. Allen’s profile is the obvious upside: when he fires he fires at a strike rate no equivalent-credit batter can match, and his 43 off 17 in the previous fixture is the form reference Cricket Addictor leans on. The downside is that the same profile that produces a 90-point captain explosion also produces a 12-point captain zero when the batter does not get in.

Salt as the contrarian vice-captain is a thinking pick rather than a vibes pick. His value comes from anchoring the Welsh Fire powerplay on a Cardiff surface where chasing teams have won only 46 percent of recent games, which means the team batting first typically posts the larger total. Salt’s 53 runs at the top of the order in his most recent innings is the floor, and the ceiling sits closer to 70 to 80 with a set batter going deep in a 100-ball chase. The realistic captaincy window is a 60 to 90-point vice-captain return; the realistic floor is 15 to 20 on a top-order failure.

The risky pair is strictly a mega-contest play and should never be the only lineup you enter. The discipline that holds up under variance is to run a 5-to-7-lineup portfolio in which the safe captain combination fills 3 or 4 entries and the risky combination fills the remaining 2 or 3. That structure captures the upside of an Allen explosion on the entries where it lands without exposing your entire bankroll to the variance of a single captain pick on a one-off midweek 100-ball game.

Two suggested MyTeam11 XIs for the lock window

Cricket Addictor’s first suggested XI reads Keepers Sam Billings, Phil Salt, Jordan Cox; Batsmen Joe Root, Ben Duckett (C), Finn Allen, Tom Banton; All-rounders Matthew Short, Rachin Ravindra (vc); Bowlers Mohammad Amir, Lockie Ferguson. That is a 3-4-2-2 role split with the captaincy combination sitting on Duckett and Ravindra, and the lineup leans on a deep batting core to absorb a single top-order failure. The second XI swaps the captaincy to Finn Allen with Phil Salt as vice-captain and adds Craig Overton to the all-rounder block at Marco Jansen’s expense — a 3-3-3-2 split that pays for higher ceiling on the captain slot and gives the bowling attack an additional left-right variation.

The most interesting lineup decision inside either XI is the all-rounder block. MyTeam11 prices all-rounders higher than equivalent-role players because they score in two categories, and Matthew Short typically sits 1.5 to 2 credits above a comparable pure batter. The trade-off works out cleanly on a single-entry build: his off-spin gives you 2 overs of middle-phase control that historically pick up a wicket or two on this surface, and his batting at number 4 gives you a ceiling most bowling picks cannot match. On a 7-lineup portfolio the math gets tighter — you can drop the Short premium on 2 or 3 lineups and replace him with a cheaper differential or a higher-ceiling bowler depending on the contest type.

Marco Jansen and Lockie Ferguson fill the bowling block alongside Mohammad Amir in XI-1, with Craig Overton replacing Jansen in XI-2. Jansen is the left-arm pace pick whose 3-wicket match in the previous fixture is the recent-form anchor; Ferguson is the right-arm pace differential whose death-overs economy is the upside; Amir is the new-ball swing option who historically exploits overcast conditions at Sophia Gardens. The XI-2 swap of Overton for Jansen is the more aggressive call — Overton’s late boundary in his previous innings is the small-sample evidence Cricket Addictor leans on, and the credit saving lets you upgrade a role slot elsewhere.

Players to avoid: Jason Roy and Tymal Mills

Jason Roy and Tymal Mills are the two names Cricket Addictor flags to avoid in Match 11, both carrying NA fantasy credits and NA last-match points. The reason both names come up is credit efficiency rather than form alone: at NA credits a player has not yet produced a stable fantasy baseline in this tournament, and the last-match NA confirms they have either not played a completed innings or were rotated out for tactical reasons. On a MyTeam11 lineup the unpredictable-credit slot is the most contested place in the budget because it sits between the proven core and the value picks, and picking the wrong player in that slot typically costs 10 to 15 lineup points across a contest.

The cleaner alternatives in the same credit band are the players on Cricket Addictor’s XI who fall at or below the mid-tier line. Joe Root and Tom Banton are the two clearest swaps: Root gives you a stabilising top-order anchor on a Cardiff surface where chasing teams win less often than batting-first teams, and Banton brings the strike-rate ceiling you want in a 100-ball chase. Both have a locked role in the XI and a recent three-innings window that supports the credit price. If you want to stay closer to the public suggestion while still respecting the avoid list, swapping Roy for Tom Banton and Mills for Mohammad Amir clears the flag without disturbing the role split.

Reading the match prediction for your lineup

Cricket Addictor frames Trent Rockets as the predicted winner of Match 11, which is consistent with the head-to-head record at Sophia Gardens and the wider odds movement on 100-ball games between the two sides. The 5-match head-to-head record sits at 4 wins for Welsh Fire and 1 for Trent Rockets, which complicates the prediction slightly because the recent form ledger is shorter than the older H2H sample. For MyTeam11 purposes the predicted winner matters less than the predicted margin, because the margin shapes which slots actually pay. A tight Trent Rockets win favours higher individual ceiling returns for the captain pick and reinforces Allen’s strike-rate ceiling; a dominant Trent Rockets win suppresses captain variance and rewards the death-over bowlers and the catching all-rounders instead.

The lineup structure that pays off in both shapes is to take a safe captain from the slight favourite, anchor two all-rounders in the middle, fill the bowling slots with at least one wicket-taking differential, and leave at least one Welsh Fire player in the order to capture the upside if the home side gets off to a fast start. That structure costs you a small amount of captain ceiling in the dominant-win scenario but protects you from a complete captain zero when the toss goes against you. The biggest MyTeam11 lineup risk on this fixture is not picking the wrong captain — it is locking the rest of your XI in before the toss and missing the rotation picture that both teams have shown in the opening round.

Match-up inputs to track in the final 30 minutes

Two match-up inputs should move your lineup before lock. First, the toss: both teams have rotated players across the opening round, and the batting order in the 29 July preview could shift if a coach decides to rest a frontline bowler or promote a middle-order player up. Second, the confirmed playing XI: Cricket Addictor’s suggestion is a starting point, not a confirmed XI, and the right thing to do in the final 30 minutes is to wait for the toss announcement, lock your captain pick from the confirmed opening pair, and adjust the lower-order slots around that confirmation rather than the published XI.

For readers who want to read the suggestion back through the broader captain math, contest split, and bankroll discipline framework that drive most of our fantasy coverage, the wider fantasy tips on MyTeam11 walk through the safe-versus-risky captain rotation, the 60-25-15 entry split that survives a one-off 100-ball game, and the unit-size rules that make a multi-lineup portfolio on this fixture sustainable.

Frequently asked questions