Prop Firm Slippage: Measure Execution and Calculate Pips

Slippage is the difference between a defined reference price and the actual fill. It can be favourable or adverse. Network delay is one possible contributor; liquidity, order type, execution policy and the account environment also matter. A lower ping alone does not establish a better fill or a profitable strategy.

Calculate the price difference correctly

Hypothetical EUR/USD buy examples: one pip is 0.0001 and the contract is 100,000 EUR per lot. In a USD-denominated result, one pip for one lot is therefore USD 10. These are arithmetic examples, not measured trades, provider specifications or a claim that delay caused a particular fill.

On a five-decimal EUR/USD quote, 0.00001 is one point and ten such points make this example’s pip. Lot volume is not measured in pips. Use the instrument’s actual contract size, tick size, tick value and profit currency; this USD calculation cannot simply be applied to gold, futures or another account currency.

Keep a request-to-fill record

• Account, platform build, exact symbol and simulated or other execution environment.
• Buy/sell side, order type, volume, request identifier and reference bid/ask with its timestamp.
• Send, response and execution times, with time zones and clock synchronisation documented.
• Every fill price and volume, partial fill, rejection, requote and relevant server response.
• Spread at the reference time and commission separately from the price difference.

Compare like-for-like observations, including both favourable and adverse fills. A round-trip network ping is not the complete order-processing time. A quoted price from a different feed or timestamp is not proof of a broker markup. Keep missing records visible rather than labelling them zero slippage.

Order type and infrastructure change the test

A market request does not guarantee an executed trade. Limit, stop and stop-limit orders have different conditions; an unfilled limit is not a zero-cost equivalent to a filled market order. Check the symbol’s execution and filling policy. A stop level is not a guarantee of the eventual fill price.

If you test a different host or VPS location, record before/after network and fill data under comparable conditions. No universal 2 ms, 20 ms or 100 ms threshold establishes suitability. A VPS may change the network path; it does not eliminate gaps, liquidity limits, server processing or software failures.

For a prop-firm programme, check the selected account’s automation permissions, loss formula and reset time. Include other positions, charges and possible execution failures. Do not infer a universal 5% limit or guaranteed compliance from an EA setting.

Primary technical references checked on 15 October 2026: MetaQuotes symbol specification and commission fields; order execution and history; order types and execution modes.

JPTC publishes monthly figures from its own broker statements on the results page. Those are not an independent broker-cost study, an execution simulator or tests of another EA. JPTC hosts its separate Algo: customers install nothing, run nothing and need no VPS. The EA Hub has its own version-specific scope; this article establishes no automatic commission calculator, latency guarantee, permanent compliance or challenge pass.

Continue with the cost ledger

FAQ