Version control
Give the rules snapshot an identifier and date. If official terms change, create a new simulation version instead of overwriting old results.
Editorially reviewed 24 August 2026
Freeze the exact product terms
CHECK 35Product names, phases, objectives, loss calculations, trading restrictions, and fees can change. Before an FTMO practice run, save the current official terms for the exact account product and jurisdiction. This page should not substitute remembered or third-party numbers for that source.
Translate the saved terms into test events: when daily loss resets, how floating P&L and costs count, what happens at a breach, and which trades are prohibited. Add a personal buffer, then run multiple chronological windows without changing strategy risk after a fortunate or poor start.
Give the rules snapshot an identifier and date. If official terms change, create a new simulation version instead of overwriting old results.
Convert the official reset timezone to every historical timestamp, including daylight-saving changes. A “day” is a rule definition, not a chart label.
Record the first rule breached, equity immediately before it, buffer remaining, contributing trades, and whether execution stress changes the outcome.
The official agreement defines the simulation; an undated checklist cannot.
Open the official FTMO product and legal pages that apply to the account being considered. Save the URLs and the date checked. Product names, phases, objectives, loss calculations, permitted methods, and commercial terms can change, so a copied table from an old review should never drive the simulator.
| Term | Value from current official source | Simulator implementation |
|---|---|---|
| Product, phase, account currency | Record exact name and source | Label every run with this version |
| Profit objective and qualifying activity | Record formula and exceptions | Evaluate only after all costs and eligibility checks |
| Daily loss rule and reset timezone | Record reference values and reset event | Snapshot the correct state at the reset |
| Maximum loss rule | Record balance/equity basis and movement | Check after every account event |
| Restrictions and duration | Record holding, news, inactivity, and time terms | Flag violations separately from P&L |
Explain every term in plain language and reproduce several hand-calculated edge cases.
Estimate expectancy, cost share, drawdown, and losing sequences without an objective deadline.
Apply the FTMO snapshot, clock, restrictions, and safety buffer to sequential unseen dates.
Repeat independent windows and stress spread, slippage, missed trades, and same-bar ambiguity.
Report the proportion of independent windows that reached the objective, breached first, timed out, or remained unresolved. Keep median and worst-path drawdown, lowest buffer, cost share, deviation count, and concentration by month. Do not turn a single favourable path into a readiness claim.
Before payment: verify the official terms again. If the rule snapshot changed, create a new version and rerun the relevant scenarios.
One reproducible testing idea, with its rules, limitations, and review questions made explicit. In your inbox every week.
Measured from 28 million candles
Beginner exploration
Open each answer for a plain-language way to read FTMO Backtesting Plan: Simulate Current Rules Before Paying, test it carefully and decide what to explore next.
This page focuses on “FTMO Backtesting Plan: Simulate Current Rules Before Paying”.Create an FTMO practice plan from current official product terms, with versioned rules, reset clocks, floating P&L, costs, breach logs, and unseen runs.For “FTMO Backtesting Plan: Simulate Current Rules Before Paying”, a beginner should identify what the practice guide measures, assumes or teaches before acting on its conclusion.Treat this page's account of “FTMO Backtesting Plan: Simulate Current Rules Before Paying” as a learning reference rather than a prediction, signal or promise of future performance.
For “FTMO Backtesting Plan: Simulate Current Rules Before Paying”, copy the current official loss, target and eligibility rules before building a practice scenario.While exploring “FTMO Backtesting Plan: Simulate Current Rules Before Paying”, model the exact drawdown formula and reset clock rather than relying on a remembered headline limit.Keep your “FTMO Backtesting Plan: Simulate Current Rules Before Paying” record honest: judge the process by rule compliance and risk consistency as well as simulated profit.Before leaving “FTMO Backtesting Plan: Simulate Current Rules Before Paying”, re-verify the provider terms before paying because commercial conditions can change.
Turn one idea from “FTMO Backtesting Plan: Simulate Current Rules Before Paying” into a rule with explicit inputs, dates, costs and pass-or-fail conditions.Ask AI to expose missing assumptions in that “FTMO Backtesting Plan: Simulate Current Rules Before Paying” test, not to guess the next market move.Use the FXAbsolute AI Backtesting Lab to inspect calculations connected to “FTMO Backtesting Plan: Simulate Current Rules Before Paying” and the assumptions behind them.Reproduce any important “FTMO Backtesting Plan: Simulate Current Rules Before Paying” result and reserve unseen data before deciding that an apparent pattern is useful.
Continue your exploration of FTMO Backtesting Plan: Simulate Current Rules Before Paying with the beginner AI prompt guide, or inspect public calculations in the AI Backtesting Lab.