TUTUSDT rose 778% into Aug 9. The record covers the whole lead-up.
Move window: 2026-08-08 03:00 to 2026-08-09 07:00 UTC. The record for TUTUSDT 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 pump 4h on 2026-08-08. Open the archived event
Book imbalance · top levels ≥ 0.73 and Book imbalance percentile ≤ 0.085 and Realized vol percentile ≥ 0.94
feature.book_imbalance + feature.book_imbalance_pctrank + feature.realized_vol_pctrank
Read at 1 hour before the move.
Minutes like this appeared only 21 times in the 43,201 minutes searched. What followed leaned up: 14 of the 21 matches with a complete 30 minutes forward rose (67%).
Of the 21 fires, 15 came before the move began and 4 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 12 of 31 days: spread through the record rather than one event.
q#35303c57 @ dataset 1a5d8642
Best supported: Book imbalance · top levels ≥ 0.73 and Book imbalance percentile ≤ 0.085 and Realized vol percentile ≥ 0.94, 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.85 and Cascade clustering ≥ 0.63 and Realized vol percentile ≥ 0.97
feature.book_imbalance + feature.cascade_clustering_index + feature.realized_vol_pctrank
Read at 1 minute before the move.
Minutes like this appeared only 12 times in the 43,201 minutes searched. What followed leaned up: 7 of the 11 matches with a complete 30 minutes forward rose (64%).
Of the 12 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.4 a day, on 8 of 31 days: spread through the record rather than one event.
q#b4c86b1a @ dataset 1a5d8642
Cascade clustering ≥ 0.63 and Realized vol percentile ≥ 0.99 and Return · 15m ≥ 0.031
feature.cascade_clustering_index + feature.realized_vol_pctrank + feature.ret_15m
Read at 15 minutes before the move.
Minutes like this appeared only 5 times in the 43,201 minutes searched. What followed leaned down: 3 of the 5 matches with a complete 30 minutes forward fell (60%).
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 5 fires, 3 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.2 a day over 31 days, but 2026-08-08 alone holds 40% of them: this is close to a single episode.
q#3e7c83a0 @ 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.