CYSUSDT rose 175% into Aug 11. The record covers the whole lead-up.
Move window: 2026-08-07 06:00 to 2026-08-11 16:00 UTC. The record for CYSUSDT currently ends 2026-08-13 00:00 UTC.
Counted on 2026-08-14, against a record covering to 2026-08-13 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-10. Open the archived event
Book imbalance · top levels ≥ 0.88 and Compression · 15m ≤ 0.42 and Containment · 15m inside
feature.book_imbalance + feature.candle_compression_15m + feature.candle_containment_15m
Read at 1 hour before the move.
Minutes like this appeared 56 times in the 43,201 minutes searched (0.1%). What followed leaned up: 32 of the 53 matches with a complete 30 minutes forward rose (60%).
Of the 56 fires, 38 came before the move began and 15 happened while it was already under way. A fire during the move sees it; it does not telegraph it.
About 1.8 a day, on 25 of 31 days: spread through the record rather than one event.
q#9b7800f9 @ dataset 1a5d8642
Best supported: Book imbalance · top levels ≥ 0.88 and Compression · 15m ≤ 0.42 and Containment · 15m inside, 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.
Cascade clustering ≥ 0.53 and VWAP distance · day ≤ -0.059
feature.cascade_clustering_index + feature.vwap_dist
Read at 1 minute before the move.
Minutes like this appeared only 25 times in the 43,201 minutes searched. What followed leaned up: 14 of the 25 matches with a complete 30 minutes forward rose (56%).
Of the 25 fires, 10 came before the move began and 12 happened while it was already under way. A fire during the move sees it; it does not telegraph it.
About 0.8 a day, on 10 of 31 days: spread through the record rather than one event.
q#378f3860 @ dataset 1a5d8642
Book imbalance · top levels ≤ -0.84 and Cascade clustering ≥ 0.53 and Return · 15m ≤ -0.013
feature.book_imbalance + feature.cascade_clustering_index + feature.ret_15m
Read at 15 minutes before the move.
Minutes like this appeared 99 times in the 43,201 minutes searched (0.2%). What followed leaned up: 61 of the 99 matches with a complete 30 minutes forward rose (62%).
Of the 99 fires, 40 came before the move began and 46 happened while it was already under way. A fire during the move sees it; it does not telegraph it.
About 3.2 a day, on 15 of 31 days: spread through the record rather than one event.
q#a96c94e8 @ dataset 1a5d8642
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.