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 FxPro Account →
Measured

Where Each Trading Condition Comes From · FxPro Tanzania

The hard numbers behind a Raw+ account, read straight from FxPro’s own MetaTrader 5 feed: contract specs, order rules and the 2,124 tradable instruments — last read 2026-08-19.

Open FxPro Account →

Min deposit $100  ·  Up to 1:200  ·  Rating 4.6/5

Two kinds of number share this page, and they should not be read the same way. The contract fields, meaning the minimum and maximum order, the lot step, the contract size, the tick value and the digits, along with the stops level and the account risk levels, are server properties: they are read from a live FxPro MetaTrader 5 Raw+ account and stay true until the broker changes the contract, not until the market moves. The execution figures are timed events, real market orders placed on the same account with each fill timed and reported per order size, from a short run and published as indicative for that reason. The instrument universe is a third thing again, a count taken directly on the trading server. Each block therefore carries its own read date instead of sharing one date for the page, because the three age at completely different speeds.

Contract specifications (measured)

InstrumentMin lotMax lotLot stepContract sizeTick value (USD)Digits
EUR/USD0.015000.01100,000$1.005
GBP/USD0.015000.01100,000$1.005
AUD/USD0.015000.01100,000$1.005
USD/CAD0.015000.01100,000$0.725
USD/JPY0.015000.01100,000$0.633
XAU/USD (Gold)0.015000.01100$1.002

Read live from FxPro’s MT5 Raw+ account. ‘Tick value’ is the cash change per minimum price increment, per standard lot, in USD — what one point is worth to your P&L. Last read 2026-08-19.

Order rules and account risk

  • Minimum order 0.01 lot and maximum 500 lots, in 0.01-lot steps (0.01 lot = 1,000 units on an FX major).
  • No minimum stop or limit distance (stops level 0) — you can place a stop-loss or take-profit right next to price, which suits scalping and expert advisors.
  • Margin call at 10% and stop-out at 0% margin level, as measured on the Raw+ account — confirm the live levels in your own terminal before risking capital.
  • Contract size 100,000 units per lot on FX majors and 100 oz per lot on gold.
Open FxPro Account →

Execution speed and slippage (measured)

InstrumentOrder sizeAvg fillMax fillAvg slippage (pts)At price / better / worseFails
EUR/USD0.0189 ms94 ms0.03 / 0 / 00
EUR/USD0.178 ms78 ms0.03 / 0 / 00
EUR/USD1.089 ms94 ms0.03 / 0 / 00
GBP/USD0.0183 ms94 ms0.03 / 0 / 00
GBP/USD0.183 ms93 ms0.03 / 0 / 00
GBP/USD1.088 ms94 ms1.01 / 0 / 20
XAU/USD (Gold)0.0183 ms93 ms5.6671 / 0 / 20
XAU/USD (Gold)0.1141 ms250 ms-4.3332 / 1 / 00
XAU/USD (Gold)1.083 ms94 ms9.6671 / 0 / 20

Measured by placing real market orders on the Raw+ account and timing each fill; slippage is the price difference (in points) between the click and the fill, and ‘at price / better / worse’ counts how those fills landed. Small sample (a few round-trips per size) — indicative, last read 2026-06-24.

Instrument universe (measured)

FxPro’s live MT5 server carries 2,124 tradable instruments — the real count, not a rounded marketing figure. The major tradable asset classes:

Asset classInstruments
Stocks1,857
Forex75
Futures57
ETFs46
Cryptos37
Spot22
Metals12

Counted directly on the trading server. Availability of a specific instrument can vary by account and region.

Fields, timings and counts

This page mixes three kinds of measurement, and the difference between them is not cosmetic. A field is read: the server holds a value for the instrument on that account type, and reading it is a lookup that returns the same answer to anyone looking at the same account. A timing is produced: an order has to be sent and a fill has to come back before there is anything to record at all. A count is taken: the tradable universe is enumerated on the server at a moment in time.

Each method has its own failure mode. A field can be right and irrelevant, if it was read on an account type you do not hold. A timing can be right and unrepresentative, if the run was short. A count can be right and misleading, because availability differs by account and by region, which the note under the table says outright.

Keeping the three visibly separate is the point of the layout. Running them together into one impressive block of numbers would be easy, and the result would be a page on which nobody could tell which figures will still be true next month.

Different numbers, different shelf lives

The contract fields have the longest life of anything published on this site. A contract size of 100,000 units per FX lot and a 0.01-lot minimum are terms rather than observations, and they read the same tomorrow unless the broker restructures the instrument.

The spread readings on our measured spreads page sit at the other end: they are out of date within a day, which is why they are rebuilt daily and stamped. The timing figures here age in a third way again, not with the market but with the infrastructure behind it, so their date is meaningful in months rather than in hours.

That is why the page prints a read date under each block instead of one line at the bottom. A single date covering three clocks would be the neatest possible way of saying nothing.

What the specification fixes and what it leaves open

Read together, the contract fields settle a surprising amount before any money moves: the smallest position available, the increments above it, how much of an instrument one lot represents, and whether a protective order may sit close to the price. A stops level of zero, for instance, is what makes a tight stop a question of strategy rather than of permission.

What the fields cannot say is what happens between the click and the fill. No stored value covers that; it has to be produced by sending orders and watching what comes back, which is what the execution block is, and why it is the only part of this page carrying a short-sample warning.

The two halves answer different questions, and the useful habit is to ask which of them a claim about trading conditions rests on. For the cost side of the same account, the measured spread and the fixed commission are set out on our cost overview.

Frequently asked questions

What is a contract specification field, and what changes it?
A property of the instrument on a given account type, stored on the trading server: the minimum and maximum order, the lot step, the contract size, the tick value and the number of digits. It changes when the broker changes the contract, not when the price moves, which is why a field read a while ago can still be current.
What is the minimum and maximum trade size at FxPro?
On the measured Raw+ account the minimum order is 0.01 lot and the maximum is 500 lots, in 0.01-lot steps. One standard lot is 100,000 units on an FX major, so the smallest order there is 1,000 units.
Which numbers on this page were timed rather than read?
The execution block, and only that. Those figures come from placing real market orders on the Raw+ account and timing each fill, with the price difference between click and fill recorded and the fills counted as at price, better or worse. Everything else here is read from a field or counted on the server.
Why does the execution block carry a different date from the other tables?
Because it is a different kind of measurement with a different shelf life. Contract fields are stable and are re-read on the daily cycle; a timing run is a short sample from a particular session and stands until it is run again. One date for the whole page would hide that difference.
Why is the execution table called indicative?
Because the run behind it is short, a handful of round trips at each order size taken on one occasion. A run that size can establish that orders were accepted, filled and priced close to the click. It cannot stand in for a month of conditions, and sizes are listed separately rather than merged so that the table is read row by row.
Does FxPro have a minimum stop-loss distance?
No. The measured stops level is 0, so a stop-loss or take-profit can sit right next to the price. That is an account property read from the server rather than an inference from behaviour, and it is listed with the order rules above.
Where does the instrument count come from?
It is counted directly on the trading server across stocks, forex, ETFs, futures, cryptos, spot and metals, and it is shown in the table above rather than written into this text, because the count moves as listings are added or retired. Availability of a specific instrument can vary by account and region.
A field here does not match my platform, what would explain it?
The account type first, since these were read from a Raw+ account and other account types can carry different values for the same instrument. Then the symbol itself, because a broker can list variants of one instrument on different contract terms. The read date under each block says when the value was taken.

Related FxPro pages