Condition · recorded history

Liquidation intensity elevated

Normalized liquidation intensity is reading above 0.5: liquidations arriving well above this market baseline.

What is a liquidation?

Recorded window: 9 Sept 2026 to 8 Oct 2026 (UTC). Counted 10 Oct 2026 at 08:03 UTC.

Read it in context

On one market
Each market page compares that market with its own minutes, not with every market at once.
Compare markets
Test it, then plan it
Narrow it to your markets and dates in the Workbench. A tested result leads to Plan a trade, which measures what trading it would have paid after costs.
Edit this test in Workbench

By market

Results vary by market. Compare a market before drawing a conclusion.

Most matches:ZECUSDT BANKUSDT ETHUSDT BTCUSDT NEARUSDT XRPUSDT

All 26 markets

How results varied by market

Range across 10 markets with at least 30 measured: reached +5% within 24 hours in 6 of 49 on ETHUSDT (12%) to 28 of 31 on BLESSUSDT (90%).

Every market pooled, without context

What happened in the next 24 hours?

Both moves were more common than on minutes without it.

Other minutes are the same markets and dates without this condition. Each percentage is the share of measured minutes that reached that move from the starting price.

Price touched +5% or higher

When this held: 43.0% · 847 of 1,972 minutes
Other minutes: 33.4% · 7,263,954 of 21,736,650 minutes

Price touched −10% or lower

When this held: 22.0% · 434 of 1,972 minutes
Other minutes: 6.2% · 1,344,861 of 21,736,650 minutes

Price can touch both levels within the same 24 hours.

Every matching minute counts, so one long run adds many near-identical minutes. Busy markets weigh most.

Every condition is measured over the same 24 hours, whatever the length of its own reading. Other windows and move sizes shows shorter and longer windows.

This counts how often price touched a level, not what trading it would have paid.

Sample and counting

All 1,972 matches, pooled across 524 markets, have a full 24 hours after them.

When it happened

About 64 a day, on 28 of 31 days: spread through the record rather than one event.

Other windows and move sizes

Matches that reached each move within each window. Counts first; the measured row is what each rate is over.
Move	1 hour	4 hours	24 hours	72 hours	7 days
Measured	1,972	1,972	1,972	1,867	1,679
Too recent	0	0	0	105	293
+0.1% or more	1,801 (91.3%)	1,864 (94.5%)	1,917 (97.2%)	1,847 (98.9%)	1,675 (99.8%)
+0.2% or more	1,704 (86.4%)	1,794 (91.0%)	1,889 (95.8%)	1,833 (98.2%)	1,671 (99.5%)
+0.5% or more	1,437 (72.9%)	1,626 (82.5%)	1,800 (91.3%)	1,792 (96.0%)	1,652 (98.4%)
+1% or more	1,075 (54.5%)	1,393 (70.6%)	1,664 (84.4%)	1,721 (92.2%)	1,617 (96.3%)
+2% or more	641 (32.5%)	1,007 (51.1%)	1,401 (71.0%)	1,571 (84.1%)	1,535 (91.4%)
+5% or more	238 (12.1%)	429 (21.8%)	847 (43.0%)	1,179 (63.1%)	1,329 (79.2%)
+10% or more	100 (5.1%)	192 (9.7%)	466 (23.6%)	743 (39.8%)	999 (59.5%)
+15% or more	42 (2.1%)	106 (5.4%)	294 (14.9%)	503 (26.9%)	751 (44.7%)
+20% or more	23 (1.2%)	75 (3.8%)	203 (10.3%)	355 (19.0%)	573 (34.1%)
+30% or more	13 (0.7%)	30 (1.5%)	125 (6.3%)	212 (11.4%)	360 (21.4%)
+50% or more	5 (0.3%)	12 (0.6%)	66 (3.3%)	109 (5.8%)	156 (9.3%)
+100% or more	1 (0.1%)	3 (0.2%)	23 (1.2%)	46 (2.5%)	65 (3.9%)
+200% or more	0 (0.0%)	0 (0.0%)	6 (0.3%)	18 (1.0%)	19 (1.1%)
+400% or more	0 (0.0%)	0 (0.0%)	4 (0.2%)	9 (0.5%)	11 (0.7%)
−0.1% or lower	1,843 (93.5%)	1,905 (96.6%)	1,950 (98.9%)	1,857 (99.5%)	1,671 (99.5%)
−0.2% or lower	1,736 (88.0%)	1,856 (94.1%)	1,930 (97.9%)	1,846 (98.9%)	1,662 (99.0%)
−0.5% or lower	1,464 (74.2%)	1,691 (85.8%)	1,863 (94.5%)	1,814 (97.2%)	1,641 (97.7%)
−1% or lower	1,088 (55.2%)	1,409 (71.5%)	1,771 (89.8%)	1,765 (94.5%)	1,602 (95.4%)
−2% or lower	657 (33.3%)	989 (50.2%)	1,565 (79.4%)	1,637 (87.7%)	1,516 (90.3%)
−5% or lower	247 (12.5%)	435 (22.1%)	929 (47.1%)	1,209 (64.8%)	1,214 (72.3%)
−10% or lower	80 (4.1%)	166 (8.4%)	434 (22.0%)	685 (36.7%)	786 (46.8%)
−15% or lower	32 (1.6%)	75 (3.8%)	237 (12.0%)	387 (20.7%)	452 (26.9%)
−20% or lower	17 (0.9%)	43 (2.2%)	136 (6.9%)	226 (12.1%)	279 (16.6%)
−30% or lower	7 (0.4%)	19 (1.0%)	58 (2.9%)	115 (6.2%)	150 (8.9%)
−50% or lower	0 (0.0%)	1 (0.1%)	18 (0.9%)	38 (2.0%)	48 (2.9%)

Each window counts only matches old enough for it, so a longer window can show fewer.

Distributions and daily counts

Upside reached · 24hThe most price moved up within 24 hours of each match: a high-water mark, never a close. 1,972 with a complete 24 hours.

Drawdown · 24hThe worst price moved against within 24 hours of each match: the deepest point, never the close. 1,972 with a complete 24 hours.

Price 30 minutes laterForward 30-minute returns across 1,969 matches: close to an even split, which is what a coin flip looks like. 3 too recent.

How to read a distribution

Matches per UTC day

9 Sep196 matches
10 Sep31 matches
11 Sep32 matches
12 Sep30 matches
13 Sep231 matches
14 Sep42 matches
15 Sep81 matches
16 Sep42 matches
17 Sep47 matches
18 Sep79 matches
19 Sep93 matches
20 Sep63 matches
21 Sep75 matches
22 Sep56 matches
23 Sep100 matches
24 Sep0 matches
25 Sep0 matches
26 Sep27 matches
27 Sep66 matches
28 Sep93 matches
29 Sep69 matches
30 Sep50 matches
1 Oct60 matches
2 Oct109 matches
3 Oct29 matches
4 Oct31 matches
5 Oct62 matches
6 Oct43 matches
7 Oct45 matches
8 Oct90 matches
9 Oct0 matches

How this is counted

Each rate counts only matches with the full window after them.
A minute where a reading was missing is left out and reported, not read as zero.
The condition picks the setup, never the outcome: a definition that filters on what followed is rejected (OUTCOME_IN_PREDICATE). Every match is measured, winners and losers alike.
"Other minutes" is every other eligible minute in the same markets and window. It is a reference, not a control group.
"Reached +5%" uses the highest price inside the window (maximum favourable excursion, MFE); "fell to −10%" uses the lowest (maximum adverse excursion, MAE). Neither is the close.
Checked 22,417,255 eligible market-minutes (eligible_symbol_buckets) on 524 markets, 2026-09-09 00:00 to 2026-10-09 00:00 UTC.
These counts pool every market, so markets that match often weigh more. Each market page compares that market with its own reference.
Live status is not connected yet, so this page is recorded history only.

What are MFE and MAE?

Reproducibility key (q#6b38cf96)

The key that re-runs this exact count. Same key, same bytes; when the record grows, the dataset revision changes.

grammar: research_query.v2
normalization: archive_normalization.v1
feature library: feature_defs.v1
dataset revision: 8696b70f6a30f00fc47fa0749365772f864d601724559c5816f208110ddfcf7d
query hash: 6b38cf96600ccfbfe458aa3043f8110bfbb03ac82a0de7e2119a6c3e7e4d5d75
scanned window: 2026-09-09T00:00:00.000Z to 2026-10-09T00:00:00.000Z (UTC)

Re-run over the API

The exact search definition behind this count. Send it to the key-authed research API (or the MCP research tool) and compare the bytes; a cached rerun is free.

{
  "schema_version": "research_query.v2",
  "normalization_version": "archive_normalization.v1",
  "feature_version": "feature_defs.v1",
  "target": "record_occurrences",
  "where": {
    "all": [
      [
        "feature.liq_intensity_norm",
        "gte",
        0.5
      ],
      [
        "times.anchor_time",
        "between",
        [
          "2026-09-09T00:00:00.000Z",
          "2026-10-09T00:00:00.000Z"
        ]
      ]
    ]
  },
  "sort": [
    "times.anchor_time",
    "desc"
  ],
  "page": {
    "limit": 50,
    "cursor": null
  }
}

curl -s https://app.edgedepth.com/api/v1/research/query \
  -H 'authorization: Bearer $EDGEDEPTH_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"schema_version":"research_query.v2","normalization_version":"archive_normalization.v1","feature_version":"feature_defs.v1","target":"record_occurrences","where":{"all":[["feature.liq_intensity_norm","gte",0.5],["times.anchor_time","between",["2026-09-09T00:00:00.000Z","2026-10-09T00:00:00.000Z"]]]},"sort":["times.anchor_time","desc"],"page":{"limit":50,"cursor":null}}'