Skip to content

Performance & Research

Data over assumptions.

This page is built for verified MetaTrader 5 reports — backtest, demo, live and prop accounts, strictly separated. Until verified data is published, it says so plainly instead of filling the space with numbers.

Performance dashboard

Loading chart…

No performance promise. Past results — whether backtest, demo or live — are not a reliable indicator of future results.

Methodology

How to read these numbers

Numbers without context mislead. These rules apply to everything shown here.

  • Backtest ≠ live

    A backtest replays history with known data. Spreads, slippage and execution in live markets differ — results can deviate significantly.

  • Demo ≠ real money

    Demo accounts simulate fills. Real liquidity, slippage and the psychological pressure of real money are missing.

  • A short profitable phase is no proof

    A few good weeks say little about robustness. A meaningful assessment needs many trades across different market phases.

  • Result and drawdown together

    Every result is shown next to its maximum drawdown. Return without its risk is not a result.

  • Costs are part of the result

    Spread, commission, swap and slippage assumptions are stated for every dataset — a result without costs is a hypothetical.

  • Versioned systems

    Each dataset belongs to exactly one system version. A change to the system starts a new evaluation instead of extending an old one.

Publication

How verified MT5 reports are published

Verified data follows a fixed path before it appears in this dashboard.

  1. Original report

    The unedited MetaTrader 5 report — Strategy Tester or account history — is the starting point. No screenshots, no excerpts.

  2. Context check

    Period, account type, broker, system version and cost assumptions are documented and checked for plausibility.

  3. Publication

    Key figures, equity curve and drawdown appear here together with the source and the reporting period.

  4. Traceability

    Reports remain assigned to the system version they were created with, so later changes can be compared.

Research process

Report. Diagnosis. Change. Test.

Development follows a controlled cycle. Filters are not added because they improve a historical test — they must address an identifiable error and hold up outside the optimisation period.

  1. MetaTrader report

    Every evaluation starts with the raw report, not with impressions.

  2. Diagnosis

    Which trades failed, under which conditions, and why?

  3. Scoped change

    One clearly defined change that addresses the identified error.

  4. Renewed test

    A fresh demo or forward test before any conclusion is drawn.

What you will not find here

  • Promises of returns or “guaranteed” results
  • Selected screenshots without period and account type
  • Hypothetical results presented as real trading
  • Win rates without the drawdown that came with them

Privacy settings

We only load third-party content (TradingView charts) after your consent. Everything else on this site works without cookies from third parties.