TAKEUSDT rose 152% into Aug 7. The record covers the whole lead-up.
Move window: 2026-08-02 11:00 to 2026-08-07 07:00 UTC. The record for TAKEUSDT currently ends 2026-08-09 00:00 UTC.
Counted on 2026-08-10, against a record covering to 2026-08-09 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-04. Open the archived event
Book imbalance · top levels ≤ -0.56 and Cascade clustering ≥ 0.6 and Return · 15m ≥ 0.02
feature.book_imbalance + feature.cascade_clustering_index + feature.ret_15m
Read at 15 minutes before the move.
Minutes like this appeared 59 times in the 43,201 minutes searched (0.1%). What followed was close to a coin flip: 30 rose and 29 fell over the next 30 minutes (59 of the 59 matches have a complete 30 minutes forward).
Of the 59 fires, 12 came before the move began and 41 happened while it was already under way. A fire during the move sees it; it does not telegraph it.
About 1.9 a day, on 14 of 31 days: spread through the record rather than one event.
q#d5da0267 @ dataset 34c2a990
Best supported: Book imbalance · top levels ≤ -0.56 and Cascade clustering ≥ 0.6 and Return · 15m ≥ 0.02, 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: EVAA short squeeze · 8 Jul 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.87 and Cascade clustering ≥ 0.6 and Return · 1h ≥ 0.032
feature.book_imbalance + feature.cascade_clustering_index + feature.ret_1h
Read at 1 minute before the move.
Minutes like this appeared 40 times in the 43,201 minutes searched (<0.1%). What followed leaned down: 26 of the 40 matches with a complete 30 minutes forward fell (65%).
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 40 fires, 7 came before the move began and 29 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 12 of 31 days: spread through the record rather than one event.
q#b16fd5e5 @ dataset 34c2a990
Book imbalance · top levels ≥ 0.64 and Cascade clustering ≥ 0.6 and Return · 1h ≥ 0.032
feature.book_imbalance + feature.cascade_clustering_index + feature.ret_1h
Read at 1 hour before the move.
Minutes like this appeared 48 times in the 43,201 minutes searched (0.1%). What followed leaned down: 30 of the 48 matches with a complete 30 minutes forward fell (63%).
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 48 fires, 10 came before the move began and 34 happened while it was already under way. A fire during the move sees it; it does not telegraph it.
About 1.5 a day, on 12 of 31 days: spread through the record rather than one event.
q#ad0627c6 @ dataset 34c2a990
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.