Move read

HEMIUSDT rose into Aug 28

+82%

Move window

Move window: 2026-08-27 05:00 to 2026-08-28 15:00 UTC.

The record for HEMIUSDT currently ends 2026-09-03 00:00 UTC.

The record covers the whole lead-up.

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

Exact setup countedBook imbalance · top levels ≥ 0.95 and Cascade clustering ≥ 0.6 and Return · 15m ≥ 0.013 · Read at 1 minute before the move.

44MATCHES of 43,201 minutes
21ROSE
23FELL
44 of 44COMPLETE 30M
What the record says

After 1 hour this setup fell 2% or more in 14 of 44 complete windows (31.8%), against 13.5% with no condition (5,825 of 43,123): 2.36x.

Best point inside 1 hour reached +5% or more in 12 of 44 complete windows; worst point fell 5% or more in 11 of 44.

Want the next one?

Opens this exact setup in Research. Confirm it, search every prior match, then arm an alert for the next one.

Watch the ignition replayPRO

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

Read at 1 minute before the move.

Of the 44 fires, 29 came before the move began and 6 happened while it was already under way. A fire during the move sees it; it does not telegraph it.

About 1.4 a day, on 16 of 31 days: spread through the record rather than one event.

q#845ac2bb @ dataset e92709f8

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 HEMIUSDT research page

What the minutes before it looked like

Where these readings were taken
the move beginsreadings taken here+82%0.0071120.010150.01449Aug 26 23:00Aug 27 05:00Aug 28 19: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 15 minutes, 1 hour, 4 hours, 24 hours before the move.

  1. -1m2026-08-27 04:59 UTC

    At 1 minute before the move, 4 of the 53 readings stood out.

    Book imbalance · top levels ≥ 0.95Cascade clustering ≥ 0.6Return · 15m ≥ 0.013Return · 1h ≥ 0.022
    Show the full readings
    READINGBEFORE THE MOVESEARCHES FOR
    Book imbalance · top levels feature.book_imbalance0.9501≥ 0.95
    Cascade clustering feature.cascade_clustering_index0.6047≥ 0.6
    Return · 15m feature.ret_15m0.01379≥ 0.013
    Return · 1h feature.ret_1h0.0226≥ 0.022

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.