AKEUSDT rose 51% into Aug 29. The record covers the whole lead-up.

Move window: 2026-08-26 19:00 to 2026-08-29 04:00 UTC. The record for AKEUSDT currently ends 2026-09-01 00:00 UTC.

Counted on 2026-09-01, against a record covering to 2026-09-01 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-26. Open the archived event

Exact setup countedCascade clustering ≥ 0.57 and Return · 15m ≤ -0.01 and Return · 1h ≤ -0.048 · Read at 1 hour before the move.

45MATCHES
30ROSE
15FELL
45 of 45COMPLETE 30M

Minutes like this appeared 45 times in the 43,201 minutes searched (0.1%). What followed leaned up: 30 of the 45 matches with a complete 30 minutes forward rose (67%).

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.

Evidence and counting
feature.cascade_clustering_index + feature.ret_15m + feature.ret_1h

Read at 1 hour before the move.

Of the 45 fires, 31 came before the move began and 8 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 8 of 31 days: spread through the record rather than one event.

q#47490034 @ dataset 9bf4ae59

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

Picked in hindsight: the counts include every other time these readings appeared, not just this move.

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.

> Full AKEUSDT research page

What the minutes before it looked like

Where these readings were taken
the move beginsreadings taken here+51%0.0045970.0077320.01300Aug 25 17:00Aug 26 19:00Aug 29 08: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.

No recorded readings at 1 minute, 15 minutes, 4 hours, 24 hours before the move.

  1. -1h2026-08-26 18:00 UTC

    At 1 hour before the move, 3 of the 39 readings stood out.

    Cascade clustering ≥ 0.57Return · 15m ≤ -0.01Return · 1h ≤ -0.048
    Show the full readings
    READINGBEFORE THE MOVESEARCHES FOR
    Cascade clustering feature.cascade_clustering_index0.5737≥ 0.57
    Return · 15m feature.ret_15m-0.01079≤ -0.01
    Return · 1h feature.ret_1h-0.04863≤ -0.048

Point the research surface at any past minute yourself PRO

Also counted

Every night the record counts what fired and what usually followed: the daily brief.

No account? Replay a real move tick by tick, free: TUT short squeeze · 9 Aug 2026.