Move read

PROMUSDT rose into Aug 30

+97%

Move window

Move window: 2026-08-26 17:00 to 2026-08-30 02:00 UTC.

The record for PROMUSDT currently ends 2026-09-02 00:00 UTC.

The record covers the whole lead-up.

Counted on 2026-09-03, against a record covering to 2026-09-02 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 pump 4h on 2026-08-28. Open the archived event

Exact setup countedfeature.candle_compression_1h ≤ 0.47 and Containment · 15m inside and Return · 15m ≥ 0.018 · Read at 4 hours before the move.

3MATCHES of 43,201 minutes
1ROSE
2FELL
3 of 3COMPLETE 30M
What the record says

Usually lower after 30 minutes: 2 of 3 completed matches fell.

Want the next one?

Opens this exact setup in Research. Confirm it, search every prior match, then arm an alert for the next one.

Watch the ignition replayPRO

Both are true: these readings sat before this rise, and the other times they appeared, what followed more often fell. That disagreement is the finding: a lead-up that looks special is not the same as one that usually comes before rises.

Evidence and counting
feature.candle_compression_1h + feature.candle_containment_15m + feature.ret_15m

Read at 4 hours before the move.

Of the 3 fires, 3 came before the move began; none were during it.

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

q#ee05c174 @ dataset 489ec93a

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 PROMUSDT research page

What the minutes before it looked like

Where these readings were taken
the move beginsreadings taken here+97%3.55705.41778.2517Aug 25 23:00Aug 26 17:00Aug 30 06: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, 24 hours before the move.

  1. -4h2026-08-26 13:00 UTC

    At 4 hours before the move, 4 of the 41 readings stood out.

    feature.candle_compression_1h ≤ 0.47Containment · 15m insideReturn · 15m ≥ 0.018VWAP distance · day ≤ -0.033
    Show the full readings
    READINGBEFORE THE MOVESEARCHES FOR
    feature.candle_compression_1h feature.candle_compression_1h0.4646≤ 0.47
    Containment · 15m feature.candle_containment_15minsideinside
    Return · 15m feature.ret_15m0.01811≥ 0.018
    VWAP distance · day feature.vwap_dist-0.03389≤ -0.033
  2. -1h2026-08-26 16:00 UTC

    At 1 hour before the move, 5 of the 41 readings stood out.

    Sweep + reclaim · 1h bullishMinutes to funding ≤ 1Return · 15m ≤ -0.015Return · 1h ≥ 0.032VWAP distance · day ≤ -0.031
    Show the full readings
    READINGBEFORE THE MOVESEARCHES FOR
    Sweep + reclaim · 1h feature.candle_sweep_reclaim_1hbullishbullish
    Minutes to funding feature.mins_to_funding0≤ 1
    Return · 15m feature.ret_15m-0.0151≤ -0.015
    Return · 1h feature.ret_1h0.03296≥ 0.032
    VWAP distance · day feature.vwap_dist-0.03163≤ -0.031
  3. -15m2026-08-26 16:45 UTC

    At 15 minutes before the move, 6 of the 41 readings stood out.

    Book imbalance · top levels ≥ 0.97Book imbalance percentile ≤ 0.05Sweep + reclaim · 1h bullishReturn · 15m ≥ 0.021Return · 1h ≤ -0.02VWAP distance · day ≤ -0.035
    Show the full readings
    READINGBEFORE THE MOVESEARCHES FOR
    Book imbalance · top levels feature.book_imbalance0.9706≥ 0.97
    Book imbalance percentile feature.book_imbalance_pctrank0.04944≤ 0.05
    Sweep + reclaim · 1h feature.candle_sweep_reclaim_1hbullishbullish
    Return · 15m feature.ret_15m0.02114≥ 0.021
    Return · 1h feature.ret_1h-0.02004≤ -0.02
    VWAP distance · day feature.vwap_dist-0.03526≤ -0.035

Point the research surface at any past minute yourself PRO

Also counted

Book imbalance · top levels ≥ 0.97 and Book imbalance percentile ≤ 0.05 and Sweep + reclaim · 1h bullish1 match, 1 rose, 0 fell
feature.book_imbalance + feature.book_imbalance_pctrank + feature.candle_sweep_reclaim_1h

Read at 15 minutes before the move.

Minutes like this appeared only 1 time in the 43,201 minutes searched. What followed was more often higher: 1 of the 1 matches with a complete 30 minutes forward rose (100%).

Its one fire came before the move began.

About 0 a day over 31 days, but 2026-08-26 alone holds 100% of them: this is close to a single episode.

q#a6b4a959 @ dataset 489ec93a
Sweep + reclaim · 1h bullish and Minutes to funding ≤ 1 and Return · 15m ≤ -0.0152 matches, 0 rose, 2 fell
feature.candle_sweep_reclaim_1h + feature.mins_to_funding + feature.ret_15m

Read at 1 hour before the move.

Minutes like this appeared only 2 times in the 43,201 minutes searched. What followed was more often lower: 2 of the 2 matches with a complete 30 minutes forward fell (100%).

Both are true: these readings sat before this rise, and the other times they appeared, what followed more often fell. That disagreement is the finding: a lead-up that looks special is not the same as one that usually comes before rises.

Of the 2 fires, 2 came before the move began; none were during it.

About 0.1 a day over 31 days, but 2026-08-13 alone holds 50% of them: this is close to a single episode.

q#f7b735c0 @ dataset 489ec93a

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.