Sign in Get access

liquidations

Forced liquidations on Binance USDⓈ-M perpetuals (BTC, ETH, SOL): side, average price, size, notional and the full exchange event, with stream start/gap markers — live from 14 Nov 2026 · spot · premium · 2026-11-14 — 2026-11-17 (4 days)

Schema

ColumnTypeMeaning
timestamp_msBIGINT Exchange trade time of the liquidation (forceOrder `o.T`), ms UTC. On marker rows: the moment the stream (re)connected.
symbolVARCHAR Instrument, e.g. `BTC/USDT` (USDⓈ-M perpetual of the same name).
priceDOUBLE Average fill price of the liquidation order (`o.ap`; the order price `o.p` when no average is given).
qtyDOUBLE Filled quantity in the base asset (`o.z`; the original quantity `o.q` when nothing is reported as filled).
sideTINYINT 1 = forced BUY (a short position was liquidated); 0 = forced SELL (a long position was liquidated); −1 on `start`/`gap` marker rows.
eventVARCHAR `liquidation` — a forced order published by Binance; `start` — our subscription started (events before it were not observed); `gap` — the stream reconnected after an outage, no events exist for the preceding `gap_ms` (Binance does not replay them).
event_msBIGINT Exchange event time of the frame (`E`), ms UTC.
recv_msBIGINT Local receive time, ms UTC.
order_priceDOUBLE Price of the liquidation order (`o.p`).
orig_qtyDOUBLE Original order quantity (`o.q`).
last_qtyDOUBLE Quantity of the last fill (`o.l`).
statusVARCHAR Order status reported by Binance (`o.X`), e.g. FILLED.
order_typeVARCHAR Order type (`o.o`), e.g. LIMIT.
time_in_forceVARCHAR Time in force (`o.f`), e.g. IOC.
notional_usdDOUBLE price × qty — the liquidated notional in USDT.
gap_msBIGINT On `gap` rows: length of the outage before the reconnect, ms. Empty otherwise.

Conventions shared by all streams — UTC milliseconds, integer prices, what side means where, how gaps are marked and how to rebuild the book — are in the data dictionary. The same text is returned by GET /v1/schema/liquidations and the MCP tool get_schema.

Sample rows (demo hour)

The demo hour for this stream is not loaded yet — but the schema above is already the contract: columns and types will not change silently.

Work with this stream in the SQL console and the backtest runner — the data stays with us, the results go to you. Get access