CAPUSDT rose 85% into Aug 10. The record covers the whole lead-up.
Move window: 2026-08-07 04:00 to 2026-08-10 07:00 UTC. The record for CAPUSDT currently ends 2026-08-14 00:00 UTC.
Counted on 2026-08-15, against a record covering to 2026-08-14 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-09. Open the archived event
Book imbalance · top levels ≥ 0.76 and Sweep + reclaim · 15m bullish and Cascade clustering ≥ 0.56
feature.book_imbalance + feature.candle_sweep_reclaim_15m + feature.cascade_clustering_index
Read at 1 hour before the move.
Minutes like this appeared 34 times in the 43,201 minutes searched (<0.1%). What followed leaned up: 20 of the 34 matches with a complete 30 minutes forward rose (59%).
Of the 34 fires, 30 came before the move began; none were during it.
About 1.1 a day, on 11 of 31 days: spread through the record rather than one event.
q#49725a84 @ dataset de1f6756
Best supported: Book imbalance · top levels ≥ 0.76 and Sweep + reclaim · 15m bullish and Cascade clustering ≥ 0.56, the combination with the most fires before the move began.
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.
No account? Replay a real move tick by tick, free: TUT short squeeze · 9 Aug 2026.
Picked in hindsight: the counts include every other time these readings appeared, not just this move.
Also counted
This is not a similarity search. Each count matches the exact readings above and nothing else.
Book imbalance · top levels ≥ 0.94 and Containment · 15m outside and Engulfing · 15m bearish
feature.book_imbalance + feature.candle_containment_15m + feature.candle_engulfing_15m
Read at 1 minute before the move.
Minutes like this appeared only 10 times in the 43,201 minutes searched. What followed leaned up: 6 of the 10 matches with a complete 30 minutes forward rose (60%).
Of the 10 fires, 8 came before the move began and 1 happened while it was already under way. A fire during the move sees it; it does not telegraph it.
About 0.3 a day, on 9 of 31 days: spread through the record rather than one event.
q#9c097b86 @ dataset de1f6756
Book imbalance · top levels ≤ -0.55 and Containment · 15m outside and Engulfing · 15m bearish
feature.book_imbalance + feature.candle_containment_15m + feature.candle_engulfing_15m
Read at 15 minutes before the move.
Minutes like this appeared only 21 times in the 43,201 minutes searched. What followed was close to a coin flip: 11 rose and 10 fell over the next 30 minutes (21 of the 21 matches have a complete 30 minutes forward).
Of the 21 fires, 17 came before the move began and 1 happened while it was already under way. A fire during the move sees it; it does not telegraph it.
About 0.7 a day, on 17 of 31 days: spread through the record rather than one event.
q#718e501a @ dataset de1f6756
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.
Every night the record counts what fired and what usually followed: the daily brief.