Why Your Broker is Killing Your Scalping Edge (And Why IC Markets Fixes It)

[PTScalper]

If you are scalping the 1-minute or tick charts, your trading strategy is only half the equation. The other half is your infrastructure. I have seen countless traders build a profitable strategy on a demo account, only to bleed their capital dry in live markets. Why? Because they are trading on a standard market maker broker with a dealing desk.
When your profit target is 3 to 5 pips, a 1.5-pip spread means you are paying a 30% to 50% "tax" on every single trade before you even break even. Add in a 500-millisecond execution delay, and slippage will turn your precise entries into a game of roulette.
This is why a high-speed ECN (or Raw Spread) broker isn't a luxury for a scalper—it is an absolute requirement. Many high-frequency traders route their orders through IC Markets, and looking at the infrastructure shows exactly why ECN environments matter:
Near-Zero Spreads: True ECN brokers aggregate pricing from multiple institutional liquidity providers. IC Markets' Raw Spread account frequently hits 0.0 pips on major pairs during the London and New York sessions, with the EUR/USD averaging just 0.1 pips. You pay a flat commission (like $7 round turn on MT4) instead of getting chopped up by inflated, variable spreads.
Institutional Execution Speed: Speed is everything when capturing micro-fluctuations. IC Markets hosts its MetaTrader servers in the Equinix NY4 data center in New York and cTrader in London’s LD5. This hardware delivers average execution speeds of under 40 milliseconds. If you run an automated EA on a collocated VPS, your latency drops to under 1 millisecond.
Zero Restrictions & No Freeze Levels: A lot of retail brokers secretly restrict scalping by enforcing minimum distances on stop losses and limit orders. IC Markets features a freeze level of 0, meaning you can place your orders right inside the spread without being blocked. High-frequency algorithms and scalping are fully unrestricted.
The Bottom Line
You wouldn’t enter a Formula 1 race with a daily commuter car. If you want to trade like an institution by targeting rapid, micro-price movements, you need institutional-grade latency and pricing. Switch to a Raw Spread environment, eliminate the dealing desk interference, and watch how much cleaner your trade executions become.

[FTtrader]

Hi PTtrader,

from my point of view im able to make profit at the end even on bad broker, because biggest edge i see in looking for good trading setup.
But on another hand it is difference in long run, if i make 10-15k$ per month more for the same work

And i got it, once i will scale more it will be bigger difference thanks to liquidity.

[LondonScalper]

When your profit target is 3 to 5 pips, a 1.5-pip spread means you are paying a 30% to 50% "tax"

The cost arithmetic is the part worth keeping. The broker-brand wrapping around it is optional.

If your median target is a handful of pips, all-in round-turn (spread + commission + typical slip) has to be a small slice of that target or the strategy is a donation. That pushes you toward raw/ECN-style pricing and decent routing — true for any venue that can actually fill you, not a slogan for one logo.

What I verify myself, quarterly:

• Median and p95 slip by pair/session
• Reject rate on market orders
• Whether “raw” stays raw around rollover and thin minutes

A dealing-desk wide spread will kill a 3-pip scalp book. So will a fancy raw account with toxic slip. Measure the book you actually get — then choose infrastructure. Happy to compare measurement methods if useful; less interested in brand warfare.

[FTtrader]

When your profit target is 3 to 5 pips, a 1.5-pip spread means you are paying a 30% to 50% "tax"

The cost arithmetic is the part worth keeping. The broker-brand wrapping around it is optional.

If your median target is a handful of pips, all-in round-turn (spread + commission + typical slip) has to be a small slice of that target or the strategy is a donation. That pushes you toward raw/ECN-style pricing and decent routing — true for any venue that can actually fill you, not a slogan for one logo.

What I verify myself, quarterly:

• Median and p95 slip by pair/session
• Reject rate on market orders
• Whether “raw” stays raw around rollover and thin minutes

A dealing-desk wide spread will kill a 3-pip scalp book. So will a fancy raw account with toxic slip. Measure the book you actually get — then choose infrastructure. Happy to compare measurement methods if useful; less interested in brand warfare.

Hi LondonScalper,

You’ve isolated the exact math that separates scalable scalping from random variance. When the median target is 3 to 5 pips on a 1-minute or 5-minute chart, a 1-pip average drag (spread + commission + negative slippage) destroys 20-33% of your gross edge before the market even moves. The branding on the server is irrelevant; the execution routing and order book depth are everything.

Since you mentioned comparing measurement methods for that quarterly verification, here is a highly granular approach to quantifying that infrastructure, removing all marketing from the equation:

1. Custom Execution Logging

Relying on standard account statements masks the microstructure. A robust measurement script needs to log the exact delta between requested and filled parameters directly to an external database (like SQL) in real-time to prevent data loss.

Timestamp Delta: Server Fill Time minus Local Dispatch Time (measured in milliseconds). This isolates your network latency from the venue's internal routing and matching delays.

Price Delta (Slippage): Requested Price vs. Executed Price. Tracking both positive and negative slippage distributions is critical. Toxic infrastructure often artificially caps positive slippage (asymmetric slippage) while passing on 100% of the negative slippage during volatile moves.

[FTtrader]

2. Session-Segmented p95 Analysis

Median slippage provides the baseline cost of doing business, but p95 slippage is where tight scalping books go to die.

Segment the logged tick data by session (e.g., Frankfurt/London overlap vs. late NY/Asian session).

A venue might show a 0.1 pip median slippage during peak liquidity, but a 1.5 pip p95 slippage during minor macroeconomic releases or tier-2 data points. If your stop-loss logic relies on hard execution, that p95 tail risk will eventually hollow out the equity curve.

3. Spread Profiling & Liquidity Sweeps

Verifying whether "raw" pricing actually stays raw requires continuous, tick-level spread monitoring—especially around the daily rollover.

Rollover Audits: Run a background script that records the bid/ask spread every tick during the rollover window (23:55 to 00:05 server time).

Reject Rates at Structure: Cross-reference order reject rates specifically during liquidity sweeps. If market orders are consistently rejected, re-quoted, or slipped heavily exactly when order book liquidity thins out to sweep a structural low or high, the venue's liquidity pool is simply too shallow to absorb aggressive price action trading.

Tracking this via custom algorithmic routines rather than relying on native platform reports provides the exact empirical data needed to evaluate a venue's actual plumbing.

What does your current data capture stack look like for pulling those quarterly p95 and reject rate metrics?

[FTtrader]

To translate this into Pine Script, we have to navigate a core architectural boundary: Pine executes on TradingView’s servers, meaning it cannot ping your local machine for millisecond network latency, nor can it write directly to an external SQL database.

To get true millisecond network deltas and external SQL routing, you have to run that specific logging layer directly at the client API level (like C# cAlgo or MQL5).

However, we can build a Pine Script Execution Profiler that tracks the delta between your requested entry price and the actual server fill price, logs the slippage to the TradingView console, and maps out toxic liquidity zones (like the daily rollover) directly on your chart.

[FTtrader]

Here is a v5 Strategy script designed to audit execution quality and visualize the cost drag.

Code: Select all

//@version=5
strategy("Execution & Slippage Profiler", overlay=true, calc_on_every_tick=true, margin_long=100, margin_short=100)

// =========================================================================
// INPUTS & PARAMETERS
// =========================================================================
acceptable_slip = input.float(0.5, title="Acceptable Slippage (Pips)", step=0.1, group="Metrics")
rollover_session = input.session("2355-0010", title="Rollover Window (Toxic Liquidity)", group="Time & Liquidity")
timezone = input.string("UTC", title="Timezone", group="Time & Liquidity")

// Forex pip multiplier (Adjusts for 5-digit vs standard pricing)
pip_mult = syminfo.mintick * 10

// =========================================================================
// LIQUIDITY ZONE MAPPING
// =========================================================================
// Identify and highlight the rollover window where spreads naturally widen
in_rollover = time(timeframe.period, rollover_session, timezone) != 0
bgcolor(in_rollover ? color.new(color.red, 92) : na, title="Rollover Zone")

// =========================================================================
// EXECUTION LOGGING LOGIC
// =========================================================================
var float requested_price = na
var float total_slippage = 0.0
var int trade_count = 0

// Sample trigger: A simple momentum crossover to generate test executions
// Replace this with your actual entry logic to profile your specific setups
long_cond = ta.crossover(ta.sma(close, 9), ta.sma(close, 21)) and not in_rollover

if (long_cond)
    requested_price := close // Capture the exact price when the condition fired
    strategy.entry("Long_Test", strategy.long)

// Calculate slippage on the bar immediately following the entry
if (strategy.opentrades > 0 and strategy.opentrades > strategy.opentrades[1])
    // Get the actual fill price from the TV broker emulator or live integration
    actual_entry = strategy.opentrades.entry_price(strategy.opentrades - 1)
    
    // Calculate slippage (Actual Fill - Requested Price) translated to pips
    slip_pips = (actual_entry - requested_price) / pip_mult
    
    // Accumulate metrics
    total_slippage += slip_pips
    trade_count += 1
    
    // Log directly to the Pine Console for export/review
    log.info("Requested: {0,number,#.#####} | Filled: {1,number,#.#####} | Slippage: {2,number,#.#} pips", requested_price, actual_entry, slip_pips)

// =========================================================================
// REAL-TIME DASHBOARD
// =========================================================================
var table exec_table = table.new(position.bottom_right, 2, 4, border_width=1, border_color=color.gray)

if (barstate.islast)
    // Table Headers
    table.cell(exec_table, 0, 0, "Execution Profiler", text_color=color.white, bgcolor=color.rgb(21, 31, 41), text_halign=text.align_left)
    table.cell(exec_table, 1, 0, syminfo.ticker, text_color=color.white, bgcolor=color.rgb(21, 31, 41))
    
    // Trade Count
    table.cell(exec_table, 0, 1, "Sample Size (Fills)", text_color=color.gray, text_halign=text.align_left)
    table.cell(exec_table, 1, 1, str.tostring(trade_count), text_color=color.white)
    
    // Slippage Calculation
    avg_slip = trade_count > 0 ? (total_slippage / trade_count) : 0
    slip_color = avg_slip > acceptable_slip ? color.red : color.green
    
    table.cell(exec_table, 0, 2, "Avg Slippage (Pips)", text_color=color.gray, text_halign=text.align_left)
    table.cell(exec_table, 1, 2, str.tostring(math.round(avg_slip, 2)), text_color=color.white, bgcolor=slip_color)
    
    // Current Market State
    table.cell(exec_table, 0, 3, "Liquidity State", text_color=color.gray, text_halign=text.align_left)
    table.cell(exec_table, 1, 3, in_rollover ? "TOXIC (Rollover)" : "NORMAL", text_color=color.white, bgcolor=in_rollover ? color.red : color.green)

[FTtrader]

How to extract the data

Because Pine Script calculates on the close of the bar (unless calc_on_every_tick is checked during a live session), the script captures the close price exactly when your logic triggers, then compares it to the strategy.opentrades.entry_price to find the exact fill delta.

Open the Pine Logs panel (Shortcut: Ctrl + Shift + L / Cmd + Shift + L). The log.info() function will output a clean, comma-separated style string for every single fill. You can highlight, copy, and drop this directly into a spreadsheet or parse it through a local script to find your p95 tail risk without relying on standard broker statements.