> For the complete documentation index, see [llms.txt](https://docs.thesports.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thesports.com/help-center/football/trend-data-in-football.md).

# Trend data in football

### What is trend data?

Trend data reflects the attacking intensity of the home and away teams during a match.

### How are trend values calculated?

Trend values are calculated based on attacking activity and ball possession.

### How often should the Trend API endpoint be called?

Trend data is available while a match is in progress. Use the match status to determine when to call the [**Real-time match trends**](/thesports-docs/basic-data/real-time-match-trends.md) API endpoint.

Call the API endpoint once every 1 to 3 minutes during the match. Trend values are updated at minute-level intervals. 

If you want to get the match trends for historical matches, you can use [**Match trends**](/thesports-docs/basic-data/match-trends.md) API endpoint.

### How to display trend data

The returned data can be plotted on an x-y axis:

* The x-axis represents time.
* The y-axis represents the attacking trend of each team.

Each value in the returned trend list represents the trend value for one minute.

<figure><img src="/files/Y4ZTz8sjP61Z0h1Ec38s" alt=""><figcaption></figcaption></figure>

### How is trend data handled during adding time?

#### **First-half adding time**

During first-half adding time, the trend list includes a separate value for each minute of adding time.

When the second half starts, these values are removed and combined into the 46th trend value.

For example, if the first half has five minutes of adding time:

* Before the second half starts, the trend list contains 50 values for the first half.
* After the second half starts, the trend list contains 46 values for the first half. The five minutes of adding time are combined into the 46th value.

#### **Second-half adding time**

If the match does not proceed to overtime, the trend values for second-half adding time remain in the trend list.

For example, if the second half has three minutes of adding time, the 46th, 47th, and 48th values represent the three minutes of adding time.

If the match proceeds to overtime, the trend values for second-half adding time are removed and replaced by overtime trend values.

For example, if the second half has three minutes of adding time:

* Before extra time starts, the 46th, 47th, and 48th values represent second-half adding time.
* After extra time starts, these values are removed. The new 46th, 47th, and 48th values represent extra time.


---

# 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.thesports.com/help-center/football/trend-data-in-football.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.