MetaTrader 5 (MT5) — two copies, one account — South Africa

Measured order execution — Standard

How orders actually filled when real market orders were placed on Exness’s MT5 feed — fill time, slippage and rejects by order size:

Small sample (a few round-trips per size); indicative. The same pricing engine feeds every platform the broker offers.

MetaTrader 5 (MT5) at Exness

• Every copy of MetaTrader 5 carries the same catalogue: 21 timeframes, 38 built-in technical indicators and 44 analytical objects. An entry present in one copy and missing in another is a difference of build, and no account setting will add it.
• Order types belong to the program as well — market orders plus six pending types, each with optional Stop Loss and Take Profit. A copy that offers fewer than that is not the same build as one that offers all of them.
• Depth of Market and the built-in economic calendar work the same way: they are there because the program provides them, not because a particular account unlocks them.
• What the connection provides is the other list — which instruments appear and how their symbols are spelled. Two copies pointed at different places show different lists while the account behind them does not change.
• Multi-asset coverage across forex, metals, crypto, energies, stock and index CFDs is part of that second list, which is why one copy can offer an instrument the other has never heard of.
• Windows, macOS, the MT5 WebTerminal and the mobile apps are separate builds of one program, so a difference between a desktop copy and a phone is a build difference before it is anything else.
• MetaTrader 5 works with every Exness account type, which is what makes the account useless as an explanation: it is identical in both copies while they disagree.
• Positions stay in step across desktop, web and mobile on one account. When two copies show different positions, they are not looking at one account and the comparison has to start again.
• Naming the side before changing anything is the point of all of this: capability is fixed by the copy, content arrives with the connection, and the account is the control that makes the test readable.

Which Exness platform should you use?

Exness offers several platforms — choose by pricing model, what you trade and your device. All connect to the same account.

The test that separates the two

The two causes are told apart by holding one of them still. Point both copies at the same connection and compare again: whatever difference remains cannot come from the connection, because both now have the same one. Then take a single copy and sign it into each connection in turn: whatever changes cannot come from the build, because the build did not move. Two comparisons, and the cause has a name.

Most reports skip this and describe the symptom instead — it works on the laptop and not on the desktop. That sentence contains two variables at once and cannot be answered as it stands. Saying which of the two comparisons was actually made turns it into a question with one answer.

What a build difference looks like

Build differences are about capability. A menu entry that is not there, an order type that cannot be selected, a chart object absent from the list: the program either offers the thing or it does not, and signing in somewhere else changes nothing. Capability also stays put — the same copy behaves the same way tomorrow, and carrying the account elsewhere does not help.

Because capability travels with the copy, the remedy belongs to the copy too. Nothing about the account needs to change, and comparing account settings will turn up nothing at all — which is itself the signal that the search is being conducted on the wrong side of the line.

What a connection difference looks like

Connection differences are about content. The instrument list is longer or shorter, a symbol carries a suffix in one copy and not in the other, a market visible in one window is absent from the second. These differences arrive with the connection chosen at sign-in and they leave with it, which makes them easy to confirm and easy to misread as faults in the program.

The tell is reproducibility across copies. If the second copy shows the same content once it is signed into the same place, the copies were never the problem and the difference was content all along. If it still does not, the question moves back to the build and the first comparison has to be repeated properly.

Isolating the cause in two comparisons

1. Write the difference down as one sentence about one observable thing.
2. Sign both copies into the same connection and look again. A difference still there belongs to the build.
3. Sign one copy into each connection in turn. A difference that moves with the connection belongs to the connection.
4. Confirm that the account number and the open positions match in both copies — if they do not, the comparison was never between two views of one account.

One variable at a time. A comparison that changes both at once cannot name a cause, however carefully it is described.

Which side explains the difference

Read the table as a test rather than a list of faults: the same account in both copies is what makes the comparison valid at all.

Related Exness pages