> For the complete documentation index, see [llms.txt](https://docs.tradesurge.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tradesurge.co/platform/dashboard/surge-score.md).
# Surge score
The Surge score is a 0 to 100 readout of how well you trade, built from expectancy and consistency. Win rate cannot move it.
The Surge score is one number from 0 to 100 that sums up the quality of your trading. It rewards positive expectancy that is spread across many days, not one lucky session. It is labelled beta while real data shapes the final formula.
{% hint style="info" %}
**Beta.** The Surge score formula will change as more live data comes in.
{% endhint %}
## How it is calculated
The score multiplies two things:
1. **Expectancy**, your average result per trade in R, scaled so that -1R counts as 0 and +2R or better counts as 1.
2. **Consistency**, which is 1 minus your best day's share of your total R.
The result is multiplied by 100 and rounded.
## Why consistency matters
Many firms have a consistency rule that caps how much of your profit can come from one day. A trader who makes all their R in one session scores low, even with high expectancy.
## Win rate is not an input
The score has no win-rate input at all. A high win rate with small wins and large losses cannot lift it.
## What the bands mean
| Name | What it means |
| -------------------- | --------------------------------------------------------------- |
| **Low (0 to 33)** | Negative or thin expectancy, or results that depend on one day. |
| **Mid (34 to 66)** | Positive expectancy with some concentration. |
| **High (67 to 100)** | Strong expectancy spread across many days. |
{% hint style="info" %}
The same score will power public profiles and the leaderboard, which are planned. Your private number and your public number will always be the same.
{% endhint %}
## Next steps
---
# 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.tradesurge.co/platform/dashboard/surge-score.md?ask=&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.