Tick-level trailing stops and the whipsaw problem
Posted: Sat Oct 31, 2026 6:42 am
Trailing a stop tightly behind price locks in gains but risks being stopped out by routine noise. At tick level, the noise is large relative to the trail distance.
A trail set at 1 pip on a pair that regularly oscillates by 1.5 pips in seconds will trigger constantly. The result is exits well before the move ends.
Using a volatility-based trail, perhaps a multiple of recent ATR, adapts to conditions. Or trailing only after the trade reaches a certain profit threshold avoids early triggers.
Another option is trailing by structure, moving the stop beyond the latest swing low or high. It lags but respects the price action.
Testing different trail settings against fixed targets shows whether trailing adds anything. Many systems perform just as well, or better, with a simple target.
A quick way to test it is replaying twenty or thirty past trades with three different trail settings and counting how many exits happened before the main move finished.
How is trailing handled, by fixed distance, volatility, or structure?
A trail set at 1 pip on a pair that regularly oscillates by 1.5 pips in seconds will trigger constantly. The result is exits well before the move ends.
Using a volatility-based trail, perhaps a multiple of recent ATR, adapts to conditions. Or trailing only after the trade reaches a certain profit threshold avoids early triggers.
Another option is trailing by structure, moving the stop beyond the latest swing low or high. It lags but respects the price action.
Testing different trail settings against fixed targets shows whether trailing adds anything. Many systems perform just as well, or better, with a simple target.
A quick way to test it is replaying twenty or thirty past trades with three different trail settings and counting how many exits happened before the main move finished.
How is trailing handled, by fixed distance, volatility, or structure?