BTWUSDT rose 70% into Aug 1. The record covers the whole lead-up.

Move window: 2026-07-30 10:00 to 2026-08-01 10:00 UTC. The record for BTWUSDT currently ends 2026-08-05 00:00 UTC.

Counted on 2026-08-07, against a record covering to 2026-08-05 00:00 UTC. These numbers are frozen: this page will always say what it said the day it was written.

Book imbalance · top levels ≥ 0.53 and Cascade clustering ≥ 0.6 and Return · 15m ≤ -0.016

feature.book_imbalance + feature.cascade_clustering_index + feature.ret_15m

Read at 15 minutes before the move.

Minutes like this appeared 34 times in the 43,201 minutes searched (<0.1%). What followed leaned down: 19 of the 34 matches with a complete 30 minutes forward fell (56%).

Of the 34 fires, 28 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 1.1 a day, on 6 of 31 days: spread through the record rather than one event.

q#14edd426 @ dataset 9dad0852

Best supported: Book imbalance · top levels ≥ 0.53 and Cascade clustering ≥ 0.6 and Return · 15m ≤ -0.016, 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.

What the minutes before it looked like

Where these readings were taken
the move beginsreadings taken here0.128810.070040.096640.13333Jul 29 08:00Jul 30 10:00Aug 1 14:00UTC · log price scale

Hourly candles. The marked lines are the minutes the readings came from: 1 minute, 15 minutes, 1 hour, 4 hours and 24 hours before the move began. Every one of them sits before the move, never inside it.

A reading stands out when it sits outside the range it usually holds. The rules are fixed: the same ones the moment reader on the research page uses.

At 1 minute before the move, 6 of the 39 readings stood out. 2026-07-30 09:59 UTC
READINGBEFORE THE MOVESEARCHES FOR
Book imbalance · top levels feature.book_imbalance0.7997≥ 0.79
Book imbalance percentile feature.book_imbalance_pctrank0.9317≥ 0.93
Cascade clustering feature.cascade_clustering_index0.6056≥ 0.6
Return · 15m feature.ret_15m-0.0207≤ -0.02
Return · 1h feature.ret_1h-0.03197≤ -0.031
VWAP distance · day feature.vwap_dist-0.06741≤ -0.067
At 15 minutes before the move, 6 of the 39 readings stood out. 2026-07-30 09:45 UTC
READINGBEFORE THE MOVESEARCHES FOR
Book imbalance · top levels feature.book_imbalance0.532≥ 0.53
Cascade clustering feature.cascade_clustering_index0.6058≥ 0.6
Return · 15m feature.ret_15m-0.01607≤ -0.016
Return · 1h feature.ret_1h-0.02466≤ -0.024
Taker buy share · 15m feature.taker_buy_ratio_15m0.3381≤ 0.34
VWAP distance · day feature.vwap_dist-0.05284≤ -0.052
At 1 hour before the move, 3 of the 39 readings stood out. 2026-07-30 09:00 UTC
READINGBEFORE THE MOVESEARCHES FOR
Book imbalance · top levels feature.book_imbalance0.5737≥ 0.57
Cascade clustering feature.cascade_clustering_index0.6055≥ 0.6
VWAP distance · day feature.vwap_dist-0.04109≤ -0.041
At 4 hours before the move, 3 of the 39 readings stood out. 2026-07-30 06:00 UTC
READINGBEFORE THE MOVESEARCHES FOR
Book imbalance · top levels feature.book_imbalance0.797≥ 0.79
Cascade clustering feature.cascade_clustering_index0.6019≥ 0.6
Return · 1h feature.ret_1h0.0477≥ 0.047
At 24 hours before the move, 6 of the 39 readings stood out. 2026-07-29 10:00 UTC
READINGBEFORE THE MOVESEARCHES FOR
Book imbalance · top levels feature.book_imbalance0.774≥ 0.77
Cascade clustering feature.cascade_clustering_index0.5815≥ 0.58
Realized vol percentile feature.realized_vol_pctrank0.9118≥ 0.91
Return · 15m feature.ret_15m0.0373≥ 0.037
Return · 1h feature.ret_1h-0.04959≤ -0.049
VWAP distance · day feature.vwap_dist-0.1697≤ -0.16

Also counted

This is not a similarity search. Each count matches the exact readings above and nothing else.

Book imbalance · top levels ≥ 0.79 and Book imbalance percentile ≥ 0.93 and Cascade clustering ≥ 0.6

feature.book_imbalance + feature.book_imbalance_pctrank + feature.cascade_clustering_index

Read at 1 minute before the move.

Minutes like this appeared only 8 times in the 43,201 minutes searched. What followed leaned down: 5 of the 8 matches with a complete 30 minutes forward fell (63%).

Of the 8 fires, 8 came before the move began; none were during it.

About 0.3 a day over 31 days, but 2026-07-28 alone holds 63% of them: this is close to a single episode.

q#1e70b10a @ dataset 9dad0852

Book imbalance · top levels ≥ 0.57 and Cascade clustering ≥ 0.6 and VWAP distance · day ≤ -0.041

feature.book_imbalance + feature.cascade_clustering_index + feature.vwap_dist

Read at 1 hour before the move.

Minutes like this appeared only 22 times in the 43,201 minutes searched. What followed leaned down: 13 of the 22 matches with a complete 30 minutes forward fell (59%).

Of the 22 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 4 of 31 days: spread through the record rather than one event.

q#f89d82e9 @ dataset 9dad0852

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.