How the live-matches desk works
The Fantoss live-matches desk tracks every match in real time — scorecard, fall of wickets, captain multiplier, economy bonus triggers. The match brief stays open in a side panel so you can re-read the toss logic when the dew settles. This page lists today's fixtures, the in-play captain switches and the live momentum reads.
At a glance
Today's fixtures
Three to five fixtures per match day
Today's fixture list is published inside the lobby at 9 AM and updated whenever the schedule changes. Each fixture links to the match brief, the probable XI, the venue notes and the desk's captain pick.
Double-headers and rain-reserve days are flagged in the lobby. The desk surfaces the day-night distinction in the brief — dew is a factor in day-night matches; weather is the second variable.
Each fixture has a live ticker that updates after every over. The ticker shows the score, the run rate, the required rate and the captain's contribution. The ticker also surfaces the next bowler's name and the upcoming batter.
In-play captain switches
When to captain a player whose role changed mid-match
The impact-player rule (IPL only) allows each team to substitute one player from a list of four substitutes at any point during the match. The desk flags likely impact-player swaps in the brief — they can affect the captain pick if a player is unlikely to bat or bowl.
If your captain is the likely impact-player substitute, the desk surfaces the risk. Consider vice-captaining the impact player instead — the 1.5x multiplier is better than losing the 2x.
In-play captain switches are not supported in the Fantoss lineup. The captain pick is locked at the deadline. Read the brief carefully before locking — the desk flags likely XI changes within five minutes of the toss.
Each fixture has a live ticker that updates after every over. The ticker shows the score, the run rate, the required rate and the captain's contribution. The ticker also surfaces the next bowler's name and the upcoming batter.
If your captain is the likely impact-player substitute, the desk surfaces the risk. Consider vice-captaining the impact player instead — the 1.5x multiplier is better than losing the 2x.
A high run rate with a low required rate is a momentum shift in favour of the batting side. A spate of wickets in the middle overs is a momentum shift in favour of the bowling side.
Dew is the most underestimated weather variable. A wet ball is harder to grip; spinners and seamers both struggle. The captain pick may shift to a top-order batter if dew is expected to settle in the second innings.
Today's fixture list is published inside the lobby at 9 AM and updated whenever the schedule changes. Each fixture links to the match brief, the probable XI, the venue notes and the desk's captain pick.
Rain delays are flagged in the brief within 30 minutes of the official announcement. If the match is reduced to a specific number of overs, the desk updates the captain pick logic — the captain pick may change because the role distribution shifts.
Partnerships are the most underrated variable. A 50-run partnership in the middle overs is worth more than a 30-run partnership in the powerplay because the run rate is higher. The desk cites the partnership data in the brief.
Where can I see the next bowler's name? In the live ticker. The ticker shows the next bowler's name, the upcoming batter and the captain's contribution.
Reading momentum mid-innings
Run rate, required rate, fall of wickets, partnerships
Momentum is read through four variables — run rate, required rate, fall of wickets and partnerships. The desk surfaces the relevant variable in the brief and in the live ticker.
A high run rate with a low required rate is a momentum shift in favour of the batting side. A spate of wickets in the middle overs is a momentum shift in favour of the bowling side.
Partnerships are the most underrated variable. A 50-run partnership in the middle overs is worth more than a 30-run partnership in the powerplay because the run rate is higher. The desk cites the partnership data in the brief.
Weather alerts and rain delays
Dew, rain, reduced overs
Weather is the second variable after the pitch. Overcast skies help the seamers; bright sunshine helps the batters. Dew is a factor in day-night matches — the side batting second gets a wet ball that is harder for the bowlers to grip.
Rain delays are flagged in the brief within 30 minutes of the official announcement. If the match is reduced to a specific number of overs, the desk updates the captain pick logic — the captain pick may change because the role distribution shifts.
Dew is the most underestimated weather variable. A wet ball is harder to grip; spinners and seamers both struggle. The captain pick may shift to a top-order batter if dew is expected to settle in the second innings.
Frequently asked questions about live matches
Frequently asked questions
How often does the live ticker update?
After every over. The scorecard also surfaces the captain's contribution within two seconds of the broadcast feed.
Can I switch my captain in-play?
No. The captain pick is locked at the deadline. Read the brief carefully before locking — the desk flags likely XI changes.
How does the desk handle rain delays?
Rain delays are flagged within 30 minutes of the official announcement. If the match is reduced, the captain pick logic is updated.
What is a momentum read?
A momentum read is the desk's take on which side is in control. The read is published in the brief and updated in the live ticker.
How does the desk handle the impact-player rule?
Impact-player swaps are flagged in the brief. If your captain is the likely impact-player substitute, the desk surfaces the risk.
Where can I see the next bowler's name?
In the live ticker. The ticker shows the next bowler's name, the upcoming batter and the captain's contribution.
Each fixture has a live ticker that updates after every over. The ticker shows the score, the run rate, the required rate and the captain's contribution. The ticker also surfaces the next bowler's name and the upcoming batter.
Yes — see the FAQ list above for the full answer.
