BEATUSDT · recorded history

One-sided tape: buyers on BEATUSDT

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

  2. Its recorded moves

  3. Test it on BEATUSDT, 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?

Reaching +5% was about as common as without it; falling to −10% was less common than 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
77.4% · 41 of 53 minutes
Other minutes
73.3% · 29,248 of 39,918 minutes

Price touched −10% or lower

When this held
47.2% · 25 of 53 minutes
Other minutes
74.0% · 29,525 of 39,918 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 53 of 57 matches with a full 24 hours after them. The 4 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-28 to 2026-08-27

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

Over the full record

Every recorded day on BEATUSDT, 2026-05-15 to 2026-08-14: reached +5% in 172 of 258 (66.7%); fell to −10% in 60 of 258 (23.3%), 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
Measured565653
Too recent114
+0.1% or more53 (94.6%)56 (100.0%)53 (100.0%)
+0.2% or more52 (92.9%)55 (98.2%)53 (100.0%)
+0.5% or more49 (87.5%)55 (98.2%)53 (100.0%)
+1% or more41 (73.2%)51 (91.1%)52 (98.1%)
+2% or more24 (42.9%)41 (73.2%)51 (96.2%)
+5% or more7 (12.5%)26 (46.4%)41 (77.4%)
+10% or more2 (3.6%)11 (19.6%)35 (66.0%)
+15% or more0 (0.0%)6 (10.7%)25 (47.2%)
+20% or more0 (0.0%)1 (1.8%)15 (28.3%)
+30% or more0 (0.0%)0 (0.0%)10 (18.9%)
+50% or more0 (0.0%)0 (0.0%)2 (3.8%)
−0.1% or lower53 (94.6%)56 (100.0%)53 (100.0%)
−0.2% or lower52 (92.9%)55 (98.2%)53 (100.0%)
−0.5% or lower49 (87.5%)52 (92.9%)51 (96.2%)
−1% or lower32 (57.1%)43 (76.8%)46 (86.8%)
−2% or lower19 (33.9%)35 (62.5%)40 (75.5%)
−5% or lower5 (8.9%)14 (25.0%)33 (62.3%)
−10% or lower0 (0.0%)7 (12.5%)25 (47.2%)
−15% or lower0 (0.0%)2 (3.6%)20 (37.7%)
−20% or lower0 (0.0%)0 (0.0%)14 (26.4%)
−30% or lower0 (0.0%)0 (0.0%)8 (15.1%)

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
Measured259259258
Too recent001
+1% or more156 (60.2%)198 (76.4%)231 (89.5%)
+2% or more86 (33.2%)151 (58.3%)216 (83.7%)
+5% or more17 (6.6%)75 (29.0%)172 (66.7%)
+10% or more4 (1.5%)24 (9.3%)120 (46.5%)
+15% or more0 (0.0%)7 (2.7%)83 (32.2%)
+20% or more0 (0.0%)1 (0.4%)59 (22.9%)
−1% or lower136 (52.5%)188 (72.6%)229 (88.8%)
−2% or lower58 (22.4%)126 (48.6%)198 (76.7%)
−5% or lower8 (3.1%)38 (14.7%)133 (51.6%)
−10% or lower0 (0.0%)7 (2.7%)60 (23.3%)
−15% or lower0 (0.0%)1 (0.4%)30 (11.6%)
−20% or lower0 (0.0%)0 (0.0%)16 (6.2%)

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

How to read a distribution

Matches per UTC day

  • 28 Jul3 matches
  • 29 Jul1 match
  • 30 Jul9 matches
  • 31 Jul6 matches
  • 1 Aug3 matches
  • 2 Aug1 match
  • 3 Aug2 matches
  • 4 Aug3 matches
  • 5 Aug4 matches
  • 6 Aug0 matches
  • 7 Aug2 matches
  • 8 Aug4 matches
  • 9 Aug1 match
  • 10 Aug0 matches
  • 11 Aug0 matches
  • 12 Aug1 match
  • 13 Aug2 matches
  • 14 Aug1 match
  • 15 Aug0 matches
  • 16 Aug2 matches
  • 17 Aug4 matches
  • 18 Aug0 matches
  • 19 Aug0 matches
  • 20 Aug1 match
  • 21 Aug0 matches
  • 22 Aug1 match
  • 23 Aug1 match
  • 24 Aug2 matches
  • 25 Aug3 matches
  • 26 Aug0 matches
  • 27 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,731 eligible market-minutes (eligible_symbol_buckets) on BEATUSDT, 2026-07-28 00:00 to 2026-08-27 00:00 UTC.

What are MFE and MAE?

Reproducibility key (q#dedb17c6)

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
896a4727caf667cfa34cd73a7db512a14144336387da6c22d2f716650335af30
query hash
dedb17c6f1f6228aeef4363e2ff4be42528b04f79dfd82406b784855ba5c8598
scanned window
2026-07-28T00:00:00.000Z to 2026-08-27T00: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",
        "beatusdt"
      ],
      [
        "times.anchor_time",
        "between",
        [
          "2026-07-28T00:00:00.000Z",
          "2026-08-27T00: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","beatusdt"],["times.anchor_time","between",["2026-07-28T00:00:00.000Z","2026-08-27T00: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.