edgedepthEARLY ACCESSSign in
Menu
Terminal
Recent moves
ResearchResearch hubResearch WorkbenchInvestigate a moveLiquidation mapsPublished reportsDaily movesEvent archiveSaved studiesLive alertsMarketsData coverage
LearnGuidesReading libraryWorked examplesGuided lessonsFAQ
DevelopersAPI documentationMCP setupConnect an AI agentOpen source
Pricing
< One-sided tape: buyers
SOONUSDT · recorded history

One-sided tape: buyers on SOONUSDT

Taker buy ratio over the last 15 minutes has run at 0.62 or more: a persistently buyer-heavy tape.

Read it in context

  1. Read SOONUSDT itself

    Inspect SOONUSDT now or at a past minute

  2. Its recorded moves

    SOONUSDT market events and replays

  3. Test it on SOONUSDT, then plan it

    A tested result leads to Plan a trade, which measures what trading it would have paid after costs.

    Edit this test in Workbench

What happened in the next 24 hours?

Both moves were less 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
19.4% · 72 of 372 minutes
Other minutes
28.5% · 9,421 of 33,098 minutes

Price touched −10% or lower

When this held
0.8% · 3 of 372 minutes
Other minutes
4.5% · 1,483 of 33,098 minutes

Price can touch both levels within the same 24 hours.

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

Sample and counting

Rates use the 372 of 394 matches with a full 24 hours after them. The 22 newer ones are left out, not counted as zero.

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.

When it happened
Matches per UTC day, 2026-09-01 to 2026-10-01

About 13 a day, on 30 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.
Move1 hour4 hours24 hours72 hours7 days
Measured373372372368320
Too recent2122222674
+0.1% or more314 (84.2%)340 (91.4%)359 (96.5%)367 (99.7%)320 (100.0%)
+0.2% or more267 (71.6%)325 (87.4%)356 (95.7%)366 (99.5%)320 (100.0%)
+0.5% or more154 (41.3%)255 (68.5%)335 (90.1%)355 (96.5%)315 (98.4%)
+1% or more57 (15.3%)171 (46.0%)300 (80.6%)337 (91.6%)309 (96.6%)
+2% or more17 (4.6%)77 (20.7%)259 (69.6%)318 (86.4%)305 (95.3%)
+5% or more1 (0.3%)9 (2.4%)72 (19.4%)161 (43.8%)212 (66.3%)
+10% or more0 (0.0%)1 (0.3%)22 (5.9%)80 (21.7%)112 (35.0%)
+15% or more0 (0.0%)1 (0.3%)20 (5.4%)52 (14.1%)83 (25.9%)
+20% or more0 (0.0%)1 (0.3%)17 (4.6%)50 (13.6%)57 (17.8%)
+30% or more0 (0.0%)1 (0.3%)13 (3.5%)46 (12.5%)55 (17.2%)
+50% or more0 (0.0%)0 (0.0%)7 (1.9%)45 (12.2%)54 (16.9%)
+100% or more0 (0.0%)0 (0.0%)0 (0.0%)0 (0.0%)19 (5.9%)
−0.1% or lower333 (89.3%)354 (95.2%)361 (97.0%)363 (98.6%)317 (99.1%)
−0.2% or lower284 (76.1%)329 (88.4%)354 (95.2%)358 (97.3%)315 (98.4%)
−0.5% or lower178 (47.7%)278 (74.7%)333 (89.5%)346 (94.0%)307 (95.9%)
−1% or lower58 (15.5%)171 (46.0%)261 (70.2%)296 (80.4%)285 (89.1%)
−2% or lower7 (1.9%)57 (15.3%)169 (45.4%)218 (59.2%)257 (80.3%)
−5% or lower0 (0.0%)7 (1.9%)45 (12.1%)95 (25.8%)150 (46.9%)
−10% or lower0 (0.0%)1 (0.3%)3 (0.8%)11 (3.0%)50 (15.6%)
−15% or lower0 (0.0%)1 (0.3%)1 (0.3%)0 (0.0%)0 (0.0%)

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

Distributions and daily counts
Upside reached · 24hUpside reached (MFE, 24h)The most price moved up within 24 hours of each match: a high-water mark, never a close. 372 with a complete 24 hours.
Drawdown · 24hDrawdown (MAE, 24h)The worst price moved against within 24 hours of each match: the deepest point, never the close. 372 with a complete 24 hours.
Price 30 minutes laterForward 30-minute returnForward 30-minute returns across 354 matches: close to an even split, which is what a coin flip looks like. 40 too recent.

How to read a distribution

Matches per UTC day

  • 1 Sep12 matches
  • 2 Sep14 matches
  • 3 Sep18 matches
  • 4 Sep16 matches
  • 5 Sep19 matches
  • 6 Sep15 matches
  • 7 Sep17 matches
  • 8 Sep10 matches
  • 9 Sep16 matches
  • 10 Sep12 matches
  • 11 Sep13 matches
  • 12 Sep18 matches
  • 13 Sep15 matches
  • 14 Sep13 matches
  • 15 Sep14 matches
  • 16 Sep14 matches
  • 17 Sep14 matches
  • 18 Sep17 matches
  • 19 Sep15 matches
  • 20 Sep16 matches
  • 21 Sep14 matches
  • 22 Sep14 matches
  • 23 Sep15 matches
  • 24 Sep17 matches
  • 25 Sep17 matches
  • 26 Sep13 matches
  • 27 Sep1 match
  • 28 Sep3 matches
  • 29 Sep1 match
  • 30 Sep1 match
  • 1 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 market 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 43,201 eligible market-minutes (eligible_symbol_buckets) on SOONUSDT, 2026-09-01 00:00 to 2026-10-01 00:00 UTC.

What are MFE and MAE?

Reproducibility key (q#0f0fcaed)

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
c764b05a2cce2a39e38b40d35fcb2488ecc1bfda3dfbabbbd252d4ba3f3a9680
query hash
0f0fcaedd9edae99a8b33fc9832da2dac2233bb59ed747582da9f10afd65cb0e
scanned window
2026-09-01T00:00:00.000Z to 2026-10-01T00: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.taker_buy_ratio_15m",
        "gte",
        0.62
      ],
      [
        "identity.symbol",
        "eq",
        "soonusdt"
      ],
      [
        "times.anchor_time",
        "between",
        [
          "2026-09-01T00:00:00.000Z",
          "2026-10-01T00: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.taker_buy_ratio_15m","gte",0.62],["identity.symbol","eq","soonusdt"],["times.anchor_time","between",["2026-09-01T00:00:00.000Z","2026-10-01T00:00:00.000Z"]]]},"sort":["times.anchor_time","desc"],"page":{"limit":50,"cursor":null}}'

Past examples from the record, not a guarantee or a prediction. Nothing here is trading advice.