SKYAIUSDT rose 129% into Aug 9. The record covers the whole lead-up.
Move window: 2026-08-06 03:00 to 2026-08-09 07:00 UTC. The record for SKYAIUSDT 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-06. Open the archived event
Book imbalance · top levels ≤ -0.88 and Cascade clustering ≥ 0.56 and Return · 15m ≥ 0.03
feature.book_imbalance + feature.cascade_clustering_index + feature.ret_15m
Read at 1 hour before the move.
Minutes like this appeared 40 times in the 43,201 minutes searched (<0.1%). What followed was close to a coin flip: 20 rose and 20 fell over the next 30 minutes (40 of the 40 matches have a complete 30 minutes forward).
Of the 40 fires, 17 came before the move began and 9 happened while it was already under way. A fire during the move sees it; it does not telegraph it.
About 1.3 a day, on 10 of 31 days: spread through the record rather than one event.
q#2424102e @ dataset 1a5d8642
Best supported: Book imbalance · top levels ≤ -0.88 and Cascade clustering ≥ 0.56 and Return · 15m ≥ 0.03, 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.57 and Return · 1h ≤ -0.074 and VWAP distance · day ≤ -0.044
feature.cascade_clustering_index + feature.ret_1h + feature.vwap_dist
Read at 1 minute before the move.
Minutes like this appeared only 13 times in the 43,201 minutes searched. What followed was close to a coin flip: 6 rose and 7 fell over the next 30 minutes (13 of the 13 matches have a complete 30 minutes forward).
Of the 13 fires, 6 came before the move began and 2 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 7 of 31 days: spread through the record rather than one event.
q#1d0d8b3d @ dataset 1a5d8642
Book imbalance · top levels ≥ 0.96 and Book imbalance percentile ≥ 0.91 and Cascade clustering ≥ 0.57
feature.book_imbalance + feature.book_imbalance_pctrank + feature.cascade_clustering_index
Read at 15 minutes before the move.
Minutes like this appeared only 24 times in the 43,201 minutes searched. What followed was close to a coin flip: 11 rose and 13 fell over the next 30 minutes (24 of the 24 matches have a complete 30 minutes forward).
Of the 24 fires, 16 came before the move began and 3 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 11 of 31 days: spread through the record rather than one event.
q#203b741e @ 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.