It's a Tuesday evening in Andheri. The Mumbai Indians are chasing 187 against Chennai at Wankhede. Your mate Arjun leans over from the sofa, phone in hand, and asks: "What's this session market everyone keeps tapping?" You've seen the tab on the FairPlay app — "Session 1: Overs 1-6", "Session 2: Overs 7-12" — but never placed one. The match is live. The powerplay just ended. You need an answer before the next over starts.
What Session Betting Actually Means
Session betting — sometimes called over-under on a block of overs — is a market where you predict whether the runs scored in a defined slice of an innings will finish above or below a line set by the bookmaker. On FairPlay the standard slice is six overs. So Session 1 covers overs 1-6, Session 2 covers overs 7-12, Session 3 covers overs 13-18, and Session 4 covers overs 19-20 (or 19-20 plus any super over if the format allows). You back Over if you think the batting side will exceed the line, Under if you think they will fall short.
The line moves as the game progresses. Before the first ball the line for Session 1 might sit at 48.5 runs. After two quiet overs it could drop to 42.5. After a six and a four in the third over it might climb back to 46.5. You can bet pre-session or in-play. The odds shift with every delivery. This is why the market feels faster than a match-winner bet — you get a result in thirty-six balls, not three hours.
FairPlay lists these markets under the cricket match page. Open the FairPlay cricket section, pick the fixture, and scroll past the match-winner and top-batsman tabs. You'll see "Sessions" or "Over/Under Sessions" depending on the tournament. Indian Premier League, Syed Mushtaq Ali, Tamil Nadu Premier League — all carry session lines. Domestic T20s sometimes use five-over blocks instead of six, so always check the header.
Walking Through One Innings Block by Block
Let's stay with that Tuesday chase. Mumbai need 187. Rohit Sharma and Ishan Kishan open. The Session 1 line opened at 48.5. You tap Over at 1.90 because the pitch looked flat in the warm-up and Chennai's new-ball bowler tends to leak width. First over: four singles, a wide, a dot — seven runs. Second over: Kishan pulls a short ball for six, then a single — eight runs. Running total fifteen after two. Third over: Rohit drives two fours through cover — thirteen runs. Total twenty-eight after three. You're already more than halfway to the line with three overs left.
Fourth over: Kishan skies one but the fielder drops it at long-on. Two runs. A dot. A single. Four runs off the over. Total thirty-two. Fifth over: Rohit sweeps a spinner for four, then rotates strike. Seven runs. Total thirty-nine. Sixth over: Kishan charges, misses, keeper fumbles — two byes. A wide. A four down the ground. Nine runs. Session 1 finishes at forty-eight runs exactly. The line was 48.5. Under wins. Your Over bet loses by half a run. That half-run margin is why the .5 exists — no push, no refund, just a clean result.
Now Session 2: overs 7-12. The line opens at 52.5 because the field spreads and spinners come on. Mumbai are 48 for 0 after six. You think the scoring rate will climb, so you take Over at 1.85. Seventh over: Rohit reverse-sweeps a four. Kishan hits a straight six. Fifteen runs off the over. Eighth over: a wicket — Kishan holes out. New batter Suryakumar Yadav takes a single. Eight runs. Ninth over: Rohit falls lbw. Two dots. Three runs. Tenth over: Surya finds gaps — four, two, single. Nine runs. Eleventh over: Tilak Varma joins, blocks three, singles two. Five runs. Twelfth over: Surya launches two sixes in the last three balls. Sixteen runs. Session 2 total: fifty-six runs. Over wins. Your ₹500 stake returns ₹925.
Session 3: overs 13-18. Line at 58.5. Mumbai now 104 for 2 after twelve. Required run rate creeping past ten. You like Surya at the crease, so you back Over again at 1.80. Thirteenth over: ten runs. Fourteenth: twelve. Fifteenth: Surya out caught at deep midwicket. Six runs. Sixteenth: new batter Pollard, two sixes, a four. Eighteen runs. Seventeenth: Pollard run out off a direct hit. Four runs. Eighteenth: tailenders scramble seven. Session 3 total: fifty-seven runs. Under wins by 1.5 runs. Another loss. The volatility is real — one wicket, one missed catch, one wide call swings the session.
Session 4: overs 19-20. Only twelve balls. Line at 22.5. Mumbai need forty-three off twelve. You stay away — too much variance, too little data. The match ends two balls early, Mumbai fall short by eight runs. Session 4 finishes at eighteen runs. Under would have won, but you didn't play. That restraint is part of the discipline session betting teaches.
Placing Your First Session Bet on FairPlay
Open the FairPlay app or site. Log in with your registered mobile — OTP arrives in seconds. Navigate to Cricket, pick the live match. Tap the Sessions tab. You'll see each block with its current line and two buttons: Over and Under. The odds sit beside each. Tap your choice, enter stake — say ₹200 — confirm. The bet slip shows potential return. If the session is already underway the odds update ball by ball. You can cash out early if FairPlay offers it for that market; the button appears on your active bets screen.
Deposits work via UPI, NetBanking, or the usual wallets. Minimum deposit is low enough for a first session punt. Withdrawals process back to the same method. Keep your KYC updated — PAN and Aadhaar — so payouts don't stall. If you hit a snag, the FairPlay customer support chat runs 24/7 in Hindi and English.
- Check the block length — six overs is standard but some domestic leagues use five.
- Watch the first two overs before committing; early wickets or boundaries move the line fast.
- Don't chase losses across sessions. Each block is independent.
- Use the cash-out only when the maths favours you, not out of panic.
- Set a session budget — say ₹1,000 for the whole innings — and stop when it's gone.
Common Mistakes to Avoid
First mistake: betting every session just because they're there. Four sessions per innings, two innings per match — that's eight decisions in one evening. Even sharp punters pick two or three spots where they have an edge. Second mistake: ignoring the pitch report. A Chepauk surface grips for spinners in Session 2 and 3; a Chinnaswamy belter keeps lines high all night. Third mistake: overreacting to one over. A sixteen-run over feels like a trend; often it's just one bowler having a bad spell. The next bowler might be the opposition's best.
Fourth mistake: forgetting the toss impact. Team batting first sets a target; team batting second chases. Chase sessions behave differently — required run rate dictates intent. A Session 3 line of 55 looks generous when the chase needs twelve an over, but the field is out and dot balls multiply. Fifth mistake: betting on matches you haven't watched. If you don't know which bowler operates at the death, you're guessing the Session 4 line. Stick to leagues you follow — IPL, TNPL, Maharashtra Premier League — where you know the personnel.
Reading the Line Movement Like a Pro
The line is not a prediction; it's a balancing tool. FairPlay adjusts it to attract equal money on both sides. When you see the line drop from 50.5 to 47.5 mid-session, it means heavy money landed on Under — or a key batter got out. When it rises, Over money dominates or a power-hitter just arrived. Track the movement, not just the static number. A line that barely moves despite wickets suggests the market expects the incoming batter to maintain tempo. A line that plunges three runs after a single wicket says the market rates that batter highly.
You can spot value by comparing your own over-by-over projection with the live line. Say you project 54 runs for Session 2 based on the batters at crease and bowlers due. The line sits at 50.5. That four-run gap is your perceived edge. Bet Over. If the line sits at 56.5, the market disagrees — stay out. This discipline separates session betting from gambling. It's a numbers exercise wrapped in cricket knowledge.
One more thing: session markets close at the start of the first over of the block. You cannot bet Session 2 once the seventh over begins. In-play bets on Session 2 must be placed during overs 1-6 or during the innings break. FairPlay greys out the buttons the moment the bowler starts his run-up for the first ball of the session. Plan ahead. Have your stake ready during the previous over.
Session Betting in the Context of Your Overall Strategy
Session bets are short-horizon, high-frequency decisions. They complement longer-horizon markets like match-winner or top run-scorer. Some punters use sessions to hedge: back the chasing team pre-match, then back Under on Session 3 if the required rate balloons and the field spreads. Others treat sessions as standalone — pure over-under punts based on pitch, weather, and match-ups. Neither approach is wrong; consistency is what matters.
Track your session results in a notebook or spreadsheet. Note the line, your pick, the actual runs, and the reason you chose that side. After twenty sessions you'll see patterns — maybe you're strong on Session 1 powerplay reads but weak on Session 3 death overs. Adjust. Drop the losing segments. Double down on the winning ones. That's how a Tuesday habit becomes a sustainable edge.
The Wankhede floodlights hum. The match ends. Arjun scrolls his bet history — one win, two losses, one pass. He's down ₹350 on the night but he understands the mechanism now. Next Tuesday he'll wait for Session 2, watch the first six overs, then decide. That's the lesson: session betting rewards patience more than instinct. Open the FairPlay live betting page next match, watch the lines breathe, and pick your spot.
More on how we approach numbers is on about FairPlay, and the tools for setting your own limits are on responsible gaming.