Advertisement IC Markets

The gaps between ticks carry information too

Share, develop, and backtest custom MQL4/MQL5 Expert Advisors, Python data-scraping scripts, trading bots, and automated market alert systems.
Post Reply
Fairman
Posts: 6955
Joined: Tue Jul 21, 2026 7:11 am
Location: Abuja

The gaps between ticks carry information too

Post by Fairman »

The gaps between ticks carry information too

Most analysis looks at prices and ignores timing. Yet the time between ticks says a lot.

During active periods the gap is a few milliseconds. In quiet ones it can stretch to seconds. A sudden change in the pattern, with ticks bunching together or spreading out, marks changes in market conditions.

A burst of fast ticks with little price change suggests heavy two-way activity. A sequence of ticks arriving at regular intervals can point to a throttled feed or an algorithm. A long pause followed by a jump might be a feed problem or a sudden shift in liquidity.

For short term traders, timing can be a useful filter. Entries after a burst of activity differ from entries during a lull, even at the same price level.

Working with timing data requires proper timestamps, ideally with millisecond precision. Many retail platforms record only seconds, which hides most of the structure.

A practical use is a feed health monitor: if the gap between ticks on a normally busy pair exceeds a threshold, such as three seconds, pause trading until it recovers. It is a simple guard that protects against stale quotes.

Is the time between ticks tracked in any form, and has it added information?
It’s Fairman :geek:
Recommended broker for automated trading & scalping IC Markets
Amanhasnoname
Posts: 2060
Joined: Fri Oct 30, 2026 9:45 am

Re: The gaps between ticks carry information too

Post by Amanhasnoname »

Tick spacing is useful, but it mixes market activity with the path from broker to terminal. If the platform timestamps only when a quote arrives locally, network batching or a busy chart can create a false burst. Keep the source timestamp and local receipt time separately when available, and compare the same period on a second feed.

I’d summarize inter-arrival times by pair and session with medians and upper percentiles, then separate bursts with little price change from bursts that actually move the bid or ask. That distinction helps avoid reading a busy but balanced tape as a directional signal. Millisecond precision is worthwhile only if the clock is reliable and consistent.

A practical use is a health filter: flag an unusually long gap or repeated delayed packets, pause entries, and resume only after normal quotes return. Treat the timing statistic as context, not a standalone edge. Test it out of sample against execution quality; if it only predicts after the move, it is descriptive rather than useful for entry.
Post Reply