> For the complete documentation index, see [llms.txt](https://docs.candelacharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.candelacharts.com/statistics/ohlc-session-range-map-tm/sessions.md).

# Sessions

**The OHLC Session** **Range Map performs calculations that are specifically tailored to distinct trading sessions—commonly referred to as "killzones"—to deliver more focused and context-aware market analysis.**

By aligning with the natural rhythm of institutional activity across global financial centers, the script offers enhanced insight into price behavior during each key period:

* **Asia Session:** 20:00 – 00:00 (UTC)
* **London Session:** 02:00 – 05:00 (UTC)
* **New York AM Session:** 09:30 – 11:00 (UTC)
* **New York Lunch Session:** 12:00 – 13:00 (UTC)
* **New York PM Session:** 13:30 – 16:00 (UTC)
* **Custom**

Each session is treated as a distinct phase, allowing traders to observe how price interacts with liquidity and manipulation levels during specific windows of high institutional activity.

This session-based approach helps users identify patterns, anticipate market behavior, and refine entry or exit strategies with greater precision.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.candelacharts.com/statistics/ohlc-session-range-map-tm/sessions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.