Market mechanics, measured on minute data since 2015

What more than a decade of minute data says about the trading day.

This is what can actually be measured on the DAX, FTSE, Nasdaq and Dow: when opening breakouts carry and when they fail, where an index's upward drift really comes from, why a filter shines in the backtest and adds nothing in trading. 87 studies, including a fresh scan of about 897,000 logged tests, each with its data basis, method and limits, including the ideas that did not survive the test. Plus the instruments that produce these numbers.

Loading market data…

Methodology

From hypothesis to running system

Five stages, documented on one continuous example: hypothesis, specification, in-sample measurement, validation gate, deployment.

  1. 01

    Hypothesis

    The starting point is an observation from our own trading: behaviour that seems to recur. Stated as a hypothesis about market, time window and condition, with no result yet and a clear null expectation.

    The desk where the observation happens: DAX and FTSE, same session, same setup.
    The desk where the observation happens: DAX and FTSE, same session, same setup.
  2. 02

    Specification & pre-measurement

    Rule, market, period, exit and cost model are fixed before the first number exists. A pre-measurement against a benchmark (random walk, base rate) decides on the full test bench; most candidates end here.

    Study: second candle on trend days →
    First evaluation: hit rate across the confirmation offset, four indices — confirmation helps, but not equally everywhere.
    First evaluation: hit rate across the confirmation offset, four indices — confirmation helps, but not equally everywhere.
  3. 03

    In-sample measurement

    The full history on minute data: episodes per market and setup, avgR with standard error and day-clustered t-statistic, spread and slippage at entry, regime decomposition by volatility and calendar.

    Study: edge persistence →
    Measured, not assumed: a fresh anomaly does not decay slowly — it falls off a cliff after one half-year.
    Measured, not assumed: a fresh anomaly does not decay slowly — it falls off a cliff after one half-year.
  4. 04

    Validation gate

    Out-of-sample split, rolling walk-forward, Monte Carlo on the daily series, edge persistence across epochs. The gate separates a mechanism from a fit to the past; failed hypotheses are published with their numbers.

    Study: validation gate →
    The gate in one picture: profit factor per rolling one-year window — no market stays above the threshold.
    The gate in one picture: profit factor per rolling one-year window — no market stays above the threshold.
  5. 05

    Deployment

    What passes the gate is implemented: as an open indicator on TradingView, as a utility on the MQL5 Market, or as an expert advisor with execution logic, risk limits and a reference backtest that is tracked in live operation.

    Study: MT5 algo reference →
    The finished EA in its reference backtest, out-of-sample 2023–2026 — a historical curve, not a return forecast.
    The finished EA in its reference backtest, out-of-sample 2023–2026 — a historical curve, not a return forecast.

The full methodology, documented in five phases →

Platforms

One standard, five platforms.

Built natively instead of lowest common denominator — MQL5, Pine, C#, Python. NinjaTrader and the cTrader tools are in preparation.

MetaTrader 5MQL5Tools + orders

The execution layer: runs unattended on live and prop accounts, with full access to orders, history and account state. MQL5 is close to C — fast but unforgiving: mistakes cost real money, which is why restart safety beats elegance.

Example: a drawdown guardian that enforces limits, or a recovery EA whose accounting nets out swap and commission.

TradingViewPine Script v6Tools + orders

The chart cockpit: Pine is deliberately limited — no file system, no external computation — which makes it fast to review and hard to obfuscate. Ideal for making context visible; unsuitable for heavy backtesting.

Example: projecting futures volume into CFD coordinates, or dealer-gamma levels as a chart overlay with alerts.

PythonPython 3.xTools + orders

The research layer everything else stands on: data engineering, backtest pipelines, walk-forward and Monte Carlo. Anything is possible — which is why methodological discipline matters more than the language itself.

Example: the research pipeline behind our studies (minute data, 15 markets, a random market as the zero line), or a walk-forward test bench for your own rule.

cTraderC# (.NET)Orders · tools coming soon

Full execution control in a grown-up language: C# with a real type system, proper testing and direct API access to every order. The choice when order logic gets complex and has to stay traceable.

Example: fine-grained partial executions with complete logging of every fill.

NinjaTrader 8NinjaScript (C#)Coming soon

The standard of the futures prop scene, technically C# family. In preparation — the risk utilities get ported first.

About

Background

KruegerAlgorithms grew out of our own trading: live in the markets for several years, research-driven from day one — because an idea is worth nothing until it has been quantified and tested. The systems here run by the same rules that get published.

What you see on this site is the part of the work that can be open: 87 studies on minute data since 2015, including a fresh scan of about 897,000 tests on 15 markets, 10 open instruments, 4 delivered projects — including the ideas that did not survive the test. You will not find signals here. Tools to measure for yourself — that you will.

  • Every number names its source: market, period, sample, cost assumption.
  • Negative results are published and filterable by verdict.
  • The instruments are open — recomputable, not a black box.
  • No return promises. No subscriptions.
More about how we work →

"Really cleanly solved! Congratulations!"

Returning client, MT5 EA projects — 4 orders

Quant development for your own rule set.

Specification, backtest on minute data with a cost model, walk-forward validation and implementation as an expert advisor for MetaTrader 5. The first step is an assessment of whether the rule set can be automated cleanly and what the test bench already says about it; it is non-binding.