The lab's today slate
Today's fixtures, with live fantasy-point updates synced ball-by-ball to the PlayExch dashboard. The slate covers IPL, T20 internationals, and bilateral series.
IPL — Match 47
MI vs CSK, 7:30 PM IST, Wankhede. The lab leans toward a CSK top-order stack on a turning Wankhede surface. Differential captain: Devon Conway at 8% ownership. Watch the dew factor in the second innings.
T20 International — 2nd T20I
IND vs AUS, 7:00 PM IST, Mohali. Lab picks Yashasvi Jaiswal as captain (high recent form, ownership under 25%). Death-bowling stack with Bumrah + Bishnoi remains the safer differential.
SA20 — Match 12
DSG vs MICT, 9:00 PM IST (5:30 PM SAST), SuperSport Park. Lab flags the surface as batting-friendly with a small spin advantage. Captain pick: Heinrich Klaasen at 12% ownership.
The Hundred — Match 18
OVI vs TRT, 11:30 PM IST (7:00 PM BST), The Oval. Lab picks a Trent Rockets all-rounder stack — Rashid Khan as differential captain at 7% ownership. The Hundred's 20-ball innings rewards aggressive top-order picks.
The lab's tomorrow slate
Tomorrow's fixtures, with pre-match captain reads and squad-construction guidance. The slate updates every evening at 10 PM IST.
IPL — Match 48
RCB vs KKR, 3:30 PM IST, Chinnaswamy. The lab flags a Chinnaswamy flat track where RCB top three should dominate. Captain pick: Virat Kohli (consensus) or Faf du Plessis (differential). Run-heavy build recommended.
T20 International — 3rd T20I
IND vs AUS, 7:00 PM IST, Bengaluru. The lab covers the probable XI after the toss. Captain picks lean toward the in-form player — Jaiswal if he fires at Mohali, otherwise Ruturaj Gaikwad.
CPL — Match 22
SLK vs BR, 8:30 PM IST (11:00 AM AT), Daren Sammy. Lab flags the venue's spinner-friendly surface. Differential captain: Akeal Hosein at 9% ownership. The death-bowling stack is the safer build.
BBL — Match 5
SYS vs MLS, 1:45 PM IST (7:15 PM AEDT), SCG. Lab picks a Sydney Sixers top-order stack on a batting-friendly SCG surface. Captain: Steve Smith at 14% ownership.
Ball-by-ball fantasy point sync
The lab's live-match dashboard syncs fantasy points ball-by-ball. The sync latency is under one second during business hours. Off-hours latency can stretch to three seconds.
From the live desk
Yesterday's biggest international T20 fixture, with the partnership math, the chase curve and the captain read for the rest of the tour.
Kishan and Tilak Varma lead India to 219/5 in 2nd T20I against Zimbabwe at Harare
Ishan Kishan's 81 and an unbeaten 60 from vice-captain Tilak Varma lift India to 219/5 at the Harare Sports Club on 25 July 2026, recovering from a 29/2 wobble after Zimbabwe asked them to bat first. The lab's partnership math, the chase curve, and the captain read for the rest of the tour are inside the match note.
Live Matches questions, answered
The most common questions about live matches on PlayExch, with detailed answers.
What matches does the lab cover?
IPL, T20 internationals, bilateral series, The Hundred, SA20, CPL, BBL, and PSL. Coverage depth varies — IPL and T20 internationals receive full coverage; bilateral series receive captain-pick coverage.
How fast is the live sync?
Under one second during business hours. Off-hours latency can stretch to three seconds. The methodology page publishes the latency benchmark.
Can I track multiple matches?
Yes. The dashboard supports multi-match tracking. Readers with entries in multiple matches can see all matches on one screen with a quick-jump to the per-match view.
Does the lab send captain alerts?
Yes. The dashboard sends a push notification when the captain's projected points cross a threshold (default 50 fantasy points). The threshold is configurable.
What happens if I miss a match?
The dashboard archives every match's live data for ninety days. Archived matches can be replayed ball-by-ball. The fantasy points are final once the match is closed.
See the decision from three angles
These visuals connect the page topic to the evidence, decision and safety checks readers should make before acting.
Ready to start with PlayExch?
Read the lab reports, pick a contest tier, run ten squads with the captain reads, and audit your ROI after fifty contests.
The lab's deeper perspective on live-matches
Beyond the headline content, the lab's editorial team publishes a longer read on the underlying dynamics, the historical context, and the future direction.
Historical context
The fantasy cricket market has evolved through three phases. Phase 1 (2008-2015) was the early-adopter phase — Dream11 was the dominant operator and the captain-pick methodology was largely gut-driven. Phase 2 (2016-2022) was the data-driven phase — operators introduced live-match data feeds and projection models became more sophisticated. Phase 3 (2023-present) is the transparency phase — readers demand methodology disclosure, hit-rate auditing, and assumption-risk documentation. The lab was founded in 2023 to serve Phase 3 readers.
Underlying dynamics
The underlying dynamics of fantasy cricket are driven by three forces. The first is the ownership distribution — when ownership spikes, the differential edge compresses. The second is the venue read — venue-aware picks outperform venue-blind picks by 11 points in hit rate. The third is the form curve — recent form is a stronger predictor than career average. The lab's research covers all three forces in depth.
Future direction
The fantasy cricket market is moving toward three futures. The first is increased regulation — state gaming authorities are tightening the rules around paid contests. The second is increased transparency — readers demand methodology disclosure and hit-rate auditing. The third is increased automation — AI-driven captain picks and squad optimization are becoming mainstream. The lab is positioned for all three futures.
Lab's editorial position
The lab's editorial position is that fantasy cricket is a research-grade problem. Captain picks are not gut calls — they are data-driven decisions backed by methodology, dataset versioning, and assumption-risk documentation. The lab's editorial principles are published on the owner page. The lab's editorial standards are reviewed quarterly by the editorial board.
The lab's extended perspective
A longer-form walk-through of the underlying dynamics, the data behind the recommendations, and the lab's analytical approach.
Methodology in depth
The lab's methodology is built on a five-stage pipeline. Every published report passes through framing, dataset pull, analysis, assumption-risk documentation, and re-test. The pipeline is published in full on the methodology page. The lab's edge comes from data freshness and analyst expertise, not from a secret formula. Other analysts can re-run the experiments with the published datasets and the published model code. The lab publishes every dataset version and every model version. The lab never quietly updates a dataset after the conclusion lands.
Data sources in depth
The lab pulls data from four primary sources. Match data comes from official tournament data partners, cross-checked against broadcast records. Ownership data comes from public contest-platform feeds, sampled every 30 seconds during contest open windows. Contest result archives come from publicly published leaderboards. Self-collected squad logs come from volunteer readers who submit their picks at lock time. Each source has a published quality score and a published latency benchmark. The lab's data-quality framework is reviewed quarterly by the statistics team.
Reader-safety commitments
The lab's reader-safety commitments cover deposit limits, self-exclusion, play-time alerts, loss trackers, cool-down reminders, and family-controls integration. The lab publishes the safety commitments on the responsible-play page. The lab refuses to partner with operators that do not enforce responsible-play defaults. The lab's reader-safety framework is reviewed annually by an external auditor.
Editorial principles
The lab operates by five public editorial principles. No sponsored picks — no contest operator, brand, or individual can pay the lab to feature a captain pick. Methodology is public — every model's code is published on the methodology page. Misses are published — every Monday morning the lab publishes the previous week's misses alongside the hits. Reader-funded economics — the lab's long-term economics rely on reader subscriptions and contest-entry referrals, not on advertising. Responsible play by default — every contest lobby on the lab's partner platforms shows a responsible-play banner.
Quarterly transparency
Every quarter the lab publishes a transparency report covering methodology changes, hit-rate recalibrations, partner-operator relationships, and revenue mix. The report is published on the 15th of the month following quarter end. The most recent report covers Q1 2026 and shows a 61% captain hit rate over the trailing 90 days, a 48/47/5 revenue split between subscriptions, referrals, and other, and four partner operators. The report is available on the disclosure page.