Is initial balance always the first hour?

The first hour is a common convention, but the window must be stated. TradingView TPO lets you choose a number of opening blocks. For other sessions, document the anchor and duration before comparing results.

How do I choose an initial balance indicator on TradingView?

Check the session anchor, timezone, duration, freeze behavior, and extension formula. Manually verify one complete opening window and confirm that later highs do not change the frozen IB high. Indicator names alone do not establish equivalent settings.

Does a return inside the initial balance prove a failed breakout?

It proves only the re-entry condition you defined. In this example, a completed close inside after a break creates a re-entry record. Price can still leave the range again, so preserve later events rather than treating the first return as a forecast.

Can I classify a no-break day before the close?

Only as no break so far. The full no-break label requires every observation through your declared cutoff. Missing later data makes the result unavailable, not a no-break day.

TradingView session structure

Initial Balance Trading on TradingView: Range and Extensions

Initial balance trading uses the high and low of a specified opening period as a reference for the rest of a session. A common choice is the first hour, or two 30-minute blocks. Fix the market, session, timezone, and duration first. After that period ends, freeze the boundaries and measure how price extends beyond them or returns inside. The range describes structure; it does not establish a profitable entry rule.

See the decision guide

Choose the session before choosing the indicator

Write the exchange-qualified symbol, exchange timezone, selected session, IB start and end, and review cutoff in your notes. An exchange timezone identifies the clock used by the instrument; your chosen research session may use another named zone. Record both. The following are possible study definitions, not universal exchange rules for IB.

A 30-minute opening range and a 60-minute IB may overlap, but this exercise studies the later session structure rather than prescribing a breakout entry.
For an overnight session, assign the session date consistently. Resetting at calendar midnight can split a range that belongs to one trading session.
Use a named regional timezone for a local opening time that follows daylight saving rules. A fixed UTC offset can move the window relative to that opening.

Market or study	Possible IB convention	Decision that changes the result
US cash equities	09:30 to 10:30 America/New_York, within the core session	Whether premarket prices are excluded. NYSE lists its normal core session as 09:30 to 16:00 Eastern.
US equity-index futures	A cash-open study can use 08:30 to 09:30 America/Chicago	The cash-open range differs from a range anchored to the electronic session start. Verify the contract and session selected.
Spot forex	A named London or New York opening window selected in advance	Record the broker feed and local timezone; a single exchange opening is not a shared reference for every feed.
A continuously traded crypto pair	A research window such as 00:00 to 01:00 UTC	Midnight is an analytical boundary here, not evidence that participants share an opening auction.

Build and freeze the range on TradingView

On standard time-based candles, mark the chosen opening window and take its highest high and lowest low. For the hypothetical 09:30 to 10:30 study below, aligned five-minute bars opening at 09:30 through 10:25 belong to IB. The 10:30 bar belongs to the observation period after IB. Wait for the last included bar to close before treating the range as final.

Where TPO is available, its Initial balance range setting selects how many opening blocks form the range. Two 30-minute blocks represent one hour; two 15-minute blocks represent 30 minutes. Set the profile session before checking the block count.
TradingView custom TPO session times use the chart timezone. Pine time functions use the exchange timezone by default unless supplied another zone. Do not assume the same displayed hours configure both tools.
If using a community initial balance indicator, inspect its timezone, session start, duration, and extension formula. Compare its high and low against the included candles on one complete session before relying on its labels.
Save the final high, low, width, and a screenshot at the freeze time. Later prices may cross the lines but must not move them. Reset for the next selected session, not for each breakout.

Worked example: calculate extensions from a frozen IB

Assume a complete opening hour has high H = 5,020 and low L = 5,000. These are invented price points, not observed market data. Width W = H − L = 20 and midpoint M = (H + L) / 2 = 5,010. Define an extension as a distance outside the nearest IB edge: upper(k) = H + k × W and lower(k) = L − k × W.

An upper excursion to 5,035 is (5,035 − 5,020) / 20 = 0.75 IB widths outside the high. If the session low stays 5,000, its total range is 35 / 20 = 1.75 IB widths. Those are different measurements.
Some indicators label percentages from the opposite edge or use total range. Check the formula before comparing a displayed 100% line with 5,040.
The midpoint and extensions are reference prices. They do not establish targets that price must reach or valid stop distances.

Distance outside the edge	Upper level	Lower level
0.5 × IB width	5,020 + 0.5 × 20 = 5,030	5,000 − 0.5 × 20 = 4,990
1.0 × IB width	5,020 + 1 × 20 = 5,040	5,000 − 1 × 20 = 4,980
2.0 × IB width	5,020 + 2 × 20 = 5,060	5,000 − 2 × 20 = 4,960

Compare expansion, re-entry, and no-break sessions

Keep H = 5,020 and L = 5,000 in all three hypothetical paths. Observe only after 10:30 until a preselected 16:00 cutoff. Define an upper break as a traded high strictly above H and a lower break as a traded low strictly below L. A touch equal to an edge is not a break. Define re-entry separately as a completed five-minute close strictly inside the range after a break.

At 10:40 the first two paths both show an upper break. Their later difference cannot be used to improve a signal supposedly issued at 10:40.
If both edges are exceeded, record two-sided extension and the event order. A session that breaks high, returns inside, and later breaks low should retain all three events.
A later close back outside does not erase an earlier re-entry. Keep event flags separate from the final close location so changing behavior remains visible.
A no-break day is known only at the cutoff. During the session, the accurate status is no break so far. These operational labels are not a complete Market Profile day-type taxonomy.

Path after IB	Evidence available	Record at the cutoff
Upper expansion	First break at 10:40; later high 5,040; no lower break; no close back inside; final close 5,036	Upper extension = 20 / 20 = 1.0 W. One-sided expansion with no observed close-based re-entry.
Break and re-entry	High 5,030 at 10:40; close 5,018 at 10:45; later low 5,004; final close 5,012	Upper extension = 10 / 20 = 0.5 W. Re-entry confirmed at 10:45; final close inside.
No break	Every later high is at most 5,020 and every later low is at least 5,000; final close 5,011	Neither boundary was exceeded. Both outside-extension measures are zero.

Reject incomplete or incompatible observations

A range is usable only when its input window and later observation window are known. An attractive line drawn across missing history is still an incomplete measurement. Mark unavailable sessions explicitly instead of treating them as small-range or no-break days.

Standard candle OHLC can show both edges crossed within one bar without revealing which happened first. Record the sequence as unknown unless finer data resolves it.
Use ordinary price candles for this audit. Synthetic chart prices and bar construction can change the measured window and levels.
A very narrow IB makes small price moves large when divided by W. Record width in price points and ticks alongside the ratio; do not interpret a large normalized value without its denominator.

Failure condition	Why it matters	Handling rule
History starts at 10:00 for a 09:30 IB	The earlier high or low may be missing	Exclude the session; do not rebuild the missing half-hour from later bars.
A chart bar straddles the IB end	Its high and low include prices after the intended cutoff	Use an aligned finer interval or verified lower-timeframe data.
W = 0	Normalized extension divides by zero	Keep raw high and low, but mark normalized ratios unavailable.
A halt or missing expected bars inside IB	Twelve nominal five-minute slots do not guarantee twelve usable bars	Flag the event and decide the exclusion policy before comparing sessions.
An early close or missing afternoon history	A normal 16:00 review window was not observed	Use the actual scheduled close under a declared policy, or exclude; do not silently compare unequal windows.

Turn the observation rules into a reviewable workflow

Give Pineify the symbol, timezone, session window, IB duration, extension formula, and close-based re-entry definition. Ask the Pine Script AI Coding Agent for a chart overlay that distinguishes developing and frozen levels and exposes the conditions for review. Specify that alerts begin only after IB is complete, use confirmed bars for close conditions, and cannot infer a final day label before the review cutoff.

Check the generated output against the 5,000 to 5,020 arithmetic before using market history. Then inspect a complete session, an incomplete opening window, and a daylight saving transition where applicable.
In Trading Journal, save the hypothesis before the break, paste a saved chart screenshot link into the diary text, and record the observed event times and end-of-session outcome. Preserve no-break and excluded sessions as well as traded ones.
Suggested review fields: session date, feed, timezone, IB start/end, H, L, W, first break side/time, maximum upper/lower extension, first re-entry close, cutoff close location, and missing-data reason.
For a strategy test, add entry timing, exit rules, position sizing, costs, and slippage separately. A correctly plotted IB does not prove that trading its breakouts or fading its edges has positive expectancy.

Where Pineify fits

Pine Script AI Coding Agent

Describe your IB window and event rules, generate a chart aid, and inspect the resulting source and levels against a known example.

Also useful: Trading Journal. Keep your session hypothesis, screenshot links, and later review together so the original observation remains distinguishable from the final outcome.

Build an IB chart aid

Related resources

TradingView workflows Chart timezone and session logic Auction market theory Trading Journal

Frequently asked questions

Educational information, not investment advice. All price paths and ratios on this page are hypothetical calculations, not historical tests, live signals, or evidence of future returns.

Sources and verification

Last verified: 2026-10-17

Published by Pineify. Pineify is an independent product and is not affiliated with TradingView. Sources support the technical explanations; examples do not establish trading performance.