> For the complete documentation index, see [llms.txt](https://chartschool.stockcharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://chartschool.stockcharts.com/table-of-contents/index-and-market-indicator-catalog/stockcharts-high-low-percent.md).

# StockCharts High-Low Percent

## Overview <a href="#overview" id="overview"></a>

High-Low Percent (HL Percent) is a breadth indicator that measures the percentage of Net New Highs for a particular group of stocks, such as an index or ETF. Net New Highs equals the number of 52-week highs less the number of 52-week lows. High-Low Percent equals Net New Highs divided by the total number of stocks in the group. High-Low Percent fluctuates between -100% and +100%. Chartists can use this indicator to create oscillators and the High-Low Line.

## Details <a href="#details" id="details"></a>

**Symbol Group:** High-Low Percent

**Publisher**: StockCharts

**Update Frequency:** End of Day (EOD). These indicators are updated after the market close, usually by 6:00 PM ET.

**Links to Current Symbols:** [High-Low Percent](https://stockcharts.com/search/?q=%22High-Low%20Percent%22\&section=symbols)

## Data Characteristics <a href="#data_characteristics" id="data_characteristics"></a>

StockCharts uses a three-step process to calculate breadth indicators. First, StockCharts maintains component lists for these indices. Second, our scan engine uses these component lists to run scans based on the price data for the individual stocks. Third, the data is then updated and published to our website. This “in-house” data may differ from other sources due to differences in the index components and price data. Index components change and require updates on a regular basis. Additionally, note that StockCharts uses dividend-adjusted data for its calculations, while other sources may use non-adjusted data.

## Chart Example <a href="#chart_example" id="chart_example"></a>

<figure><img src="https://436553459-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FERtrZrZOhufFzk6ZQO4B%2Fuploads%2Fx20tHj2EJHUT0EaIQQ8v%2Fsym-hlp-spxexam.png?alt=media&amp;token=52409e32-40d3-47bb-bb01-b87970116e91" alt=""><figcaption></figcaption></figure>

## Symbol List <a href="#symbol_list" id="symbol_list"></a>

StockCharts.com users can access [an up-to-date list of symbols](https://stockcharts.com/search/?q=%22High-Low%20Percent%22\&section=symbols) for all our High-Low Percent Indicators. From this list, click the “Mentions” icon to the right of a specific symbol for more details about the symbol, as well as recent mentions in Public ChartLists, blog articles, and more.

### Additional Resources <a href="#additional_resources" id="additional_resources"></a>

### ChartSchool Articles <a href="#chartschool_articles" id="chartschool_articles"></a>

[**High-Low Percent**](/table-of-contents/market-indicators/high-low-percent.md)\
A breadth indicator that measures the percentage of net new highs within a particular group, such as a SPDR or index ETF.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://chartschool.stockcharts.com/table-of-contents/index-and-market-indicator-catalog/stockcharts-high-low-percent.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.