BLUAIUSDT · recorded history

One-sided tape: buyers on BLUAIUSDT

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 BLUAIUSDT itself

  2. Its recorded moves

  3. Test it on BLUAIUSDT, then plan it

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

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
40.2% · 135 of 336 minutes
Other minutes
50.8% · 17,350 of 34,153 minutes

Price touched −10% or lower

When this held
8.9% · 30 of 336 minutes
Other minutes
20.2% · 6,902 of 34,153 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 336 of 347 matches with a full 24 hours after them. The 11 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-07-18 to 2026-08-17

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

Over the full record

Every recorded day on BLUAIUSDT, 2026-05-15 to 2026-08-14: reached +5% in 389 of 853 (45.6%); fell to −10% in 108 of 853 (12.7%), within 24 hours.

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 hours
Measured346345336
Too recent1211
+0.1% or more311 (89.9%)332 (96.2%)335 (99.7%)
+0.2% or more273 (78.9%)317 (91.9%)333 (99.1%)
+0.5% or more199 (57.5%)275 (79.7%)322 (95.8%)
+1% or more120 (34.7%)227 (65.8%)306 (91.1%)
+2% or more40 (11.6%)135 (39.1%)270 (80.4%)
+5% or more9 (2.6%)28 (8.1%)135 (40.2%)
+10% or more3 (0.9%)12 (3.5%)68 (20.2%)
+15% or more3 (0.9%)9 (2.6%)40 (11.9%)
+20% or more1 (0.3%)4 (1.2%)21 (6.3%)
+30% or more1 (0.3%)4 (1.2%)18 (5.4%)
+50% or more1 (0.3%)3 (0.9%)17 (5.1%)
+100% or more0 (0.0%)0 (0.0%)2 (0.6%)
−0.1% or lower319 (92.2%)334 (96.8%)332 (98.8%)
−0.2% or lower293 (84.7%)322 (93.3%)331 (98.5%)
−0.5% or lower209 (60.4%)277 (80.3%)314 (93.5%)
−1% or lower115 (33.2%)207 (60.0%)281 (83.6%)
−2% or lower41 (11.8%)117 (33.9%)230 (68.5%)
−5% or lower7 (2.0%)25 (7.2%)111 (33.0%)
−10% or lower1 (0.3%)1 (0.3%)30 (8.9%)
−15% or lower1 (0.3%)1 (0.3%)3 (0.9%)
−20% or lower0 (0.0%)0 (0.0%)3 (0.9%)
−30% or lower0 (0.0%)0 (0.0%)2 (0.6%)
−50% or lower0 (0.0%)0 (0.0%)2 (0.6%)

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

Full record: 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 hours
Measured857856853
Too recent6710
+1% or more313 (36.5%)579 (67.6%)797 (93.4%)
+2% or more125 (14.6%)364 (42.5%)699 (81.9%)
+5% or more27 (3.2%)102 (11.9%)389 (45.6%)
+10% or more6 (0.7%)34 (4.0%)205 (24.0%)
+15% or more3 (0.4%)15 (1.8%)95 (11.1%)
+20% or more2 (0.2%)6 (0.7%)65 (7.6%)
−1% or lower299 (34.9%)533 (62.3%)735 (86.2%)
−2% or lower96 (11.2%)299 (34.9%)618 (72.5%)
−5% or lower15 (1.8%)69 (8.1%)310 (36.3%)
−10% or lower5 (0.6%)14 (1.6%)108 (12.7%)
−15% or lower4 (0.5%)10 (1.2%)58 (6.8%)
−20% or lower0 (0.0%)7 (0.8%)45 (5.3%)

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. 336 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. 336 with a complete 24 hours.
Price 30 minutes laterForward 30-minute returnForward 30-minute returns across 345 matches: close to an even split, which is what a coin flip looks like. 2 too recent.

How to read a distribution

Matches per UTC day

  • 18 Jul12 matches
  • 19 Jul12 matches
  • 20 Jul16 matches
  • 21 Jul13 matches
  • 22 Jul14 matches
  • 23 Jul14 matches
  • 24 Jul15 matches
  • 25 Jul19 matches
  • 26 Jul17 matches
  • 27 Jul17 matches
  • 28 Jul17 matches
  • 29 Jul12 matches
  • 30 Jul18 matches
  • 31 Jul17 matches
  • 1 Aug13 matches
  • 2 Aug15 matches
  • 3 Aug14 matches
  • 4 Aug11 matches
  • 5 Aug11 matches
  • 6 Aug14 matches
  • 7 Aug15 matches
  • 8 Aug4 matches
  • 9 Aug0 matches
  • 10 Aug3 matches
  • 11 Aug1 match
  • 12 Aug4 matches
  • 13 Aug7 matches
  • 14 Aug11 matches
  • 15 Aug11 matches
  • 16 Aug0 matches
  • 17 Aug0 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 41,761 eligible market-minutes (eligible_symbol_buckets) on BLUAIUSDT, 2026-07-18 00:00 to 2026-08-17 00:00 UTC.

What are MFE and MAE?

Reproducibility key (q#db0e17f2)

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
b49b614681261e550f26db551c43d7bbb8a19c4343c6163b1de13cdc0e2fbf5f
query hash
db0e17f2ac7f25c80650823bc9c1bf8343dea42d1a93f50b6ecb2125261b35a3
scanned window
2026-07-18T00:00:00.000Z to 2026-08-17T00: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",
        "bluaiusdt"
      ],
      [
        "times.anchor_time",
        "between",
        [
          "2026-07-18T00:00:00.000Z",
          "2026-08-17T00: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","bluaiusdt"],["times.anchor_time","between",["2026-07-18T00:00:00.000Z","2026-08-17T00: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.