Best ICT Killzone Indicators on TradingView (2026), Code-Read.

Short answer: the most-boosted free killzone indicator, ICT Killzones + Pivots by TFO (59,515 boosts), is the one we'd start with. It reads its windows on New York time, so they move with daylight saving time, and keeps each killzone's high and low until price trades through one, with an alert. Know two things: its New York AM window starts at 09:30, not 08:30, and a wick through counts as taken, with no close test. LuxAlgo's two killzone scripts read their times at a fixed UTC-5, so from March to November their windows open an hour late on the New York clock. For a session's high and low drawn only once the session is over, Session Highs and Lows by tc3oliver is the one in our read.

Most lists name killzone indicators.

This one reads them.

What we checked

Killzones are fixed windows on the New York clock, named after the market that's busiest in them. There's no official table: guides disagree on where the Asia and New York windows start, and our ICT killzone clock lists them source by source. The guides there all put London at 02:00 to 05:00 New York time. New York changes its clocks on the second Sunday of March and the first Sunday of November, so on UTC and on most other clocks every window moves by an hour for part of the year.

That makes the clock the first thing to check in a script. Pine's time() reads a session in "the time zone of the exchange by default, unless a timezone argument is specified" (Pine manual, sessions). An IANA name such as America/New_York "represents UTC-4 or UTC-5, depending on the time of year"; a fixed offset doesn't (Pine manual, time, both checked 31 October 2026).

We searched TradingView's scripts for seven terms on 31 October 2026: "killzone", "killzones", "kill zone", "ict killzones", "ict killzones and pivots", "session high low" and "asian range". We kept the 195 whose names mention a kill zone, a session or Asia, 143 of them open source, took the 15 most-boosted open-source ones, none skipped, and read every line that decides what is drawn. Five questions:

• The windows: which killzones, and at what times by default?
• The clock: New York's own, so daylight saving time moves the windows with it, a fixed offset, or the exchange's?
• The high and low: does the script keep each window's high and low after it ends, and mark one taken? By a wick, or by a close?
• When it decides: a window's high or low isn't final until the window ends. Does the script draw it before then, and does it decide on the live candle?
• Alerts, and the licence.

The table

Boosts as TradingView's search showed them on 31 October 2026. Times are each script's defaults, on the clock its Clock column names.

Five more near the top of the search have closed code, so they aren't in the table. ICT SM Trades by majky (20,302 boosts), ICT Killzones [28Trades] by ReflowFX (7,229), Sessions & ICT Killzones (0xCryptoVince) by Vincent139 (7,031), Asian Range by Nico948 (6,302) and Killzones / Daily Open / Weekly Open / Monthly Open by realbartbtc (3,064) are protected: free to add, with the code hidden.

What the code says

TFO's is the popular one, and its clock is right. Each killzone is a time() call in the Timezone setting, America/New_York by default. The other choices are fixed GMT offsets, which its own tooltip says are "not adjusted to reflect Daylight Saving Time changes". While a window runs, its box and its two "pivot" lines follow the live candle's high and low. After it ends, the lines extend "Until Mitigated": the first candle whose high goes above the high, or whose low goes below the low, stops the line, and with Alert Broken Pivots on it sends "Broke ASIA High" (or Low) right then, once per bar, on the live candle. A wick through and a close beyond look the same to it. By default it tracks only each killzone's latest session and keeps three on the chart. It is shared under the Mozilla Public License 2.0.

Its settings, for anyone searching them. In the version we read:

• Killzones: six rows, each with a switch, a colour, a name and a session: ASIA 2000-0000, LNDN 0200-0500, NYAM 0930-1100, NYL 1200-1300 (off), NYPM 1330-1600 and RTH 0930-1600 (off). Session Limit, 3, is how many of each drawing it keeps.
• Pivots: Show Pivots on, Midpoints off, Pivot Labels on, Alert Broken Pivots on, Extend Pivots "Until Mitigated" (or "Past Mitigation"), from the "Most Recent" session (or "All").
• Range Data & Levels: a table of each window's range, its average over the last 20 sessions and how often its high and low were later hit. Range levels around each window's open are off.
• Day - Week - Month: the previous day's, week's and month's high, low and midline are on; their opens are off, and so is their alert.
• Opening Prices and Timestamps (two groups): lines at the 09:30, 12:00 and 16:00 opens, and vertical lines at the same times. The midnight open is in the list, switched off by the // in front of 0000, yellow, Midnight.
• Global: Timezone America/New_York; Timeframe Limit 30, so it draws on charts of 30 minutes or less; Drawing Cutoff Time off.

To match the 08:30 New York AM window that tc3oliver's script and our desk use, type 0830-1100 in the NYAM row. To get the midnight open, delete the //.

LuxAlgo's two read the clock at UTC-5. Both pass 'UTC-5' to time(), a fixed offset, and New York is on UTC-5 only from November to March. From the second Sunday of March to the first Sunday of November, 02:00 at UTC-5 is 03:00 in New York, so the London box opens at 03:00, an hour late, and every other box with it. The Toolkit's windows can be edited, the offset can't; ICT Killzones' times are written into the code. The Toolkit extends the latest window's high and low until a candle reaches one or the next window starts, shows its windows on charts of 15 minutes or less by default, and adds order blocks and fair value gaps. ICT Killzones draws retracement levels from 0 to 1 across each window's range instead. Neither has alerts, and both are shared under CC BY-NC-SA 4.0, which doesn't allow commercial use.

The dashed box in this replay is 07:00 to 10:00 UTC, which is where a 02:00 to 05:00 window read at UTC-5 always lands. On 13 January it matches the London killzone; on 17 March and 14 July it opens an hour after it.

TradingFinder's marks a high or low taken, on UTC. Its windows come from a library, Sessions KillZones Library, that reads them at 'UTC+0'. Its London killzone, 07:00 to 09:55 UTC, is 02:00 to 04:55 New York time in winter and 03:00 to 05:55 in summer. Each killzone's high and low extend through the rest of its session (London's runs to 14:25 UTC), and the first candle that trades through one stops the line and sends "The Highest of London's Kill Zone Was Touched." on the live candle. It is shared under MPL 2.0.

Three draw the day's high and low, not the window's. leonsholo's ICT Sessions and BryceWH's ICT Killzone Boxes, which it was built from, shade bands at the daily candle's high and low. They ask for it with security(tickerid, 'D', high) in Pine version 2, where lookahead is on by default (TradingView's guide to Pine version 3), so on past days each band sits at the whole day's high and low, candles after the window included. nsrgroup's AsianRange and KillZones asks for the daily high and low with lookahead_on and no offset for its London, New York and London close lines, with the same result; only its Asia box is the window's own range. All three read the exchange's clock.

FXN's Asian range is marked discontinued. Its code opens with "Discontinued Indicator - No Longer supported". Its times are typed as "EST" but read on the exchange's clock, plus four hours when the symbol's clock is UTC: New York's summer offset, so an hour off in winter. The Asian box, 20:00 to 02:00 by default, is drawn out to its end time while it forms, its lines run to 11:30, and its one alert, "Asian Range Break", fires on a close outside the range between 02:00 and 12:00. It carries no licence line.

For a session's high and low once it's over: tc3oliver's Session Highs and Lows reads America/New_York and draws each window's high and low, labelled at the candle that made it, only on the first candle after the window, so nothing it draws moves. The lines extend right until the next session's replace them. It sends no alerts and doesn't mark a level taken; MPL 2.0. Shanxia's ICT Session Killzone Boxes also reads New York time, and boxes CBDR, Asia, London, New York and London close with a midline and the New York midnight open, but its boxes grow with the live candle and stop at the window's end. No alerts, no licence line.

The rest. oscarvs' two only colour the background, on the exchange's clock; the Bitcoin one says to "Change manually if you need to adjust DST". Texmoonbeam's boxes three full sessions at GMT+1, and its alerts cover Monday's, the previous day's, the week's and the month's levels, not the sessions. Zeiierman's boxes one session you set and alerts when it starts and ends (CC BY-NC-SA 4.0). kurtsmock's tracks a running high and low, but its default date range ends on 1 January 2023, so on today's charts it draws nothing until you change the dates or its reset.

Licences. The Mozilla Public License 2.0 for TFO's, nsrgroup's, TradingFinder's, tc3oliver's and kurtsmock's; CC BY-NC-SA 4.0, which doesn't allow commercial use, for LuxAlgo's two and Zeiierman's. The other seven carry no licence line.

Ours

ICT Levels Desk isn't on TradingView's search: its full Pine v6 source comes in Pine Pro Library, $49 once. Its killzones are four windows on the New York clock: Asia 20:00 to 00:00, London 02:00 to 05:00, New York AM 08:30 to 11:00 and New York PM 13:30 to 16:00, each a time() call in its Timezone setting, America/New_York by default, so daylight saving time moves them with New York. The times can be edited; there's no London close window. Each box grows on closed candles only.

When a window ends, its high and low become lines named after it, "London high" and "London low". Each reads resting until a candle trades through it: a close back makes it swept (⚡), a close beyond makes it broken, and a later close beyond breaks a swept line too. The alert "Session high / low swept" fires on the closed candle; it doesn't say which session, and the desk's JSON alert() payloads don't carry it. Lines stay two days by default, and only those within 2 × the daily ATR of price are drawn; the rest are still tracked. One gap we found reading our own code: a line is born on the first candle after the window, after that candle's checks have run, so that candle's own wick through it isn't judged. The checks start with the next one.

The desk also draws the 00:00, 08:30 and 09:30 opens, the previous day's and week's highs and lows, the opening gaps, the first fair value gap after 09:30 and ICT's macro windows. Its rule for a window's level, replayed on simulated candles: London's high and low, then the first candle beyond one, here in New York AM.

Sweep Desk, in the same library, keeps the London, New York AM and New York PM killzones' highs and lows as liquidity pools once each window ends, on New York time, and can start its setup when one is swept. For sweep scripts that use pivots and fractals instead: best liquidity sweep indicators, code-read. For every window on your own clock, today: the ICT killzone clock. ICT's power of 3 scripts, three of which name windows like these accumulation, manipulation and distribution, are code-read in best power of 3 indicators, code-read. For the one-hour silver bullet windows inside London, New York AM and New York PM, and the scripts that look for a setup in them: best silver bullet indicators, code-read.

We haven't measured whether trading inside a killzone does better than trading outside one.

Check one yourself

• The clock: find the time( call. A third argument of "America/New_York" follows New York's clock changes; "UTC-5", "GMT+1" or "UTC+0" doesn't; no third argument reads the exchange's clock.
• The window's own high and low: if the script asks for a daily high with request.security(), or security() in Pine version 1 or 2 (no //@version line means version 1), look for lookahead. On with no [1], a past day's line sits at the high that day ended with.
• Taken: high > level counts a wick; close > level counts a close. A sweep needs both: a wick beyond, then a close back.
• When: look for barstate.isconfirmed. Without it, a box or a broken line you see live is the live candle's.

None of the scripts here, ours included, runs on MT5, MT4 or NinjaTrader: Pine Script runs only on TradingView.

Limits

One code read, on 31 October 2026, of the versions TradingView served that day. Scripts change, and boosts measure popularity, not quality. We build and sell ICT Levels Desk and Sweep Desk, and we have no relationship with any author named here. Nothing here is financial advice.

Use these animations on your site.Embed these animations