LAN vs DER Dream11 Prediction — Match 85, T20 Blast 2026 at Old Trafford: Captain Picks, Playing XI, Pitch Report & MyTeam11 XI

CricTracker's 6 July 2026 fantasy preview of North Group Match 85 of the Vitality Blast 2026 between Lancashire and Derbyshire at Emirates Old Trafford, Manchester, first ball 11:00 PM IST. Liam Livingstone is the safe captain on the back of a 47 off 31 against Nottinghamshire, AHT Donald is the risky captain, Tom Hartley and James Anderson form the Lancashire seam-plus-spin axis, and the Old Trafford forecast — 21.6°C, cloudy, 61% humidity — sets up a bat-first toss decision that both captains are expected to take. Here is how to translate that read into a working MyTeam11 lineup before the 10:30 PM IST lock window closes.

Match card, lock window and where the table sat

CricTracker's match card frames the fixture as LAN vs DER, Match 85 of the T20 Blast 2026 North Group, at Emirates Old Trafford in Manchester, with the first ball scheduled for 11:00 PM IST on Monday 6 July 2026. The lineup screen on MyTeam11 closes 30 minutes before the toss, which puts the lock at 10:30 PM IST — late enough that lineup builders who wait for the toss decision can still make captain moves, but early enough that the XIs have to be templated in advance rather than built from scratch at the buzzer. The match was scheduled to be broadcast and live-streamed on YouTube, which gives the wider Indian audience an evening crossover fixture rather than a red-eye start.

The table context for both sides going into the fixture was sharply asymmetric. Lancashire sat third in the North Group with 16 points after winning four of their first nine matches, anchored by the Livingstone top-order show against Nottinghamshire and a death-overs economy that has held through the middle of the competition. Derbyshire sat bottom of the North Group with only two wins in the tournament and a 4-run loss to Lancashire when the two sides met earlier in the group — chasing 205 and falling four short — which gave the CricTracker read its underlying assumption that the Lancashire side is the favourite at home but not by enough margin to justify loading the lineup with six Lancashire batters and three Derbyshire tail-end bowlers.

Probable XIs: Lancashire and Derbyshire

CricTracker's probable Lancashire XI reads MA Jones and KK Jennings (captain) at the top, LS Livingstone at three, BR McDermott behind the stumps, J Moores, SH Khan, Matthew Hurst, JM Blatherwick, T Hartley, Tom Aspinwall and James Anderson to round out a batting-plus-bowling split that gives Lancashire seven frontline batting options and four frontline bowling options including the spin of Hartley alongside the pace of Anderson and Blatherwick. The shape is a recognised T20 Blast template — keeper at four, two overseas-or-domestic all-rounders in the middle, two frontline pacers and a left-arm spinner — and the captaincy sits with Jennings rather than Livingstone despite the latter being the marquee fantasy name, which is the kind of internal rotation that Lancashire have run for the past two seasons.

Derbyshire's probable XI is AHT Donald (captain), MK Andersson, Yousaf Bin Naeem, WL Madsen, M Montgomery, RA Whiteley, Amrit Basra, Nick Potts, Ben Aitchison, Akif Javed and Mohammad Abbas. The composition gives Derbyshire an overseas seam trio of Aitchison, Akif Javed and Mohammad Abbas to share the new ball and the death overs, which is the clearest seam-bowling edge on either side and the reason CricTracker names the seam attack rather than the top order when describing where Derbyshire's contest ceiling actually sits. Donald at the top is a captain pick for ownership differential reasons rather than ceiling — the 6:5 head-to-head Mega League record cited in the preview is led by Lancashire but is tight enough that any Donald-led Derbyshire win still pays out at fixture-level ownership premiums.

Safe captain pick: Liam Livingstone

CricTracker names Liam Livingstone as the safe captain and the reasoning is supported by his most recent match — a 47 off 31 balls in the 1-run defeat to Nottinghamshire while chasing 181, top-scoring for Lancashire in a chase that fell one run short. 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. Picking Livingstone at the 2x multiplier captures the role-and-form combination that small-league and head-to-head contests reward: a top-order batter who can clear the rope at Old Trafford's short straight boundary, a part-time off-spinner who picks up 1 to 2 wickets when the captaincy gives him a powerplay over, and a fielder whose catching points add a third scoring category on top of the batting and bowling.

The ownership math behind the safe captain pick matters as much as the player logic. On a North Group fixture where Lancashire are favourites, the obvious captain ownership band tends to settle in the 45 to 60 percent range when the lineup window opens and drift down toward 30 to 45 percent by lock as the field splits between Livingstone and the differential captain. Picking Livingstone at that ownership 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 your core lineups but should not be the only captain combination you run across a multi-lineup portfolio.

Risky captain pick: AHT Donald

The risky captain is AHT Donald — Derbyshire's captain and top-order batter. The shape of the pick is a high-variance differential captain on the side most likely to lose: when Donald fires he fires at a strike rate no equivalent-credit batter can match, the boundary bonuses stack quickly, and a 60-plus captain haul is what mega contests reward when ownership stays below the 10 percent band. 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, which is exactly the kind of variance a single-lineup head-to-head entry cannot absorb.

Donald as the contrarian captain is a thinking pick rather than a vibes pick. His value against a Lancashire attack that includes James Anderson and Tom Hartley comes from the right-handed top-order aggression that has historically rewarded Derbyshire openers when they take the powerplay on, particularly at Old Trafford where the square boundaries sit short enough that an over of 12 to 15 runs is achievable from the first six balls. The realistic ceiling is a 55 to 70 captain haul with a boundary count above six, which multiplied by 2x pushes a strong differential entry into the top percentile of mega contests. The realistic floor is 5 to 10 points on a low-score dismissal. 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 Livingstone combination fills 3 or 4 entries and the risky Donald combination fills the remaining 2 or 3.

Reading the Old Trafford pitch and the 21.6°C cloudy forecast

CricTracker's pitch read describes Emirates Old Trafford as excellent for batting with some assistance for pacers, with both captains likely to choose to bat first after winning the toss. The forecast supports that read — 21.6°C, cloudy, 61% humidity — which is the kind of overcast Manchester evening where the ball nibbles off the surface for the first two or three overs, the ball comes onto the bat nicely under lights once the cloud cover thins, and a total in the 175 to 195 band tends to be par rather than chased down comfortably. For MyTeam11 purposes the predicted toss decision shapes which slots actually pay: a bat-first innings favours the top-order batting captain and the powerplay seamers who pick up early swing, while a successful chase lifts the middle-overs spinners and the death-overs finishers.

The conditions argue for a balanced XI rather than a top-heavy batting stack. Lancashire's Tom Hartley has been rewarded at Old Trafford by the surface's left-arm spin grip in the middle overs, and Anderson's historical record at the ground — across Tests, ODIs and T20 Blast — is the kind of swing-bowling edge that turns a 30-point seam spell into a 50-point matchup haul when the cloud cover holds. For Derbyshire, Mohammad Abbas and Akif Javed offer similar new-ball discipline with the ball likely to move laterally for the first six overs, and a 2-to-3 wicket combined spell is a realistic ceiling against a Lancashire top order that has been one of the strongest in the North Group.

Two working MyTeam11 lineups from the probable XIs

CricTracker's suggested XI translates into a working MyTeam11 lineup that satisfies the role cap: a 1 wicketkeeper / 4 batter / 3 all-rounder / 3 bowler split with BR McDermott behind the stumps, MA Jones, KK Jennings, LS Livingstone and M Montgomery in the batting block, SH Khan, WL Madsen and RA Whiteley as the all-rounder trio, and T Hartley, Tom Aspinwall and Mohammad Abbas as the bowling unit. The structure keeps the captaincy on Livingstone and the vice-captaincy on SH Khan — whose left-arm spin into Derbyshire's right-handed middle order is the cleanest matchup edge available on this fixture — and leaves a credit differential of roughly 0.5 to 1.5 for a bench slot or a flex upgrade.

A second lineup for multi-entry portfolios swaps M Montgomery for AHT Donald at the top of the order, demotes Khan from vice-captain to a plain slot, and shifts the captaincy to the risky Donald pick. The role split moves to 1 keeper / 4 batter / 2 all-rounder / 4 bowler, which gives the lineup an extra seamer — typically James Anderson or Akif Javed — at the cost of an all-rounder. The trade-off is a cleaner seam matchup against a possible Derbyshire top-order wobble and a lower captain ownership, which is the right structure for a mega-contest portfolio in which the safe lineup carries the consistent small-league entries and the differential lineup carries the upside mega entries.

Reading the head-to-head and the team-form ledger

The head-to-head Mega League record cited by CricTracker sits at Lancashire 6 to Derbyshire 5, which is tighter than the table position implies and is the single most useful framing for fantasy lineups on this fixture. A 6:5 head-to-head with home advantage suggests the underlying expected win probability sits in the 55 to 60 percent band for Lancashire rather than the 70 percent+ that the table position alone would imply, which is the difference between a confident favourite and a side whose recent loss to Nottinghamshire by 1 run chasing 181 is a reminder that the same Lancashire side can collapse from a winning position. The implication for MyTeam11 is that the lineup should not assume a Lancashire win — at least one Derbyshire batter should be in every multi-lineup portfolio, and at least one Derbyshire seamer should be in the differential entry.

The team-form ledger for the previous five matches reads Lancashire L W W L L and Derbyshire L T W L L, with Lancashire's most recent defeat being the 1-run loss to Nottinghamshire while chasing 181 and Derbyshire's most recent result being a 4-run loss to Lancashire while chasing 205. The W in Derbyshire's column is the more interesting data point: a win over anyone in this North Group gives the Donald-led side a template to follow, and the CricTracker preview leans on that data point when it names Donald as the risky captain rather than a pure differential punt. The L in both columns at the tail of the form ledger is the equally useful negative data point — both sides lost their most recent match, which means the lineup window opens with no recent winning momentum on either side and the captain pick has to be made on role-and-matchup rather than form tail.

Final-30-minute decisions: toss, confirmed XI and weather update

Two final-30-minute decisions move the lineup more than any pre-toss templating. First, the toss: both captains have rotated players through the group stage, and the CricTracker preview expects both captains to bat first if they win the toss, which means the lineup should pre-template two batting-first XIs and one bowling-first XI rather than committing to one structure pre-toss. Second, the confirmed playing XI: CricTracker's probable XIs are 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.

The third decision is weather. The 21.6°C cloudy, 61% humidity forecast is the expected state, but a heavier rain band pushing in from the Pennines could shorten the match to a five-over shootout, which would change the captain math entirely — a five-over game favours the powerplay batters and the specialist death-over bowlers, with captain ownership consolidating around three or four names rather than the dozen who become relevant in a full 20-over game. The MyTeam11 lineup builder who watches the toss announcement, the confirmed XI, and the radar at 10:25 PM IST before locking at 10:30 PM IST has a measurable edge over the lineup builder who locks at 8 PM and walks away. For readers who want to read the captain math, contest split and bankroll discipline framework that drive most of our fantasy coverage, the rest of the fantasy tips articles on MyTeam11 walk through the safe-versus-risky captain rotation, the 60-25-15 entry split that survives a single bilateral T20I, and the unit-size rules that make a multi-lineup portfolio on this fixture sustainable.

Frequently asked questions