> For the complete documentation index, see [llms.txt](https://docs.spectralink.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spectralink.net/amie-advanced/metrics-reference/cycle-count.md).

# Cycle count

How many times a battery has been discharged and recharged over its life. It is the standard measure of how much work a rechargeable battery has done, and the main reason a battery loses [capacity](/amie-advanced/metrics-reference/battery-capacity.md).

## How it's counted

A cycle is one full battery's worth of discharge, however it is split up: running from 100% to 50% and recharging, twice, is one cycle, not two. The count is kept by the battery's own fuel gauge, which adds up the charge that flows out of the battery and increments the count each time the total reaches a full capacity. AMIE reports the count as the battery last sent it.

On a Versity handset there is one nuance worth knowing. The handset shuts itself down while the battery still holds a little charge, so running it from full down to 0% on screen draws slightly less than a full capacity. The fuel gauge counts the charge that actually flowed, not what the screen showed, so that run does not complete a cycle. The shortfall carries into the next one: after recharging, the battery may have to give up another 10% or 20% before the count goes up by one. The count is a close measure of how much work the battery has done, not a tally of how many times it was charged.

## How the product shows it

**Cycle Count** on [Battery details](/amie-advanced/using-the-platform/battery-details.md) and **Cycles** on the [Batteries inventory](/amie-advanced/using-the-platform/batteries-inventory.md) show the count itself. **Cycle Count** on the [Batteries overview](/amie-advanced/using-the-platform/batteries-overview.md) groups batteries into four bars:

| Bar         | Cycle count |
| ----------- | ----------- |
| **<100**    | 0 to 99     |
| **100-199** | 100 to 199  |
| **200-299** | 200 to 299  |
| **300+**    | 300 or more |

A battery with no recorded count is left out of every bar, and reads **0** under **Cycles** on the inventory while the detail page leaves the value blank.

## What the count tells you

Cycle count and capacity go together. Capacity falls as cycles accumulate, so a battery with many cycles and healthy capacity has more wear behind it than one with few. A battery with few cycles and low capacity has lost capacity for some reason other than use; age, heat and long spells fully charged all affect the reading — see [Battery capacity](/amie-advanced/metrics-reference/battery-capacity.md). Use the count to decide which healthy batteries to watch, and capacity to decide which to replace.

## Edge cases

* **Colors carry no judgment of the count.** On the inventory the **Cycles** figure is colored to match the row's health band; on the battery's own page it is always red, whatever the value.
* **0 has two meanings.** On the inventory a battery that has never reported a count reads **0**, the same as a battery that has genuinely done no cycles. The battery's own page leaves the value blank instead.
* **The count travels with the battery.** It is kept by the battery's own fuel gauge, so it follows the battery from handset to handset.

## Where you'll see it

* [Battery details](/amie-advanced/using-the-platform/battery-details.md) — **Cycle Count**
* [Batteries inventory](/amie-advanced/using-the-platform/batteries-inventory.md) — the **Cycles** column
* [Batteries overview](/amie-advanced/using-the-platform/batteries-overview.md) — the **Cycle Count** chart

## Related metrics

* [Battery capacity](/amie-advanced/metrics-reference/battery-capacity.md): what the cycles wear down


---

# 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://docs.spectralink.net/amie-advanced/metrics-reference/cycle-count.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.