CFDs are complex instruments and come with a high risk of losing money rapidly due to leverage. Trade only with money you can afford to lose.
Open Exness Account →
Measured data

Exness Execution — Measured Fills, Read Against the Fields Nobody Set — the Philippines

Four things in an order window hold a value before anybody touches them: the execution mode, the deviation allowance, the volume and, on a pending order, the expiry. The figures below record what real market orders did on this account — which is a statement about two of those fields and about none of the rest. Measured 2026.07.02 16:38.

Open Exness Account →

Founded 2008  ·  100+ instruments  ·  Planning pages for people who cannot watch all day

An order window is never empty. Before a first trade it already holds an execution mode that arrived with the account and the symbol, a deviation allowance, a volume, and — on a pending order — an expiry, and normally only one of those four is ever changed by the person sending the order. The measured table on this page records what market orders actually did here: how long a fill took, how far the price moved between screen and ticket, and how often size was refused. It answers to the mode and to the volume. It says nothing about the deviation box, and nothing at all about expiry.

Which default each figure belongs to

A latency figure belongs to the mode: it counts the time an order spent travelling, and the mode is the field that decides whether that journey can end in a price being re-offered instead of filled. A slippage figure belongs to the price the ticket accepted, which is what a deviation allowance is written to bound. A reject belongs to size. The expiry belongs to none of them, because a market order has no waiting to do. Reading the columns without knowing which field each one answers to is how a number ends up applied to the wrong setting.

Execution speed and fill quality vary with market conditions, liquidity and position size.

What the fills did, one size at a time

InstrumentLot sizeAvg executionSlowest fillAvg slippage (signed)Better / zero / worse fillsRejects
EUR/USD0.01151 ms187 ms-0.3 pts1 / 2 / 00
EUR/USD0.1151 ms172 ms-0.3 pts1 / 2 / 00
EUR/USD1146 ms172 ms-0.3 pts1 / 2 / 00
GBP/USD0.01141 ms156 ms+0.7 pts0 / 1 / 20
GBP/USD0.1130 ms140 ms+0.0 pts0 / 3 / 00
GBP/USD1135 ms156 ms+0.3 pts0 / 2 / 10
XAU/USD (Gold)0.01141 ms172 ms+0.0 pts0 / 3 / 00
XAU/USD (Gold)0.1151 ms172 ms+80.0 pts1 / 1 / 10
XAU/USD (Gold)1130 ms141 ms-72.3 pts2 / 1 / 00

Across 27 measured round-trips the average fill took 130–151 ms depending on instrument and size, with 0 rejected orders in total. Signed slippage is the distance between the price on the screen and the price on the ticket, and the sign says which side of the screen price the fill landed on.

Points, signed: a minus is a fill on the better side of the screen price, a plus is a fill on the worse side. Of everything in this table, the rejects column is the one a deviation allowance would be expected to touch first.

What the probe left alone

  • Market orders — the kind that takes the price the book offers rather than asking for one to be held — sent from a MetaTrader 5 terminal.
  • The clock ran inside the terminal, from the moment the order left it to the moment the confirmation came back.
  • Volume was the one field deliberately moved, stepped 0.01 to 1.00 lot, because it is the default that gets overwritten first and re-read last.
  • Everything else in the window stayed where it was found. Fills depend on liquidity, account and market conditions, and can differ.

Measured in-terminal on Exness’s own MetaTrader 5 pricing feed and symbol specifications, refreshed on a schedule. All figures are indicative and change with market conditions.

Open Exness Account →

The mode was chosen for you, not by you

Of the four values sitting in the window, the execution mode is the one that is not a setting at all. It arrives with the account type and with the symbol, it is shown rather than offered, and it is the field that quietly decides what the other three can do.

That matters because the mode is what determines whether a price can be handed back to you for a second look before the order is filled, or whether the order simply takes whatever the book has when it gets there. Two traders on the same symbol, sending the same volume, at the same second, can get two different kinds of answer purely because their accounts arrived with different modes.

So the first honest question about any execution number is not how large it is. It is which mode produced it. A figure recorded on one mode is not a prediction for the other, and nothing in a millisecond column tells you which one you are on — the account does.

The allowance that only earns its keep when the price moves

A deviation allowance is a cap: it says how far the fill may drift from the price on the screen before the order is refused instead of filled. Left at whatever value it was found on, it is invisible for weeks at a time, because on a quiet instrument nothing ever gets close to it.

It becomes the most consequential number in the window on exactly the days it is hardest to think about it — a release, a thin hour, a gap. A wide allowance trades certainty of getting filled against certainty of the price. A narrow one does the reverse and hands back a refusal instead of a position. Neither is the safe choice; they are two different risks, and leaving the box alone is a choice for one of them made by not choosing.

The table further down does not settle this for you. It is a record of fills that happened, not of fills that a cap prevented. Read it for the size of the drift, then decide separately what drift you are willing to accept — those are two different questions, and only the first one has a measurement.

Volume is edited by everyone and re-read by nobody

The volume box is the one field almost every trader touches, which is precisely why it goes wrong. It opens on a value, gets typed over for one trade, and then keeps that value for the next order on a different instrument, where the same figure means something else entirely.

Size is also the field the measurement below is most sensitive to. The same instrument at 0.01 and at 1.00 lot is not the same request: it asks a different amount of the book, and the signed slippage column shows that plainly. If a single row from this table is going to be carried away in memory, it should be a row at the size actually traded, not the smallest one.

There is a cheap habit that fixes most of it: read the volume box out loud before the confirm, in lots, together with the instrument. It takes a second and it catches the one default that changes the size of everything else on the ticket. The trading calculator is where to check what that volume costs before it becomes a position.

Reading the order window before the first order

  1. Find the execution mode and note it. It is not a choice on this screen; it is a property of the account and the symbol, and it frames everything else.
  2. Look at the deviation allowance and decide, once and away from a live market, what drift is acceptable. Write the figure down rather than deciding it during a release.
  3. Read the volume aloud with the instrument name. Most size accidents are a value left over from the previous trade on a different symbol.
  4. On a pending order, look at the expiry before the confirm: left in its open-ended position it will outlive the session, the plan and the reason it was placed.
  5. After the fill, compare the ticket price with the price that was on the screen. That difference, not the millisecond count, is what the columns below are measuring.

None of the above changes an execution number. It changes which number applies to you.

Order-window fields and what the measured table can say about each

FieldWhere its value comes fromDescribed by the table on this page?
Execution modeArrives with the account type and the symbolYes — every figure here was produced under one mode
Deviation allowancePreset in the terminal, edited by the traderNo — the table records fills, not caps
VolumePreset on the ticket, overwritten by the traderYes — the table is read one lot size at a time
Expiry on a pending orderPreset open-ended until a date is setNo — a market order does not wait
Stop loss and take profitEmpty until filled in by handNo — the probe closed its own positions

Column three is about this table and no other. A probe run with a cap set would answer differently, and a different account type might answer differently again.

Frequently asked questions

Which fields are already filled in before a first Exness order?
The execution mode, the deviation allowance and the volume are all holding a value before anything is typed, and a pending order adds an expiry to that list. Only the volume is normally changed, which means three of the four are decided by not deciding.
Is the execution mode something the trader picks?
No. It is instant or market depending on the account type, and the terminal shows it rather than asking. It is the one field on the ticket that a habit cannot fix, because it was settled when the account was opened.
What does a deviation allowance actually limit?
It caps how far the fill price may drift from the price on the screen before the order is refused instead of filled. Widening it buys certainty of being filled and pays for it in price; narrowing it does the reverse.
Does the measured slippage here show what a deviation setting would have done?
No. These are fills that happened, so the drift shown is the drift that was accepted. A cap changes the refusal count, not the physics of the fill, and the rejects column is where its effect would appear.
Why does the volume box deserve a second look every time?
Because it keeps the last value it was given, and that value carried over from another instrument usually means a different amount of money at risk. Size is also what the slippage column is most sensitive to, so the row that matters is the row at the size actually traded.
Does an order expiry apply to a market order?
No. A market order is filled or refused straight away, so there is nothing for an expiry to govern. It only matters on pending orders, where the open-ended default lets an order outlive the reasoning behind it.
Do these figures apply to every account type?
They were recorded on one account, on the platform feed named in the method note, and they move with liquidity, instrument and size. Treat them as a reading taken under one set of defaults rather than a specification of the platform.

Related Exness pages