> 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/free-tools/eval-simulator.md).

# Eval Simulator

Run your numbers against a real firm's challenge rules and see your odds of passing.

The Eval Simulator estimates your odds of passing a prop-firm challenge before you pay for it. You enter your trading numbers and pick a challenge. It plays out 1,000 possible paths and summarises them.

## Run a simulation

{% stepper %}
{% step %}

### Enter your numbers

Enter your win rate, your average win and average loss in R, and how many trades you take per day.
{% endstep %}

{% step %}

### Pick a challenge

Choose a firm preset. Current presets are FTMO 100K, Apex 50K, FundedNext 100K and Alpha 100K.
{% endstep %}

{% step %}

### Read the results

The simulator runs 1,000 seeded paths through the challenge's profit target, daily drawdown, maximum drawdown and trading-day rules.
{% endstep %}
{% endstepper %}

## What the results mean

| Name                 | What it means                                                    |
| -------------------- | ---------------------------------------------------------------- |
| **Pass probability** | The share of paths that hit the profit target without breaching. |
| **Bust probability** | The share of paths that breached a drawdown limit.               |
| **Days to pass**     | How many trading days the passing paths usually took.            |
| **Equity fan**       | The spread of equity paths over time, from worst to best.        |

## Your expectancy decides the outcome

Win rate on its own tells you little. A 40% win rate with 2R winners beats a 60% win rate with 0.5R winners. The simulator works from your expectancy in R. See [R and expectancy](/concepts-and-reference/r-and-expectancy.md).

{% hint style="warning" %}
The simulator is a model, not a promise. It assumes your future trades look like the numbers you entered. If those numbers come from a handful of trades, treat the result as a rough guide.
{% endhint %}

## Inside the Platform

Signed-in traders get a second mode. It resamples your own backtest results instead of numbers you typed in. See [Simulator](/platform/simulator.md).

## Next steps

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Calculators</strong></td><td>Size trades and read your limits.</td><td><a href="/free-tools/calculators.md">Calculators</a></td></tr><tr><td><strong>R and expectancy</strong></td><td>The one number that decides profitability.</td><td><a href="/concepts-and-reference/r-and-expectancy.md">R and expectancy</a></td></tr></tbody></table>


---

# 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/free-tools/eval-simulator.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.
