How Performance Is Calculated
This page explains the definitions and rules behind the GAT Trading History — how setups are counted, how outcomes are classified, how pips are calculated, and what is not published.
What counts as one trackable entry
A strategy setup is one unique XAUUSD trade opportunity defined by three required components:
Performance is counted once per canonical strategy setup. Reports from multiple connected accounts do not multiply the same strategy setup in the public dataset.
When multiple account reports exist for the same setup, one representative outcome is selected using a deterministic precedence: automatically-closed outcomes are preferred over manually-closed; within those, the deepest take-profit level reached takes precedence; then the highest realised pips; then the earliest recorded entry. The same precedence is used by the internal admin view — there is one consistent definition, not separate counting methods for public and internal data.
Setups that are cancelled before execution are logged but not counted in win/loss calculations.
Only setups for which both the entry and the outcome can be confirmed are counted. Setups where the EA failed to execute due to a connectivity issue are logged separately as execution failures and excluded from win/loss figures.
Setups that are cancelled before execution are logged but not counted in win/loss calculations. Open baskets are excluded from all published statistics until they close.
How target reach rates are counted
For each setup, whether price reached each take-profit target while the basket was open is tracked independently of the final outcome.
Target reach rates are cumulative: a setup with a TP3 outcome is also counted as having reached TP1 and TP2. This means the TP1 reached count equals all Win outcomes; TP2 reached equals TP2+ outcomes; TP3 reached equals TP3 outcomes only.
A setup is eligible for the TPN reach rate only if it was tracked with at least N defined targets. TP3 reach rate counts only setups that had three defined targets — this prevents setups with fewer targets from artificially reducing the TP3 rate.
A setup that hits TP1 and then reverses to the stop-loss is classified as a Loss. TP1 reach is still recorded. Outcome and reach are separate figures.
This distinction matters for honest reporting: a system with a high milestone-reach rate but poor final outcomes would overstate performance if milestone reach were labelled as wins. Both are shown separately so the data is transparent.
How a closed basket is classified
When a basket closes, its final outcome is assigned using the following definitions. These definitions apply consistently across all strategies.
Note on BE protection: BE protection triggered means that at least one applicable position had its stop-loss successfully moved to the configured break-even level. It does not mean that the strategy later closed exactly at entry, and it does not determine the final Win, Loss or Break-Even outcome. Spread, commission, slippage and execution differences may affect the final realised result. BE protection triggered is reported as a separate count, not as a final outcome.
How pips are calculated
(target price − entry price) / 0.10 for BUY; (entry price − target price) / 0.10 for SELL. Loss pips are negative.This is a consistent definition applied to every record in the dataset, regardless of when the setup was traded. It measures the distance from entry to the outcome level as recorded — not intra-trade equity movements, partial close prices, or trailing stop levels.
What is not published
Some data exists internally that does not appear in the public trading history.
- Individual account identifiers — no client names, MT5 account numbers, or broker account details appear in any published results.
- Monetary profit or loss — pip figures are published, not account balance changes, dollar P&L, or percentage returns.
- Internal strategy codes — internal strategy identifiers are not published. Results are shown by symbol and direction only.
- Unverifiable setups — any setup for which the entry or outcome cannot be confirmed is excluded. Only what can be verified is counted.
- Execution failures — setups where the EA failed to execute due to connectivity or technical issues are logged as failures and excluded from win/loss figures.
- Selectively filtered results — the published dataset includes all tracked closed setups. Losing periods, losing strategies, and underperforming months are not removed.