BMTUSDT rose 80% into Aug 26. The record covers the whole lead-up.

Move window: 2026-08-25 15:00 to 2026-08-26 03:00 UTC. The record for BMTUSDT currently ends 2026-09-01 00:00 UTC.

Counted on 2026-09-01, against a record covering to 2026-09-01 00:00 UTC. These numbers are frozen: this page will always say what it said the day it was written.

This move is in the event archive as a volatility spike on 2026-08-25. Open the archived event

Exact setup countedCascade clustering ≥ 0.57 and OI velocity percentile ≥ 0.98 and Realized vol percentile ≥ 0.98 · Read at 1 hour before the move.

20MATCHES
15ROSE
5FELL
20 of 20COMPLETE 30M

Minutes like this appeared only 20 times in the 43,168 minutes searched. What followed leaned up: 15 of the 20 matches with a complete 30 minutes forward rose (75%).

Opens this exact search in the research tool. Nothing runs until you confirm it there, and arming it as an alert sends a message when it next becomes true.

Evidence and counting
feature.cascade_clustering_index + feature.oi_velocity_pctrank + feature.realized_vol_pctrank

Read at 1 hour before the move.

Of the 20 fires, 10 came before the move began and 5 happened while it was already under way. A fire during the move sees it; it does not telegraph it.

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

q#dbd9e12b @ dataset 9bf4ae59

This is not a similarity search. Each count matches the exact readings above and nothing else.

Picked in hindsight: the counts include every other time these readings appeared, not just this move.

Fires often arrive as clusters of consecutive minutes, and forward windows overlap. A cluster is one episode, not many independent trials.

If these counts read weaker than the move suggested, that is the tool working: the lead-up of a picked move always looks special until it is counted everywhere else.

> Full BMTUSDT research page

What the minutes before it looked like

Where these readings were taken
the move beginsreadings taken here+80%0.014240.020280.02889Aug 24 23:00Aug 25 15:00Aug 26 07:00UTC · log price scale

Hourly candles. The marked lines are the minutes the readings came from: 1 minute, 15 minutes, 1 hour, 4 hours and 24 hours before the move began. Every one of them sits before the move, never inside it.

A reading stands out when it sits outside the range it usually holds. The rules are fixed: the same ones the moment reader on the research page uses.

No recorded readings at 1 minute, 15 minutes, 4 hours, 24 hours before the move.

  1. -1h2026-08-25 14:00 UTC

    At 1 hour before the move, 4 of the 39 readings stood out.

    Cascade clustering ≥ 0.57OI velocity percentile ≥ 0.98Realized vol percentile ≥ 0.98VWAP distance · day ≥ 0.026
    Show the full readings
    READINGBEFORE THE MOVESEARCHES FOR
    Cascade clustering feature.cascade_clustering_index0.575≥ 0.57
    OI velocity percentile feature.oi_velocity_pctrank0.98≥ 0.98
    Realized vol percentile feature.realized_vol_pctrank0.9871≥ 0.98
    VWAP distance · day feature.vwap_dist0.02693≥ 0.026

Point the research surface at any past minute yourself PRO

Also counted

Every night the record counts what fired and what usually followed: the daily brief.

No account? Replay a real move tick by tick, free: TUT short squeeze · 9 Aug 2026.