Why a MetaTrader report and a Forge test differ

Forge API 1Updated 14 Oct 2026

The same rules, tested in MetaTrader and in Forge, rarely give the same numbers at first. Each cause below is one the engine names.

Spread

MT5's tester uses the spread set in the tester or recorded in its history; a Forge run uses the spread in its own data or broker facts, so entries and exits land at different prices.

Costs, swap and funding

Server time offset

The report's times are the broker's server time and Forge's are UTC, so every time differs by the same offset.

Broker time and the trading day

Daylight saving

The broker's offset changes by an hour twice a year, so times differ by one more hour for part of the year only.

Broker time and the trading day

Swap

Both testers charge today's swap rate on past nights, and Forge books no credit, so trades held overnight end differently.

Costs, swap and funding

Price detail

MT5 may replay real ticks, generated ticks or open prices only, while Forge fills on its data's bars or minutes, so a stop and a target inside one bar can resolve differently.

Bar close and fills

Fill rules

Which price a pending order or a stop fills at, and which of a stop and a target fills first in one bar, follow each tester's own rule.

Bar close and fills

Commission

The report uses the account's commission, and a Forge run uses the commission set for it.

Costs, swap and funding