Understanding Liquidations and Public-Stream Data

What is a liquidation?

A liquidation is the forced closure of a leveraged position when its collateral no longer meets the platform’s margin requirements. It is not the same as a trader voluntarily deciding to sell or close. The mechanism and conditions depend on the contract and exchange.

Binance describes the role of maintenance margin and mark price in its futures liquidation protocols. This general definition does not determine what caused each event in a particular report.

How are liquidation records obtained?

A red or green candle alone does not identify a liquidation. Studying recorded events requires a source that publishes them. In the RavenInvestor analysis linked below, that source is Binance USDⓈ-M’s public BTCUSDT forceOrder stream.

The declared process captures messages with a collector, stores them, imports them without duplicates and groups them by UTC date and liquidated side. Recorded events are counted and reported notional is summed for the daily amount. These steps describe aggregation, not a reconstruction of events that were never received.

End-to-end verification would require source events, identification and deduplication rules, and collector availability logs. An aggregate report lets readers check its figures but does not replace that evidence.

Longs, shorts, events and notional

The liquidated side identifies the position being closed: long or short. In these charts, red represents liquidated longs and green liquidated shorts. The colors do not describe a recommended trade or guarantee the subsequent price direction.

The count answers how many events were captured; notional answers what reported amount they represent. They are not interchangeable. An event cannot be equated with a distinct person either: the report does not identify unique traders. Notional is not the trader’s loss or the collateral they contributed.

What can this information help with?

It can describe when observed forced closures clustered, compare the predominant side and test whether the highest-count dates also stand out by amount. It provides context for leverage risk without becoming a standalone buy or sell signal.

Comparisons require consistent definitions, sources, time zones and coverage. An unfinished day must not be treated as a complete day, and a collector interruption can reduce the count without representing a genuine fall in activity.

The limits of a public sample

The linked analysis warns that the exchange limits publication to approximately one event per second. The capture does not represent every Binance liquidation or the entire market. That report supplies no correction factor with which to fill unobserved activity.

A stream of recorded events and an estimated liquidation heatmap answer different questions: the former describes what was captured; the latter models potential zones under assumptions. They must not be presented as the same evidence.

Application with data and sources

Read the BTC/USDT daily-liquidation analysis, including its chart, daily table, data fingerprint and coverage limits.

Source for the collection methodology: methodology of RavenInvestor’s analysis of September 19, 2026, 00:21 UTC.

Educational content, not personalized financial advice. Historical data does not guarantee future results.