Research is a work in progress. Estimated release: 1 December 2026. Our goal is to make it a search engine for trading setups in recorded crypto markets.
Binance USDT-MIOSTUSDT rose 227% on 5 September 2026
Picked after the rise, on one market.
What happened
Price opened the 21:00 hour at 0.0006795 and reached a highest trade of 0.00222 in the 18:00 hour; the tested readings were taken at 20:00.
What stood out at 20:00
- Order book tilt0.7009Tested: 0.7 or higher
- Order book lopsidedness0.9154Tested: 0.91 or higher
- 1-hour range against usual2.411Tested: 2.4 or higher
20:00 always meets its own rules.
What the record says
Too few results to compare
Price at least 2% higher after 30 minutes
21 matches in 43,201 minutes checked.
Picked after the rise, on one market.
Evidence
No test to open
Multiple recorded sectors: sector_crypto, sector_layer_1. Choose one explicitly.
Exactly what was counted3 conditions · 21 of 43,201 minutes · saved text
- Order book tilt 0.7 or higher. Size at the best bid against the best ask; above 0 means more bids, below 0 more asks.Book imbalance · top levels ≥ 0.7 · feature.book_imbalance
- Order book lopsidedness 0.91 or higher. How lopsided the sizes at the best bid and ask were, either way, against recent readings; low means unusually even.Book imbalance percentile ≥ 0.91 · feature.book_imbalance_pctrank
- 1-hour range against usual 2.4 or higher. The last finished 1-hour candle's high to low range, as a multiple of its usual range.the last one-hour candle range versus its baseline ≥ 2.4 · feature.candle_compression_1h
Read at 1 hour before the move.
Read at 20:00 UTC on 5 September, one hour before the selected 21:00 start.
IOST only, 12 August to 10 September 2026 (UTC, ending 11 September 00:00); all 3 readings had values on 43,201 of those minutes.
Reference: every IOST minute over the same dates, matches included; it is not a matched control group.
Outcome: the close exactly 30 minutes later, not the highest or lowest price along the way.
The 21:00 start was picked automatically after the move.
IOSTUSDT stored readings end 2026-09-11 00:00 UTC (exclusive). Prices and tick replay have separate coverage.
The feature manifest spans the lead-up. Individual minutes or inputs can still be unavailable.
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.
Saved study q#e5b3dedf @ dataset d31fb5af, counted 12 Sep 2026 08:01 UTC.
Saved summary text, as written 12 Sep 2026
Written automatically when this study was saved and kept as written; where a line differs from the counts above, the counts govern.
Minutes like this appeared only 21 times in the 43,201 minutes searched. What followed was more often higher: 14 of the 21 matches with a complete 30 minutes forward rose (67%).
14 rose and 7 fell over 21 complete 30m windows. Too few completed windows for a directional generalization. No horizon cleared the floor of 30 complete windows on both the setup and the reference, so no lift is claimed.
About 0.7 a day, on 15 of 31 days: spread through the record rather than one event.
It counts the single minute on 11 September as a day.
The other reading times, as written
From 1 minute before
Minutes like this appeared only 5 times in the 43,201 minutes searched. What followed was more often higher: 5 of the 5 matches with a complete 30 minutes forward rose (100%).
5 rose and 0 fell over 5 complete 30m windows. Too few completed windows for a directional generalization. No horizon cleared the floor of 30 complete windows on both the setup and the reference, so no lift is claimed.
About 0.2 a day, on 5 of 31 days: spread through the record rather than one event.
From 15 minutes before
Minutes like this appeared only 9 times in the 43,201 minutes searched. What followed was more often higher: 6 of the 9 matches with a complete 30 minutes forward rose (67%).
6 rose and 3 fell over 9 complete 30m windows. Too few completed windows for a directional generalization. No horizon cleared the floor of 30 complete windows on both the setup and the reference, so no lift is claimed.
About 0.3 a day, on 7 of 31 days: spread through the record rather than one event.
Picked after the rise, on one market; the 21 matches came on 15 of 30 days, 4 during the rise.
When the matches happened15 of 30 days
- 12 Aug1 match
- 14 Aug1 match
- 17 Aug1 match
- 19 Aug2 matches
- 22 Aug1 match
- 26 Aug2 matches
- 28 Aug2 matches
- 1 Sep1 match
- 2 Sep1 match
- 3 Sep2 matches
- 4 Sep1 match
- 5 Sep2 matches
- 6 Sep1 match
- 8 Sep1 match
- 9 Sep2 matches
No matches on the other 15 days.
Of the 21 matches, 17 came before the rise began, 4 during it and 0 after it.
Neighbouring minutes overlap, so these are not 21 separate trials.
Picked after the rise, on one market; the 21 matches came on 15 of 30 days, 4 during the rise.
Other time frames30 minutes to 7 days
The answer uses 30 minutes, the time frame this study counted by default. Each row counts the same matches at a later close, in both directions. The bars show how often price was 2% or more higher at each time frame: first the matches, then any IOST minute.
- 30 minutes
2 of 21 were 2% or more lower; any IOST minute 1,481 of 42,380 (3.5%).
Every match has a 30-minute close.
At least 4 of these windows overlap the rise.
- 1 hour
2 of 21 were 2% or more lower; any IOST minute 2,188 of 42,362 (5.2%).
Every match has a 1-hour close.
At least 4 of these windows overlap the rise.
- 4 hours
1 of 21 was 2% or more lower; any IOST minute 4,714 of 42,164 (11.2%).
Every match has a 4-hour close.
At least 4 of these windows overlap the rise.
- 24 hours
6 of 21 were 2% or more lower; any IOST minute 8,421 of 40,988 (20.5%).
Every match has a 24-hour close.
At least 4 of these windows overlap the rise.
- 72 hours
5 of 18 were 2% or more lower; any IOST minute 6,409 of 38,153 (16.8%).
3 without a 72-hour close yet, left out.
At least 3 of these windows overlap the rise.
- 7 days
1 of 14 was 2% or more lower; any IOST minute 2,434 of 32,510 (7.5%).
7 without a 7-day close yet, left out.
At least 4 of these windows overlap the rise.
Picked after the rise, on one market; the 21 matches came on 15 of 30 days, 4 during the rise.
Readings at five times before the rise24 hours to 1 minute before · 2 other times tried
Highlights follow fixed rules, not significance tests. Proposed conditions round values or use ranges; inspect them before running.
24 hours before · 4 Sep 21:00 UTC · 11 of 63 stood out
The descending resistance line is active 4hThe distance from price back to the broken descending resistance between -0.5 and 0.5How many times the broken descending resistance had been tested 3 or higherHow long ago the descending resistance broke between 12 and 720The short descending resistance line is active 4hTouches on the broken resistance 3 or moreTime since the resistance broke between 12 and 720 hoursThe support under the short descending resistance is fallingTouches on the resistance 3 or moreThe support under the descending resistance is fallingHow many times price has touched the descending resistance 3 or higherShow the full readings
Reading Value at that minute Stored rule the descending resistance line feature.desc_resistance_active active_4h active_4h the distance from price back to the broken descending resistance feature.desc_resistance_broken_dist_atr -0.2903 -0.5 to 0.5 how many times the broken descending resistance had been tested feature.desc_resistance_broken_touches 4 ≥ 3 how long ago the descending resistance broke feature.desc_resistance_hours_since_break 83 12 to 720 the short descending resistance line feature.desc_resistance_short_active active_4h active_4h how many times the broken short descending resistance had been tested feature.desc_resistance_short_broken_touches 4 ≥ 3 how long ago the short descending resistance broke feature.desc_resistance_short_hours_since_break 83 12 to 720 the support under the short descending resistance feature.desc_resistance_short_support falling falling how many times price has touched the short descending resistance feature.desc_resistance_short_touches 5 ≥ 3 the support under the descending resistance feature.desc_resistance_support falling falling how many times price has touched the descending resistance feature.desc_resistance_touches 5 ≥ 3 4 hours before · 5 Sep 17:00 UTC · 7 of 63 stood out
1-hour range against usual 4 or higher4-hour range against usual 3.4 or higherHow many times the broken descending resistance had been tested 3 or higherTouches on the broken resistance 3 or moreVolatility rank 0.99 or higher1-hour price change 0.025 or higherDistance from the day's average price 0.036 or higherShow the full readings
Reading Value at that minute Stored rule the last one-hour candle range versus its baseline feature.candle_compression_1h 4.071 ≥ 4 the last four-hour candle range versus its baseline feature.candle_compression_4h 3.447 ≥ 3.4 how many times the broken descending resistance had been tested feature.desc_resistance_broken_touches 5 ≥ 3 how many times the broken short descending resistance had been tested feature.desc_resistance_short_broken_touches 5 ≥ 3 Realized vol percentile feature.realized_vol_pctrank 0.998 ≥ 0.99 Return · 1h feature.ret_1h 0.02506 ≥ 0.025 VWAP distance · day feature.vwap_dist 0.03635 ≥ 0.036 1 hour before · 5 Sep 20:00 UTC · 7 of 63 stood out
Order book tilt 0.7 or higherOrder book lopsidedness 0.91 or higher1-hour range against usual 2.4 or higher4-hour range against usual 3.5 or higherHow many times the broken descending resistance had been tested 3 or higherTouches on the broken resistance 3 or moreDistance from the day's average price 0.043 or higherShow the full readings
Reading Value at that minute Stored rule Book imbalance · top levels feature.book_imbalance 0.7009 ≥ 0.7 Book imbalance percentile feature.book_imbalance_pctrank 0.9154 ≥ 0.91 the last one-hour candle range versus its baseline feature.candle_compression_1h 2.411 ≥ 2.4 the last four-hour candle range versus its baseline feature.candle_compression_4h 3.553 ≥ 3.5 how many times the broken descending resistance had been tested feature.desc_resistance_broken_touches 5 ≥ 3 how many times the broken short descending resistance had been tested feature.desc_resistance_short_broken_touches 5 ≥ 3 VWAP distance · day feature.vwap_dist 0.04312 ≥ 0.043 15 minutes before · 5 Sep 20:45 UTC · 7 of 63 stood out
Order book tilt -0.58 or lowerOrder book lopsidedness 0.058 or lower1-hour range against usual 2.4 or higher4-hour range against usual 3.5 or higherHow many times the broken descending resistance had been tested 3 or higherTouches on the broken resistance 3 or moreDistance from the day's average price 0.037 or higherShow the full readings
Reading Value at that minute Stored rule Book imbalance · top levels feature.book_imbalance -0.5875 ≤ -0.58 Book imbalance percentile feature.book_imbalance_pctrank 0.05761 ≤ 0.058 the last one-hour candle range versus its baseline feature.candle_compression_1h 2.411 ≥ 2.4 the last four-hour candle range versus its baseline feature.candle_compression_4h 3.553 ≥ 3.5 how many times the broken descending resistance had been tested feature.desc_resistance_broken_touches 5 ≥ 3 how many times the broken short descending resistance had been tested feature.desc_resistance_short_broken_touches 5 ≥ 3 VWAP distance · day feature.vwap_dist 0.03791 ≥ 0.037 1 minute before · 5 Sep 20:59 UTC · 7 of 63 stood out
Order book lopsidedness 0.087 or lower1-hour range against usual 2.4 or higher4-hour range against usual 3.5 or higherHow many times the broken descending resistance had been tested 3 or higherTouches on the broken resistance 3 or more15-minute price change 0.01 or higherDistance from the day's average price 0.047 or higherShow the full readings
Reading Value at that minute Stored rule Book imbalance percentile feature.book_imbalance_pctrank 0.0866 ≤ 0.087 the last one-hour candle range versus its baseline feature.candle_compression_1h 2.411 ≥ 2.4 the last four-hour candle range versus its baseline feature.candle_compression_4h 3.553 ≥ 3.5 how many times the broken descending resistance had been tested feature.desc_resistance_broken_touches 5 ≥ 3 how many times the broken short descending resistance had been tested feature.desc_resistance_short_broken_touches 5 ≥ 3 Return · 15m feature.ret_15m 0.01072 ≥ 0.01 VWAP distance · day feature.vwap_dist 0.04797 ≥ 0.047
Two other reading times we tried 5 and 9 matches
1 minute before (20:59): order book lopsidedness 0.087 or lower, 1-hour range against usual 2.4 or higher, 4-hour range against usual 3.5 or higher.
Book imbalance percentile ≤ 0.087 and the last one-hour candle range versus its baseline ≥ 2.4 and the last four-hour candle range versus its baseline ≥ 3.5
5 matches: price was 2% or more higher after 30 minutes in 1 of 5, and 2% or more lower in 0 of 5.
Of the 5 matches, 4 came before the rise began, 1 during it and 0 after it.
15 minutes before (20:45): order book tilt -0.58 or lower, order book lopsidedness 0.058 or lower, 1-hour range against usual 2.4 or higher.
Book imbalance · top levels ≤ -0.58 and Book imbalance percentile ≤ 0.058 and the last one-hour candle range versus its baseline ≥ 2.4
9 matches: price was 2% or more higher after 30 minutes in 3 of 9, and 2% or more lower in 0 of 9.
Of the 9 matches, 6 came before the rise began, 3 during it and 0 after it.
Fewer than 30 results, so no rate is printed.
No set had 30 matches before the rise; the saved study leads with the one that had the most.
Picked after the rise, on one market; the 21 matches came on 15 of 30 days, 4 during the rise.
Hourly candles around the risefull context, lead-up, move
The 21:00 start was picked after the move, and the hour before was already rising.
Hourly candles, UTC. The marked lines are the minutes the readings came from: 1 minute, 15 minutes, 1 hour, 4 hours and 24 hours before the selected start.
Other ways to test itsame dates
Multiple recorded sectors: sector_crypto, sector_layer_1. Choose one explicitly.
Each opens Review the test; nothing runs until you press Run.
Running needs a free account and uses your allowance; you see the cost first.
Starting defaults and coverage
Starting defaults: 2026-08-12 to 2026-09-11 UTC; finishes up 2% or more after 1 hour. Review or change the markets, dates, conditions and outcome before running. Current recorded classification and sector tags, not point-in-time membership. Historical membership may differ. Instrument history does not guarantee every setup input or outcome is present; actual study exclusions remain authoritative.