Aggr.trade Liquidation Prints: Check Venue Coverage and Event Timing
Liquidation prints on a live tape are only as complete as the exchange feeds behind them. Check venue coverage and timing before reading a cascade.
Short answer
Aggr.trade shows liquidation prints from exchanges that publish them, with its own liquidation threshold, aggregation when trade aggregation is enabled, and default stats that include one-hour long versus short liquidations. Before drawing conclusions, check which connected venues actually supply liquidation events, whether those feeds report every liquidation or a sample, and how event timestamps compare with the trades around them. Missing venues make a cascade look smaller than it was.
Coverage: which venues report
Liquidations are exchange events. An aggregator can only show what each venue publishes, and publication rules differ. A tape connected to five venues may show liquidations from fewer.
Timing: when the event is stamped
Liquidations trigger on mark price under each exchange's margin rules (Bybit documents mark price as the trigger, with process depending on margin mode). The forced order then trades against the book. Event time, trade time and your display time can differ.
Comparing liquidation data across tools
Two tools can report different liquidation totals for the same hour because they connect to different venues, aggregate events differently, or receive different feeds from the same venue. Aggr's changelog mentions that liquidations are aggregated when trade aggregation is on, which changes how many rows you see but not the total size.
When comparing, align the venue list, market types and time window, and compare totals rather than row counts. Expect the tool with fewer venues to show less. If totals differ for the same venue, check whether either tool caps or samples events.
For research, record the source of every liquidation figure with the number. "Long liquidations 1h: X on venues A and B, from tool C" can be compared later; "big liquidations" cannot.
Reading a cascade responsibly
| Observation | Safer interpretation |
|---|---|
| Burst of long liquidations | Forced selling occurred on covered venues |
| No liquidations shown | None on covered venues, or venue not reporting |
| Price reversed after liquidations | Check book and footprint for absorption |
Aggr's changelog notes liquidations are aggregated when trade aggregation is on (3.0.6) and the default stats include a 1h liquidation counter of shorts vs longs (2.5.4).
Check liquidations against the order book and footprint at the same moment.
Open the live chart in ChartsPodTreat tape liquidations as a lower bound limited by venue coverage, and confirm their effect in the book and footprint.
Related: Order-Book Heatmap vs Liquidation Heatmap: Which Data Do You Need?.
Review Aggr.trade Liquidation Prints with bar replay before using it live.
Open ChartsPod replayQuestions readers ask
Does Aggr show all liquidations?
Only those published by the connected exchanges' feeds.
Why does the liquidation appear after the price drop?
Exchanges may publish the event after the forced trades print.
What triggers a liquidation?
Mark price crossing the position's liquidation level under the exchange's margin rules.
Sources and methodology
Aggr.trade behaviour is taken from its public README and CHANGELOG (version numbers cited) as read on 17 October 2026; the interface changes over time, so confirm settings in your build. Numbers in examples are illustrative.
- Aggr repository README — exchanges, aggregation, audio, history via aggr-server.
- Aggr changelog — workspaces, audio thresholds, liquidations, alerts.
- Bybit: Liquidation process — mark price and margin modes.
This article explains research tools and workflows. It is not financial advice, does not recommend buying or selling any asset and does not predict prices. Crypto derivatives carry a risk of rapid and total loss of margin.
CHARTSPOD EDITORIAL EDITION · RESEARCH AND EDUCATION ONLY · NOT FINANCIAL ADVICE.