Short Straddle Backtest: Testing the Strategy on Nifty & Bank Nifty

Published 9 July 2026 · 8 min read · SutraLipi

A short straddle is one of the most popular options-selling strategies on Nifty and Bank Nifty — and one of the easiest to lose money on if you skip the backtest. Here is how the strategy works, how to backtest it honestly, what the numbers really mean, and how strangles and iron condors change the risk.

What is a short straddle?

A short straddle means selling both the at-the-money (ATM) call and the ATM put of the same expiry at the same time. You collect two premiums up front, and you profit if the underlying stays close to that strike — the options decay and you keep the premium. You lose if the market makes a big move in either direction.

It is a bet on low movement: you want the index to sit still. That makes it attractive in range-bound conditions and dangerous around events and trends.

The rules to backtest

A testable short straddle needs every rule spelled out:

• Entry — e.g. sell the ATM call and put at 9:20 AM on the current weekly expiry.
• Stop-loss — a per-leg or combined-premium stop is essential; naked selling has open-ended risk.
• Target / exit — a premium-decay target, or a time-based square-off (e.g. 3:15 PM).
• Adjustments — optional rules to shift or hedge a threatened leg.

A short straddle in a few lines

The option chain resolves the ATM call and put for you, so the strategy is short to express:

OptionChain  chain = NFO:OPTIDX:"NIFTY";
EquitySymbol nifty = NSE:IDX:"NIFTY";
OptionSymbol ce;
OptionSymbol pe;

onStart {
    ce = chain.ATM(CE, Expiry.Weekly(0), nifty);
    pe = chain.ATM(PE, Expiry.Weekly(0), nifty);
    OrderSend(ce, SELL, 1, 0, 0, 0, NORMAL, DAY, "straddle ce");
    OrderSend(pe, SELL, 1, 0, 0, 0, NORMAL, DAY, "straddle pe");
}

In practice you would add stop-loss and square-off logic. Build it visually in the options strategy builder or in the SutraLipi language.

How to backtest it — and why tick-level matters

Options are path-dependent: theta, implied volatility and the underlying all move within a candle, and a stop-loss can be hit intrabar. A candle-close backtest can completely miss a stop that would have triggered live. That is why a realistic short straddle backtest must run at tick level. Read our full guide on how to backtest a trading strategy for the general workflow.

Reading the results honestly

Short straddles are famous for a high win rate — you will often see 70–80% of days profitable. That number is seductive and misleading on its own. The losses, when they come, can be several times the size of a typical win. Always read:

Strangle and iron condor: the same idea, different risk

Two close cousins change the risk profile:

• Short strangle — sell an OTM call and an OTM put instead of ATM. You collect less premium but get a wider breakeven range, so it tolerates more movement. Backtest it the same way, using chain.OTM(...) to pick the strikes.
• Iron condor — a short strangle with protective long wings bought further out. The wings cap your maximum loss, turning an open-ended risk into a defined one. For most retail traders, a defined-risk iron condor is a far safer way to express the same “low movement” view than a naked straddle.

All three are built from the same option chain — only the strike selection and hedges differ.

Try it

Build a short straddle, strangle or iron condor in the options strategy builder, then backtest it on tick-level Nifty and Bank Nifty history — free to start.

This article is for education only and is not investment advice. Trading and investing in securities and derivatives carry risk of loss; past performance and backtested results do not guarantee future returns. Please read our Risk Disclosure Statement and consult a SEBI-registered adviser before trading.