> ## Documentation Index
> Fetch the complete documentation index at: https://docs.joinmobius.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure capital, costs, and date range for a backtest

> Set starting capital, date range, transaction costs, and execution frequency before running an AI-powered backtest on your Mobius trading strategy.

Before running a backtest, configure the simulation parameters to match your intended trading conditions. Accurate configuration leads to results that better reflect what you'd actually experience in a real account.

## Opening backtest configuration

After defining your strategy in chat, click **Run Backtest**. The configuration panel opens before the simulation begins.

## Configuration parameters

### Starting capital

The simulated portfolio balance at the start of the backtest. Default is \$10,000.

Set this to the amount you intend to deploy in a real or paper account. Position sizing rules in your strategy (e.g. "use 10% of portfolio per trade") are calculated as a percentage of this value.

### Date range

The historical period the backtest covers.

**Recommended ranges by strategy type:**

| Strategy type      | Recommended range                         |
| ------------------ | ----------------------------------------- |
| Intraday (1–5 min) | Last 30–180 days                          |
| Swing (daily)      | Last 3–5 years                            |
| Long-term trend    | 5 years or more                           |
| Crypto             | Last 1–3 years (data availability varies) |

<Tip>
  Include at least one full market cycle (a bull and bear phase) to see how your strategy behaves in different conditions.
</Tip>

### Commission

A flat dollar amount charged per trade, applied at both entry and exit. Default is \$0.

Most retail brokers (Robinhood, Schwab, Fidelity) charge $0 commissions on US equity trades. Set to $0 unless your broker charges commissions.

### Slippage

An additional percentage cost applied per trade to simulate the difference between the expected price and the actual fill price. Default is 0.01% per trade.

For liquid large-cap stocks and ETFs, 0.01%–0.05% is realistic. Increase for small-cap stocks or low-volume assets.

### Execution frequency

How often the bot evaluates signals during backtesting. This must match the bar frequency of your strategy's indicators.

| Frequency | Total bars (3-year range) | Use when                         |
| --------- | ------------------------- | -------------------------------- |
| Daily     | \~750 bars                | Most equity strategies           |
| 1 hour    | \~5,250 bars              | Intraday swing                   |
| 15 min    | \~21,000 bars             | Active intraday                  |
| 5 min     | \~63,000 bars             | High-frequency intraday          |
| 1 min     | \~315,000 bars            | Scalping (limit to 30-day range) |

<Warning>
  High-frequency backtests (1 min, 5 min) over long date ranges can take longer to run and are limited to shorter historical windows. See the [Backtesting concepts](/concepts/backtesting) page for max window limits by frequency.
</Warning>

## Running the backtest

Click **Run Backtest** after configuring parameters. Mobius fetches historical data, calculates all indicators, and runs the AI decision loop bar by bar. Results appear in the artifact panel within a few seconds for daily strategies, or up to 30 seconds for high-frequency intraday backtests.

## Interpreting results

After the backtest completes, the results panel shows:

* **Equity curve** — portfolio value over time
* **Total return %** — overall gain or loss
* **Annualized return** — return normalized to one year
* **Sharpe ratio** — risk-adjusted return (> 1.0 is generally good)
* **Max drawdown** — largest peak-to-trough decline
* **Win rate** — percentage of trades that closed in profit
* **Trade count** — total completed buy/sell pairs
* **Trade log** — every trade with entry date, exit date, price, and P\&L

## Running multiple backtests

You can run as many backtests as your plan allows per day. Each run uses one backtest credit. Refine your strategy in chat or the visual editor between runs to compare results. Version history is preserved so you can see how performance changed across iterations.