In Smart Money Concepts (SMC) and Inner Circle Trader (ICT) communities, a “killzone” is a named time window in which a trader expects a market to be more active or a particular setup to be more relevant. The label is community terminology—not an exchange designation, a universal market rule, or proof that institutional orders must arrive at a precise minute.
The useful idea beneath the terminology is straightforward: participation, spreads, volatility, scheduled news, and overlapping business hours vary through the day. A time window can therefore be a context filter. It cannot replace direction, location, structure, confirmation, risk limits, or execution rules.
What does “killzone” mean in SMC and ICT trading?
The term generally refers to a recurring intraday window associated with the Asia, London, or New York trading day. Traders may watch the window for expansion from a range, a run through a prior high or low, a displacement move, or a lower-timeframe structure change. Definitions differ between educators, chart templates, instruments, and versions of the methodology.
That variation matters. One source may call 02:00–05:00 New York time the London killzone, while another narrows or shifts the interval. Some traders split New York into an open window and a later London-close window. Treat the exact boundary as a strategy parameter. Write down the source, timezone, start, end, and whether the interval follows daylight saving time before testing it.
If the broader vocabulary is unfamiliar, read the Smart Money Concepts guide. For objective swing and confirmation definitions, use the BOS and CHoCH market-structure guide. Those concepts describe a chart hypothesis; the killzone only adds time context.
Why trading activity changes by session
- Regional desks, banks, funds, market makers, and commercial participants begin and end business at different local times.
- Forex liquidity often increases as London opens and again when London and New York business hours overlap.
- Equity-index futures respond to European opens, US economic releases, and the US cash-market open.
- Scheduled macroeconomic announcements can produce abrupt changes in volume, spread, slippage, and volatility.
- Overnight ranges create visible reference points that later participants may trade through, reject, or accept.
- Crypto trades continuously, but fiat, derivatives, and regional participation can still create time-of-day patterns.
This reasoning concerns changing participation and available liquidity, not a guarantee of direction. Higher activity can produce cleaner continuation, violent reversal, wider spreads, or noise. Learn the difference between measurable execution liquidity and chart-based liquidity language in what liquidity means in trading.
Asia session context
SMC traders often use the Asia session to define an overnight range rather than to assume every instrument will make its main move there. The range high, range low, and midpoint may become reference levels as Europe opens. On yen, Australian-dollar, Asian-index, and regionally sensitive products, Asia can itself be the active session; on other markets it may be quieter.
- Mark the range using one fixed start and end rule.
- Record whether the range was narrow, normal, or wide relative to recent sessions.
- Note major Asia-Pacific data and local market holidays.
- Do not assume a narrow range must break or that a range extreme must be swept.
- Keep an “Asia setup” separate from an “Asia range used as London context” in your journal.
The phrase “Asian range” is especially ambiguous because Tokyo, Hong Kong, Singapore, Sydney, and continuously traded venues do not share one opening bell. Your rule needs to identify the actual clock and market you mean.
London session and London killzone context
London is a major center for foreign-exchange activity. Around the European morning, traders often watch whether price expands from the overnight range, interacts with the prior-day high or low, or rejects an apparent breakout. The active interval can also affect index futures and metals, but each instrument has its own liquidity cycle.
A common SMC narrative is that London takes one side of the Asia range and then moves toward the other side or toward a higher-timeframe objective. That is a hypothesis to test, not a sequence the market owes you. Price may continue through the first boundary, remain balanced, reverse twice, or complete most of its daily range before your chosen window.
New York session and overlap context
New York activity can include US economic releases, the London–New York overlap, futures volume around the US cash open, and later position adjustment as Europe closes. SMC communities may use separate names for an early New York window and a London-close or afternoon window.
- Pre-open releases can move price before the US stock-market bell.
- The cash open can increase index volatility and invalidate levels formed in thinner trade.
- London–New York overlap may increase participation but also produce rapid two-way movement.
- After Europe closes, liquidity and behavior can change again.
- A session model developed on EUR/USD should not be assumed to transfer unchanged to crypto, a US small-cap stock, or an index future.
Separate “New York morning,” “cash open,” and “London close” if they represent different hypotheses. Combining them under one New York tag can hide a strong early window and weak late trading.
Typical killzone times—and why lists disagree
Many educational charts express windows in New York local time. Examples often place an Asia window in the New York evening, a London window in the early New York morning, and a New York window around the US morning. Frequently quoted examples include approximately 20:00–00:00, 02:00–05:00, and 07:00–10:00 New York time, but these are conventions, not official standards.
Do not copy those examples into a plan without checking the methodology you intend to test. A one-hour difference changes which candles, news events, and trades enter the sample. Your plan should say something like: “London-context window: 02:00 inclusive to 05:00 exclusive in America/New_York, converted for each trade date.”
Daylight saving time: the most common session error
New York and London both observe daylight saving time, but their transition dates do not always match. For several weeks each year, the offset between the two cities differs from its usual value. A fixed UTC conversion can therefore shift a locally defined window by one hour, while a fixed local-clock rule changes its UTC value.
- Choose the anchor: exchange local time, New York local time, London local time, or UTC.
- Store original timestamps in UTC when possible.
- Convert each historical trade using an IANA timezone such as America/New_York or Europe/London.
- Let the timezone database apply the correct historical DST offset for that date.
- Document whether your rule follows a local clock or stays fixed in UTC.
- Spot-check dates before, during, and after both spring and autumn transitions.
Broker time, chart time, and exchange time
A broker chart may display server time, your browser may display device time, and an exchange may publish events in its local zone. Screenshots can therefore appear to show a different killzone even when the underlying instant is identical.
- Record the raw timestamp and timezone from the data source.
- Choose one canonical display timezone for analysis.
- Convert imported trades rather than manually adding a permanent offset.
- Verify whether timestamps mark order submission, fill, entry, exit, or candle open.
- For overnight positions, classify session from the planned entry or actual first fill—not the exit time.
Use killzones as a context filter, not an entry signal
A complete setup requires more than time. The window can make a setup eligible, but entry should still depend on predefined price conditions. One possible research model is:
- Bias: define the higher-timeframe condition without forcing a directional prediction.
- Location: identify a prior-day level, session boundary, range edge, or other premarked area.
- Window: allow new setups only during the named interval.
- Event: require an objective interaction such as a breach and reclaim.
- Confirmation: require the chosen close, displacement, BOS, CHoCH, or retest rule.
- Risk: calculate size from a fixed invalidation point and maximum account risk.
- Exit: define target, partials, and time-based cancellation before entry.
- No-trade conditions: block entries during unacceptable spread, news risk, or insufficient reward-to-risk.
If a sweep is part of the model, use the objective definitions in the liquidity sweep strategy guide. A wick during a killzone is not automatically a sweep, and a sweep is not automatically a reversal.
Build a session plan before the window opens
- Instrument and session window, including timezone and DST rule.
- Premarked levels and the reason each level was visible in advance.
- Eligible setup and confirmation model.
- Scheduled releases, holidays, rollover, and market-open events.
- Maximum trades, maximum daily loss, and stop-trading time.
- Conditions that cancel the idea, including a move already completed before the window.
- Screenshot before the window and after the session.
A maximum-trade rule is important because a named window can create pressure to participate. If no valid setup appears, “no trade” is correct execution. Use the overtrading guide to set attempt limits and a shutdown rule.
Journal tags for killzone and session trades
Keep strategy, session, context, and mistake labels separate. The trade-tags guide explains why combining every dimension into one label creates unusable samples.
- Setup: liquidity-sweep, pullback, opening-range-break, displacement-retest.
- Session: asia, london, new-york-am, london-close.
- Window status: inside-planned-window, outside-window, pre-window.
- Level: asia-high, asia-low, prior-day-high, prior-day-low.
- Context: scheduled-news, holiday, high-volatility, narrow-overnight-range.
- Execution: on-plan, early-entry, late-entry, exceeded-attempt-limit.
- Timezone audit: source-zone and canonical-zone when data comes from multiple feeds.
Do not encode outcomes into tags such as london-winner. Outcome already exists in P&L and R. Neutral labels let you compare all eligible trades instead of preserving only successful examples.
How to test whether a killzone adds value
- Freeze one setup definition and one timezone-correct window.
- Collect every eligible setup both inside and outside the window.
- Compare trade count, expectancy, win rate, average win, average loss, fees, and slippage.
- Compare clean execution separately from rule-breaking trades.
- Check whether one news day or outlier creates the difference.
- Repeat across enough independent days and more than one market condition.
- Validate the chosen window on future or untouched data.
This test asks whether timing improves the same setup. It does not compare a carefully selected killzone strategy with random outside-window trades. For a general method of grouping timestamped performance, use time-of-day trading analytics.
Common killzone trading mistakes
- Treating the opening minute as an automatic signal.
- Changing the window after seeing where the winning move occurred.
- Using EST as a year-round synonym for New York local time.
- Ignoring the unmatched US and UK daylight-saving transition weeks.
- Mixing broker-server timestamps with local screenshots.
- Assuming forex session behavior transfers directly to every market.
- Calling every session-high breach manipulation or a stop hunt.
- Taking repeated low-quality entries because the window is about to close.
- Reviewing only the clean textbook days and omitting no-trade or losing days.
Weekly review questions
- How many eligible windows occurred, and how many produced a valid setup?
- Did trades inside the window differ from the same setup outside it?
- Was performance driven by setup quality, session context, or execution mistakes?
- Were timestamps and DST conversions correct?
- Did scheduled news explain unusual spread or volatility?
- Did the session rule reduce poor trades or merely reduce sample size?
- What single rule will remain fixed for the next sample?
Review session clusters in the trading diary calendar, then use the weekly trade review to choose one evidence-based adjustment. Avoid redesigning the window after every week.
How Traderizz supports session-based review
Traderizz keeps timestamps, strategy labels, session tags, screenshots, P&L, and R connected to each trade. Tag Asia, London, and New York context consistently, inspect the relevant days in trader diary, and compare the same setup across windows without relying on memory.
The strongest use of a killzone is modest: it narrows attention to a planned period in which a defined setup may be worth observing. The edge, if one exists, must appear in repeatable price rules and timestamp-correct data—not in the name of the window.