Detecting Hidden Liquidity
Iceberg orders and reserve size mean the book you see understates the size that's really there. Detecting hidden liquidity means watching how a price level behaves under repeated attack, not what it displays.
Prerequisites: Depth At Touch And The Shape Of The Book
An iceberg order shows a small "tip", say 100 shares, while a much larger reserve, invisible to the book, refills the tip automatically each time it's filled. A trader watching only the displayed size sees a level that never seems to run out, and that's the tell.
A worked example
The offer at 50.02 displays 100 shares. A trader sends a 100-share market buy, it fills, and the level goes to zero. One second later, the displayed size at 50.02 is back to 100. The trader buys another 100; it fills again, and again the level refills to 100 almost instantly.
A genuine, non-iceberg level of 100 shares would show zero after the first fill and stay at zero until some new trader chose to add fresh size, an event with no particular reason to happen within a second, repeatedly, at exactly 100 shares each time. An iceberg reveals itself through this pattern: constant displayed size, refilling immediately after every execution, usually in round tip-sized increments. After five such refills the trader has bought 500 shares at 50.02 without the displayed size ever suggesting more than 100 was available, the true reserve is at least 500, and probably more.
The signature of hidden size isn't a number you can read off the book, it's a pattern: a displayed level that refills to the same size, immediately, after being fully consumed, over and over.
Where it's used. Liquidity-seeking execution algorithms probe suspected iceberg levels deliberately, sending small IOC orders to "ping" a price and see whether it refills, before committing a larger slice there. Market makers watch for icebergs on the far side of the book to judge true resistance, since a level that keeps absorbing size without moving is a much stronger signal than displayed depth alone suggests. And Order Book Features For Machine Learning pipelines sometimes engineer a "refill rate" feature per price level for exactly this reason.
Not every refilling level is an iceberg, a busy, liquid name can have many independent traders adding similar-sized orders to a popular round-number price by coincidence. Detection should look for the speed of refill (much faster than a fresh, independent decision would plausibly arrive) and the consistency of size, not a single refill event.
The quickest field test: send a small probe, note the fill, and time how fast the level snaps back. Milliseconds to an identical size is iceberg behaviour; seconds to a different size is probably just organic order flow.
Discussion
💡 Discussion rules
- Ask and answer about this concept. Off-topic gets removed.
- No homework dumps. Show what you tried first.
- Corrections are welcome. Cite a source when you claim an error.
Loading discussion…
Related concepts
- The Microprice
- Pegged, Midpoint-Peg And Discretionary Orders
- Book Resilience And Replenishment
- Tightness, Depth and Resiliency: The Dimensions of Liquidity
- Agent-Based Market Simulation
- Large-Tick Versus Small-Tick Stocks
- Order Arrival And Cancellation Intensities
- Add, Cancel And Execute: The Event Alphabet
Practice in interviews
Further reading
- Bouchaud, Bonart, Donier & Gould, Trades, Quotes and Prices (ch. 2)