Opening Range Breakout (ORB)

The Opening Range Breakout (ORB) is a session-based intraday concept built on a single observation: the first minutes of a trading session tend to concentrate order flow, and the high and low printed during that window often act as reference levels for the rest of the day. A trader defines an opening range — commonly the first 5, 15 or 30 minutes after the cash open — and treats a decisive move beyond that range as evidence that one side has taken control of the session.

What makes ORB unusual among intraday concepts is that it is fully mechanical from the outset. The clock defines the range, not an indicator, so the entry level, the invalidation point and the window in which a trade is allowed all exist before the first order is placed. That property is also why the concept attracts so many published variations: the skeleton is trivial to state, and almost all the disagreement lives in the details around it.

## How the mechanics work

Three parameters define the core. The **session anchor** determines when the clock starts — the New York cash open for US equities and index futures, the London or Frankfurt open for European instruments, a futures session open for others. The **range duration** determines how long the market is observed before the box is fixed: the high and low of that period become the reference levels. The **trigger** determines what counts as a break — a tick through the level, a candle close beyond it on the signal timeframe, or a break followed by a retest of the broken edge.

Risk is usually anchored to the same structure. Stops sit at the opposite edge of the range, at its midpoint, or at an ATR-derived distance from entry. Targets are typically a fixed multiple of the risk, a measured move of one or two range heights projected from the break, a prior-session level, or a trail into the close. Nearly every serious version also carries a time component: no new entries after a cutoff hour, and open positions closed before the session ends.

## Main variants

The most common axis of variation is range duration. Short ranges produce more signals and tighter stops but a higher share of breaks that immediately fail; longer ranges produce fewer, wider setups and often miss the strongest early expansion. A second axis is how many attempts a version allows: first break only, both directions, or re-entry after a failed break. A third is filtering — bias filters such as VWAP, moving averages or the prior day's close, volume or volatility conditions, or candle-body and structure requirements applied to the breakout bar itself. A fourth family inverts the premise entirely and trades the failure: when a break outside the opening range reverses back inside, the setup becomes a fakeout or false-breakout trade in the opposite direction. Finally, some versions layer contextual reference — volume profile, liquidity levels, auto-drawn trendlines, pre-plotted projection targets — onto the same box.

## What typically differentiates implementations

Most of the practical difference between two ORB versions is invisible in the headline description. The exchange session and time-zone handling (including daylight-saving transitions) decide whether the box is even the same box. Whether pre-market or overnight activity is included changes the range width materially. Break confirmation — tick versus close versus retest — changes both the fill price and the number of trades that exist at all. Position sizing anchored to range height behaves very differently from fixed sizing on wide-range days. And the exit model, particularly whether the version scales out, trails, or takes a fixed target, tends to dominate the outcome distribution more than the entry rule does.

## Common mistakes

The recurring errors are structural rather than tactical. Redefining the range after seeing how the day developed turns a mechanical rule into hindsight. Mishandling exchange time zones shifts the whole box and quietly invalidates a backtest. Treating a very narrow-range day and a very wide-range day identically ignores the fact that range width is itself information about the session. Allowing unlimited re-entries converts a structured setup into repeated participation in a chopping market. Tuning the range length to the minute on a single instrument and a single sample is curve-fitting to noise. Assuming fills at the exact breakout level ignores the slippage that concentrates precisely at those levels. And applying the concept unmodified to 24-hour markets overlooks that a "session open" there is a convention, not a structural liquidity event.

## How to evaluate and backtest a version

Write the rules down to the minute before coding anything: anchor, duration, trigger, stop, target, maximum trades per day, and the flat-by time. Reconstruct the strategy on data with correct session timestamps, using bar granularity finer than the range itself, and be explicit about intrabar ambiguity — when a stop and a target both sit inside the same bar, the assumption you choose can move the result more than any parameter. Include commissions and a realistic slippage assumption on breakout fills.

Then segment rather than aggregate. Look at results by year, by volatility regime, by direction, by day of week, and by range-width quartile; a version that only works on the widest quartile is a different strategy than advertised. Run a sensitivity check on the core parameters: if performance collapses when the range moves from 15 minutes to 14 or 16, the number was fitted to the sample. Validate out of sample or with walk-forward, test on correlated instruments, and always compare a filtered version against the plain unfiltered ORB on the same data — every added condition should demonstrably earn the complexity it introduces.

The 16 decoded versions linked from this page differ across exactly these axes: session anchor, range duration, confirmation, filtering, and exit model. Read side by side, they make it easier to see which design choices are cosmetic and which ones actually change how a version behaves.

Strategies in this concept (24)

Frequently asked questions

How long should the opening range be?

There is no universally correct duration; 5, 15 and 30 minutes are the most commonly published choices. Shorter ranges generate more signals with tighter risk but a larger share of immediate failures, while longer ranges produce fewer and wider setups and can miss the initial expansion. Treat the duration as a parameter to test on your instrument and session, not as a fixed rule, and check that results do not depend on one exact value.

Does the Opening Range Breakout apply to 24-hour markets like forex and crypto?

It can be applied, but the premise changes. In equities and index futures the cash open is a genuine structural event where overnight order flow is released; in a 24-hour market the chosen "open" is a convention, usually tied to a regional session such as London or New York. Versions built on 24-hour instruments therefore depend more heavily on the specific session window selected, which is worth testing explicitly rather than inheriting from an equity implementation.

Is it better to enter on the first break or wait for a retest?

They are different trade-offs, not a ranking. Entering on the break captures the fastest expansion days but accepts more false starts and worse fills. Waiting for a close beyond the level or a retest of the broken edge filters some failures and improves entry price, at the cost of missing days that never come back. Whichever you choose, define it precisely enough that a backtest can reproduce it without judgment.

Where is the stop usually placed in an ORB setup?

The three common anchors are the opposite edge of the opening range, the range midpoint, and an ATR-based distance from entry. The opposite edge is the most conservative in terms of invalidation logic but produces very different risk sizes on wide and narrow days, which is why many versions pair it with position sizing scaled to range width. The choice interacts directly with the exit model, so stop placement and target logic should be evaluated together rather than separately.

Why do two ORB versions with the same range length produce different results?

Because most of the behavior lives outside the range definition. Session and time-zone handling, whether pre-market data is included, how a break is confirmed, how many attempts per day are allowed, sizing method, and the exit model all shift outcomes substantially. When comparing versions, line up these details first — otherwise you are comparing two different strategies that happen to share a name.

What does a credible backtest of an ORB version need to include?

Correct session timestamps with daylight-saving handling, bar data finer than the opening range, an explicit assumption about intrabar stop-versus-target ordering, and realistic commissions and slippage on breakout fills. Beyond that, segment results by year, volatility regime, direction and range width, run a parameter sensitivity check, validate out of sample, and benchmark any filtered version against the plain unfiltered rule on identical data.

All strategy concepts · Explore all strategies