Atlas IB (GC) guide

What this indicator is

Atlas IB (GC) takes any 30- or 60-minute window of the gold futures day, measures the range price made during it (the Initial Balance, or IB) and shows what has historically happened next: how often price reached the upper extension first, the lower extension first, or neither before the session closed.

The three figures add up to 100%, give or take a point of rounding. They are measured frequencies from eleven years of COMEX gold history, not forecasts. If the upper rail reads X%, then in the measured history, windows that looked like this one reached the upper target first X% of the time. It says nothing certain about today. What it gives you is the base rate you would otherwise be guessing at.

This is context, not a signal. There is no buy or sell instruction anywhere in the script, by design. It tells you what usually happens, so that when you take a trade you know whether you are trading with the historical grain or against it.

Why eleven years

The gold dataset reaches back a good deal further than the tables do. Gold's intraday behaviour changed materially in 2015, and averaging across that change would have blended two different markets into one set of figures. The tables are measured only on the market you are actually trading.

Free, on any plan

Atlas IB (GC) is free to use on any TradingView plan, including the free one. Add it from its TradingView page: Atlas IB (GC) by AlgoTrader NQGC ↗. A separate build covers NQ; both are described on the Atlas IB page.

Setup

Adding it. Open the script's TradingView page ↗ and add it to your favourites; it is then one click away in the Indicators menu of any chart.

Symbol: GC or MGC futures. The statistics are measured on COMEX gold and apply to both (MGC is the same contract at one-tenth the size). They do not apply to spot gold (XAUUSD), which is a different instrument with a different trading day and no exchange volume, and they do not apply to anything else. The script does not check the symbol, so it will draw on other charts; the figures simply do not describe them.

Timeframe: any intraday timeframe that divides 30 minutes: 1m, 2m, 3m, 5m, 6m, 10m, 15m and 30m, and seconds charts that divide evenly into 30 minutes. The engine works in clock time, so the figures are identical on all of them; use whichever you like to look at. On any other timeframe nothing is drawn, and with Hide on unsupported timeframes on (the default) the table is replaced by a one-line notice asking for a timeframe that divides 30 minutes.

First run: open Settings and choose the IB start (NY time), the 30-minute boundary the window starts at, and the IB duration (min), 30 or 60. The gold day runs 18:00 to 17:00 New York time, and the IB start list runs from 18:00 to 16:30. The indicator opens on 09:30 +60m. Leave Extension target (× IB range) on Auto, its default.

Three choices at the very end of the day have no measured figures, because almost no session is left after them: 16:00 +60m, and 16:30 at either duration. They are in the list, but nothing is drawn and the table shows dashes.

If you only ever use one window, use 09:00 +60m. Which windows to read on gold explains why, and why the windows at the top of the ranking are the ones to read with the most care.

At the default settings your chart shows the box, rails, badges, run-on guides and status table; the dotted run-on guides beyond each target are on by default in the gold build, and the layers marked off by default need switching on. Screenshots, where shown, use the defaults apart from the window named in each caption.

Reading the chart

The IB box

The box spans the window's high and low. While the window is still forming it is dashed, grey and tagged "IB building…". Once the window completes, the box is tinted towards the historically favoured side (teal for up and red for down by default), or left grey when the indicator abstains, and a dotted line marks its midpoint.

Above the completed box a label gives the session's IB in points, the average IB of the previous five sessions for the same window (avg5) for comparison, and a behaviour tag. Beneath the box a compact line restates the three shares, ▲ up first, ▼ down first and ∅ neither, together with n, the number of comparable historical sessions they rest on. The line is tagged "null %", meaning the plain historical base rate with nothing layered on top. The gold build has no optional adjustments, so these are always the figures the rails carry.

The extension rails

Two dotted lines run out from the completed box, one above and one below, for one window-length. Each carries a badge with the historical frequency of that side being reached first by the session close, and a second line, 🏁 2h · 4h, giving the same frequency measured over those shorter horizons rather than all the way to the close.

On the two Direction bases of Atlas mode (the default is one of them), the badge of the higher side also carries a dir figure: the share of comparable windows that went that way among those in which either target was reached at all. That is the number the Atlas mode threshold is applied to (see What clears the threshold). When the window abstains, both badges read "abstain" and the rails and badges turn grey. In Atlas mode the favoured badge starts with a magnet, 🧲.

How far the targets sit

The distance from each IB edge to its target is a multiple of the IB range, and on gold the indicator sets it for you. Auto, the default, sets the multiple from the IB's size each session, giving more reach on quiet sessions, and the status table shows the multiple in use. The target scales with the day in front of you rather than being a number you have to guess at.

Auto also applies a cost floor. If the target would sit closer than 3 points, Auto steps the multiple up, because a target inside the friction band is not a real target. A micro gold round trip costs roughly a third of a point all in, so a 3-point target puts costs at about a tenth of the move; below that you are trading the cost, not the move. If even the widest multiple leaves the target under 3 points, the Target range row in the table shows ⚠. The floor is a fixed number of points, so it mattered most in the lower-priced years of the record; at recent gold prices IBs are rarely small enough for the ⚠ to appear.

Median run-on guides

Dotted grey lines beyond each target, labelled 15m MFE, 30m MFE and 60m MFE, mark the median distance price continued past that target within 15, 30 and 60 minutes of reaching it (MFE stands for maximum favourable excursion). A 30-minute IB draws the 15m and 30m layers; a 60-minute IB draws all three. They are on by default in the gold build, and they are drawn on both sides of every completed window whether or not a target is reached.

Read this carefully, because it is the most misread number in the script. Our analysis of what happens after a target is reached is unambiguous, and it is not what most people expect: continuation past a target behaves like drift, not momentum. Hitting the extension target does not ignite a move. The guides are useful for shaping a target or a trail; they are not evidence that continuation is likely. Treat them as "how far price typically drifts", not "where it is going".

One difference worth knowing if you also trade index futures: on the index, downside run-ons are consistently larger than upside ones. On gold they are not. Gold does not carry the equity-style downside skew, and the guides are near-symmetric because the measurement says they should be.

The abstain state

When the window does not clear the Atlas mode threshold, the box, both rails and both badges go grey and the badges read "abstain". That is the indicator telling you it has nothing useful to say about direction for this window. Abstain windows are common and they are not a failure: a coin-flip base rate honestly reported is more useful than a manufactured lean. Treat the grey as information you can act on. This window offers no historical lean, and knowing that before you commit can matter more than any other figure on the chart. Standing aside is a position.

Atlas mode and the outcome marks

The opposite state has a name. When the window clears the threshold it is in Atlas mode and the favoured badge carries the magnet 🧲. These are the windows where the measured history leans clearly to one side.

When the race between the two targets resolves, an outcome mark prints near the target that was reached: ✅ the higher-percentage side was reached first, ❌ the other side got there first, ◇ both targets were reached inside the same chart bar, which is rare. On Atlas mode windows the mark carries the magnet as well (🧲✅ or 🧲❌). Abstain windows are still marked, scoring the higher side, without the magnet. A window that reaches neither target gets no chart mark; the table records it instead. The marks are on by default, and they matter: they are the chart grading the indicator in front of you, window after window, the visible counterpart of the hit-rate rows in the table.

What clears the threshold

The Atlas mode basis input offers three definitions. The default, Direction + decided floor, needs two things: the favoured side must have been reached first in at least 62% of the comparable windows in which either target was reached (the dir figure), and at least 50% of comparable windows must have reached a target at all. Direction only drops the second condition. Outcome (3-way) applies the threshold to the plain three-way share printed on the badge.

The default exists because gold's later windows carry very large "neither" shares, and a three-way threshold is then capped by arithmetic rather than by the quality of the lean: it would stay silent in exactly the sessions where direction was clear and simply slow to resolve. Our analysis separates the two risks, and the default lets you hold direction to one standard and resolution to another.

On the two Direction bases the threshold is applied to the dir figure, not to the ▲ or ▼ share printed on the badge, so a badge with a modest three-way share can still be in Atlas mode when most of the comparable windows that resolved went its way. The 🧲 ATLAS MODE row in the table states the rule in force and the value this window achieved, so you can always see why it fired or abstained.

Projected levels (optional, off by default)

A completed IB is not only a box. Its edges and its internal quarters are prices the session keeps returning to. In the IB levels projection group of the settings you can carry the most recent completed window's geometry forward:

• Extend IB EQ (50%) projects the midpoint alone.
• Extend IB quadrants (high / low / 25% / 75%) projects the high, the low, and the 25% and 75% levels.

The Extend input offers two shapes. To next IB window, the default, runs the levels one window-length past the close, so a 30-minute IB projects half an hour and a 60-minute IB an hour, and the levels stop while they are still about the window that produced them. To current bar keeps them travelling with the session, ending a few bars ahead of price (three by default, set by Bars beyond the last bar (current-bar mode)); that is the one to use if you want them present all day as reference.

Only the most recent completed window is projected. That is deliberate: a chart carrying every past window's quarters is unreadable, and the levels stop being about the session you are trading. All projected levels share one colour and width, a quiet grey by default, and each level type has its own line style: solid edges and midpoint, dashed quarters. They sit behind the price action rather than competing with it.

These are geometry, not measured figures. No percentage in this indicator is attached to a quarter level; the three shares are about the extension targets and nothing else.

The Event Horizon (optional, off by default)

Project IB Event Horizon draws one dashed level: the halfway mark between the favoured side's IB edge and that side's extension target. It follows the same Extend setting as the projected levels.

It answers a question the rails alone do not. The target tells you where the move ends; the Event Horizon tells you where it is half done. Price that has crossed it has covered half the distance in the direction the figures favoured; price that keeps stalling beneath it is failing to make the move the base rate describes, and the run to the target still has as far to go as the run already made. On gold, where costs sit close to the target, that checkpoint is worth having: it is an early, honest read on whether the move is actually being paid for. Use it as a place to reassess, not as a place to act.

On abstain windows no horizon is drawn. There is no favoured side, so there is no run to be halfway through, and drawing one anyway would imply a lean the figures do not support.

The forming window: the hazard clock

Before the window closes the script shows something different. At a series of checkpoints through the window it reports the historical frequency that the current running high or low is already the final IB extreme, that is, that this level will still be the extreme when the window ends. The figures sit as labels at the running high (▲) and low (▼), and in the "IB forming" row of the full table, whose tooltip lists the whole checkpoint sequence for the window. Before the first checkpoint the labels show "…". The setting is Show forming-IB hazard (row + extreme labels), on by default.

A ⚡ appears beside a figure when a new extreme prints while that side's stated figure was already 60% or more, meaning something historically uncommon just happened; it stays for the rest of the forming window. It is a flag for awareness, not a signal, and it exists because knowing "that was unusual" is useful when you are watching a window form. The figures are descriptive: they say how often a running extreme at this point in the window turned out to be final, and they make no claim beyond that.

Reading the status table

The full table, top to bottom. It sits top right by default.

Some things worth dwelling on.

The table describes the most recent window on your chart. It is drawn on the last bar, so if you scroll back to an older session, the boxes and badges on screen describe that session while the table still describes the latest one. Each past window's own figures are on its badges and on the line beneath its box.

Rows appear only when they mean something. "IB forming" appears while the window is building and leaves when it completes. A row that is absent is not a row that failed; it is a row with nothing to say about this window, and leaving it out keeps the table short enough to read at a glance.

A tick marks the outcome once the race resolves. When a target is reached first, ✓ appears on that row; ◇ appears on both direction rows for the rare same-bar tie. If the session closes with neither target reached, ✓ appears on No target hit when the next session opens at 18:00 New York time, so a Friday window that reached neither side shows no tick until Sunday evening. In compact mode the direction rows are condensed into one, and the mark there reads ✓ if the higher side came first, ✗ if the other side did, ∅ for neither and ◇ for a tie.

"No target hit" is often the largest number, especially at later IB starts and on compressed days, when Auto sets the target further out. On gold it is larger than on index futures because gold's initial balances run smaller relative to the day that follows them. This is not a defect. Many sessions simply do not travel that far. If you are planning a trade off a target that historically goes unreached most of the time, the table is telling you so before you take it.

The hit-rate rows are the honesty check. They score the indicator against itself on your own loaded history. The bracketed z-score says how far the realised rate sits from the expected one in units of ordinary noise: near zero means the figures are behaving; much beyond ±2, look closer. When the figures hold up, realised and expected track each other. Watch them, and tell us if they drift. The site also keeps a public record of what the gold build showed and what price did next, misses and abstentions included: the gold IB record.

The Atlas rows count only Atlas mode windows, so they fill up more slowly than the general rows and will read as a small sample for a while. A tally of three or four windows is noise; give it a few weeks before drawing conclusions from it.

Compact mode (Compact table (mobile)) keeps the glance rows: IB window, IB range, Target range, the higher side's share with its mark, 🧲 ATLAS MODE, Atlas [W/L] and Window strength. The IB forming row is not shown in compact mode; the forming labels on the chart still are.

The two regime tags can disagree, and that is information

The label above the box compares this IB with the previous five sessions and speaks in behaviour words: 💰 ACCUMULATION · ⚖️ NORMAL · 🚀 EXPANSION. The IB range row in the table compares it with eleven years of the same window and speaks in distribution words: 💰 COMPRESSED · ⚖️ NORMAL · 🚀 EXPANDED. The vocabularies differ on purpose. They are different measurements, and identical names would encourage reading one as the other. When they disagree you are looking at a quiet week inside a busy period, or the reverse. That disagreement is real information about context, not a bug. Auto sets the target from the table tag, not from the label.

The cut points between the tags are gold's own, measured on gold. Borrowing an index's definition of an expansion day would misclassify gold badly in both directions, and the consequence would land straight on the automatic target.

The scenarios table (optional, off by default)

A second, smaller table presents the same figures as conditional statements. Switch it on with Show scenarios table in its own Scenarios table group of the settings, and place it with Scenarios position (bottom right by default). Like the status table, it describes the most recent completed window:

• ▲ (target price) first: the share of comparable sessions in which the upper target was reached first, followed by "then +N pts", the median further push within the window's own length (/30m or /60m) after that target is reached.
• ▼ (target price) first: the same for the lower target.
• Neither: the share in which neither target was reached by the close.

The rows latch as events occur. The reached target's row changes to HIT with the New York time and a ✓, and the other rows grey out; a same-bar tie reads "both in one bar"; a session that closes with neither reads NEITHER ✓. Hovering over the table shows the 2h and 4h figures as well.

Nothing new is measured here; it is the same figures in a format some people find easier to act on.

Note there is deliberately no rail-break condition anywhere in either table. Conditional rows attach only to target hits. We do not show a statistic we have not measured.

Which windows to read on gold

This section exists because gold behaves differently from index futures in a way that changes what you should do with the indicator, and because the obvious way to pick a window is a trap.

Every window the indicator covers was scored on how often its favoured target was reached first. That score, and the window's rank against all the others, is the Window strength row.

Read that row with the No target hit row beside it, always. The top of the ranking belongs to afternoon windows, and on paper they look excellent: the two highest read 80% or more. They are not the windows to use. A late-afternoon window has very little session left, so the only races that resolve at all are ones where price was already close to a target; a large part of that score describes which races got to finish, not foresight about which way they went. Their No target hit share is correspondingly large, and the default Atlas mode basis, which needs at least half of comparable windows to reach a target, keeps most of them out of Atlas mode.

Cost is the second check. A very reliable 2-point target with a third of a point of costs is not an opportunity, which is what the ⚠ on the Target range row is for. Because that floor is a fixed 3 points, it caught most afternoon windows in the lower-priced years of the record and seldom fires at recent prices. Its absence is not an endorsement: the short-session problem above does not go away when gold gets more expensive.

The family that holds up is the US late-morning 60-minute block, IB starts from roughly 09:00 to 11:30 New York time. Those windows score near 70% on Window strength, resolve most of the time, and carry targets that clear the cost floor. Judged on the share of all sessions in which the favoured target was actually reached first, the number that matters since a window that rarely resolves rarely pays, 09:00 +60m is the workhorse: it led the family on that measure and carried its largest target.

Two more things worth having:

• Overnight windows are the opposite trade-off. They resolve almost every session, but the lean is weaker: their Window strength sits in the high 50s and low 60s. They are also where the magnet appears most often on the Outcome (3-way) basis, simply because their "neither" share is tiny.
• 30-minute windows are outscored by their 60-minute siblings at most start times. The exception is the US morning from 08:00 to 11:00, where the 30-minute versions resolve far more often and can out-return the hour on the earliest IB starts, at smaller targets. Afternoon 30-minute windows carry the same short-session caveat as the afternoon hours.

The practical consequence: on gold, for much of the clock the honest answer is that this is not the window to use, and the table says so through the No target hit share, the abstain state and, when costs are the problem, the ⚠.

Where the numbers come from

Millions of one-minute gold bars, spanning nearly two decades of COMEX history, of which the tables use the post-2015 era. The prices are the contract's true traded prices, checked against known historical highs and lows to the tick, and contract-roll sessions are left out so that a rollover cannot pass for a move.

Everything the indicator displays is a measured frequency read from a fixed table built into the script. The shares are not estimated on your chart; the indicator looks up what happened, in comparable situations, in the measured history.

Getting to those tables took a long and deliberately sceptical piece of proprietary research. A large number of candidate influences on how a window resolves were considered, and each had to show that it did better than chance alone would have. Most did not, and what you are using is what was left standing after the ones that failed were removed. That is why the gold build has no list of optional adjustments: the short list is the finding.

Before release, every version goes through the same checks: the displayed figures must reconstruct from the source data, the chart output must match the research data window for window, the output must be identical on every supported timeframe, and the live behaviour must match the shipped figures on a real forming session.

The tables are fixed in each published version. Consistency across the years of the record is reassuring, but the real test is how the figures hold up on sessions after the tables were built.

Honest limitations

• These are frequencies, not predictions. No individual session is bound by them.
• The three-outcome split is measured to the session close. Over shorter horizons the split is materially different, which is why the 2h and 4h figures sit on the rail badges. Do not reuse the by-close numbers for a short-horizon plan.
• Sample size varies. Some figures are far better supported than others; the Sample (bin) row tells you which, and you should weight your confidence accordingly.
• In-sample. The tables were measured on history that includes the period they describe. Consistency across the years is reassuring, but it is not the same as evidence from sessions the tables have never seen. A minority of windows are also less stable across the years than the rest, which is part of why the tables start in 2015.
• A high Window strength in the afternoon is partly a short-session effect. The indicator will happily draw a window that should not be used; the No target hit share, the abstain state and the Window strength caveat are there so you can tell. The 3-point cost check is fixed in points and rarely fires at recent gold prices, so a missing ⚠ is not a recommendation.
• Contract rolls. Gold rolls every two months. Roll sessions were left out of the measurement but still appear on your chart. A roll does not stretch the target distances or the run-on guides, and the box, rails and race all sit inside one session. On the roll day itself, previous-IB levels projected with To current bar can still show the price gap between the old and the new contract.
• The forming-window figures are descriptive. They report how often a running extreme survived to be final. They are not a signal, and the ⚡ is not a trade trigger.
• The projected levels and the Event Horizon carry no probability. They are geometry drawn from a completed window, offered as reference. Nothing in the tables scores them.
• GC/MGC only. Not spot gold, not silver, not anything else.
• Ties happen when both targets are reached inside the same chart bar. They are rare, are marked ◇, and are not counted for either side. A longer bar is more likely to contain both targets, so ties are a little more common on a 15-minute chart than on a 1-minute one.

Using it in practice

Some patterns that make sense given what the numbers actually support:

Pick your window from Which windows to read on gold, not from the top of the ranking. This is the first decision, and on gold it is most of the decision.

Use it as a veto rather than a trigger. Its main use is negative: if you were about to take a long into a window where the historical split leans hard the other way, or towards a target that historically goes unreached most of the time, that is worth knowing before you commit.

Respect the abstain. A grey rail means the history does not favour a side. Trading it anyway is your call, but do it knowing there is no historical lean behind you.

Let the target distance decide whether there is a trade at all. If the Target range row shows a distance that barely clears your costs, reconsider regardless of the percentages. The ⚠ only catches the clearest cases.

Use the decided floor deliberately. If your plan needs the race to resolve, for an intraday target or a time-boxed trade, keep the default basis and consider raising Min decided share % (floor basis). If you are happy to sit through unresolved sessions, Direction only will hand you more windows at comparable direction quality.

Do not stack the run-on figures into a continuation thesis. They are drift, measured. If you use them, use them for target and trail geometry.

Watch the realised-versus-expected rows over time. They are your own ongoing audit of whether the figures are behaving on your data. Load a 15-minute chart when you want the biggest sample: TradingView loads far more history there than on a 1-minute chart, so the tally reaches a meaningful size much sooner. The figures themselves do not change with timeframe, only how many sessions the tally has seen.

What a week with gold looks like

A gold week does not hand you the same mix of states an index week does, and it helps to expect the real shape.

The windows worth reading are concentrated in the US late morning. Two or three mornings a week typically arrive in Atlas mode there, with a magnet on a rail, a favoured side, a target at a distance the session can reach, and the 2h and 4h figures saying how quickly comparable windows tended to resolve. On those sessions, whatever your entry logic is, you know which way the history leans and how far away the target is.

The overnight windows are the mirror image: they nearly always resolve, but the lean is thinner and the targets are smaller. They suit a different temperament, with more races and less conviction in each.

And the afternoons top the ranking and are the least useful in practice: most comparable windows never reach either target, the default basis keeps most of them out of Atlas mode, and what does resolve was mostly close to a target already. A day where the indicator talks you out of three afternoon trades has done its job.

The quieter benefit is what this does to the decision itself. Within a bar of the window closing you hold the same few numbers every day, lean or abstain, target distance and the share of sessions that reached neither, so the plan exists before the market has finished deciding. Less improvising mid-bar. Fewer trades taken just to be involved. And the outcome marks and the tally rows keep score in the open.

Using it alongside Atlas Sessions (GC)

The two indicators answer different questions about the same day, and the difference is in what they measure from.

Atlas Sessions measures against the previous session, using reference points that exist before the new session opens and do not move. Does this session take the previous session's high, its low, both, or neither?

Atlas IB measures against the current window. Price builds its own range in the chosen window, and the targets are derived from that range. Nothing is known until the window completes.

So Sessions gives you the session frame, whether this is likely to be a session that expands and takes out levels or one that sits inside, and IB gives you the execution frame within it: specific targets, distances in points, and how often they get reached.

The natural pairing on gold is the US morning: an 08:00 or 09:00 +60m IB window forms inside the US AM session that Atlas Sessions (GC) describes.

The important caveat, and it runs against instinct. When the two agree, that is not two independent confirmations. Both ask which line price reaches first, on the same instrument, and they draw on much of the same information about the day. Agreement between them is largely the same fact stated twice. Read it as coherence, not as doubled evidence, and do not size up because both agree.

Disagreement is the more informative case. If Sessions indicates a session likely to stay inside its prior range while IB projects a distant target, the two are telling you the target is probably too far for the day you are in, and the IB No target hit figure will usually already be saying so. If Sessions leans strongly to one side while the IB window abstains, you have a session-level lean with no window-level structure to express it through. Both are worth knowing before you act.

The practical order: read Sessions first for the session's character, then IB for the geometry inside it. Sessions rarely changes what you do at the window level; it changes how much you expect the day to travel at all. Atlas Sessions (GC) is free as well: see the Atlas Sessions page.

Tracking it yourself

The hit-rate rows score the figures on the history loaded on your chart. We also keep a public record of what Atlas IB (GC) showed at the 09:00 open and what price did next, misses and abstentions included: week by week from August to September 2026, and month by month from October 2026. See the gold IB record.

Settings reference

Every input, grouped as it appears in the settings dialog, with its default. Dark and light themes are supported throughout.

IB window

Probability display

Display

Table

IB levels, projection

Scenarios table

IB box style

MFE excursions

Hazard clock, forming IB

FAQ

Is it really free?

Yes. Atlas IB (GC) is free on any TradingView plan, including the free one: add it from TradingView ↗.

Does it repaint?

No. A window's figures are published once, from the first closed bar after the window ends, and are then frozen, so a session looks the same whether you watched it live or load it later. On a live chart that means they appear when the first bar after the window completes: a minute after the window on a 1-minute chart, fifteen minutes after on a 15-minute one. The forming-window display is a live, building-phase feature by nature, and the completed box replaces it when the window closes.

Why do I get the same numbers on 1m and 15m?

Because the engine works in clock time, not bars. This is deliberate, and it is checked before each release. The one thing a longer bar can change is the rare tie, when both targets fall inside one bar.

Why do the tables only start in 2015?

Because gold's intraday structure changed around then, and measuring across the change would average two different markets together. See Where the numbers come from.

Why is "no target hit" so large on my window?

Later IB starts have less session left to travel in, and on compressed days Auto sets the target further out. Gold's initial balances are also smaller relative to the rest of the day than an index's. Try an earlier window: the morning windows resolve far more often.

Why does the Target range row show ⚠?

Because the target sits under 3 points, inside the band where trading costs consume the move, even at the widest multiple. At recent gold prices this is uncommon and mostly limited to the quietest late windows.

Why does a window show nothing at all?

Three common reasons: the chart timeframe does not divide 30 minutes; the window is one of the three late choices with no measured figures (16:00 +60m, or 16:30 at either duration); or the chart does not yet hold a completed window for that IB start.

I scrolled back and the table did not change.

The table always describes the most recent window on your chart. Each past window's own figures are on its badges and on the line beneath its box.

Why is there no tick on Friday's window?

A window that reaches neither target is confirmed as "no target hit" when the next session opens at 18:00 New York time. Friday's close has already decided it; the tick appears on Sunday evening. A target reached during the session is marked straight away.

What happens at a contract roll?

The target distances and run-on guides are not stretched by the roll, and the box, rails and race sit inside one session. On the roll day, previous-IB levels projected with To current bar can still show the price gap between contracts. Roll sessions themselves were left out of the measurement.

Does it have alerts?

No. This build has no alert conditions.

Can I use it on NQ, spot gold or silver?

No. The tables are measured on COMEX gold, and applying them elsewhere would be inventing numbers. There is a separate Atlas IB for NQ, measured on its own terms: see the Atlas IB page.

The percentages changed after I reloaded.

The historical figures do not change. The realised-versus-expected rows do, because they depend on how much chart history TradingView loaded.

Can I have the underlying tables?

No. The measured tables stay private; the indicator is how they are shared.

Support

• support@algotradernqgc.com
• @AlgoTraderNQGC

Questions about interpreting a specific session are welcome; send a screenshot with the status table in view and the IB window row readable.