Counting ticks as a volatility gauge
Volatility is usually measured with range or standard deviation. A simpler and faster signal is the number of ticks arriving per second.
When the rate climbs, something is happening. Orders are being traded, quotes are changing, and liquidity providers are repricing. When it falls, the market is quiet.
For a scalper, tick rate has two advantages. It reacts instantly, with no waiting for a bar to complete. And it picks up bursts of activity that do not yet show in the range, such as the first seconds before a move.
Several simple indicators exist for it, and custom ones are easy to build. Plotting the rate beneath the chart over a week shows clear daily patterns, with spikes at the opens and releases.
One caution: tick rate depends on the broker's feed, which may throttle updates. Two brokers can show very different counts for the same market.
A cheap experiment is plotting tick count per ten seconds against the true range for the same intervals. If the two track each other closely, the count is a decent stand-in. Where they diverge, the explanation is usually a spread change or a feed hiccup.
Has tick rate ever warned of a move before price did?
Counting ticks as a volatility gauge
Counting ticks as a volatility gauge
It’s Fairman 
-
Amanhasnoname
- Posts: 2060
- Joined: Fri Oct 30, 2026 9:45 am
Re: Counting ticks as a volatility gauge
Tick rate is underrated as a quick read on activity, mostly because it answers a different question than ATR does. Range tells you how far price travelled, while tick count tells you how hard the market is working to get there. A burst of ticks with little range often means two-sided flow absorbing orders at a level, which is exactly the kind of moment where a break or a rejection is being decided.
The tricky part is normalising it. Raw counts swing massively between Asia and the London open, so a fixed threshold will fire constantly in one session and never in another. Comparing the current rate to the average for that same time of day over the past few weeks gives a far cleaner signal, since you are measuring unusual activity rather than just normal session rhythm.
Worth checking alongside your ten-second experiment is whether spikes in tick rate tend to come before range expansion or simply arrive with it. If they only coincide, the count is a nice confirmation filter but not an early warning, and it should be used that way.
The tricky part is normalising it. Raw counts swing massively between Asia and the London open, so a fixed threshold will fire constantly in one session and never in another. Comparing the current rate to the average for that same time of day over the past few weeks gives a far cleaner signal, since you are measuring unusual activity rather than just normal session rhythm.
Worth checking alongside your ten-second experiment is whether spikes in tick rate tend to come before range expansion or simply arrive with it. If they only coincide, the count is a nice confirmation filter but not an early warning, and it should be used that way.