PONSUSDT · recorded history

Swept the lows and reclaimed (1h) on PONSUSDT

The last completed one-hour candle swept prior lows and closed back above them: the "bullish" sweep and reclaim formation on the hourly.

Read it in context

Read PONSUSDT itself
Inspect PONSUSDT now or at a past minute
Test it on PONSUSDT, then plan it
A tested result leads to Plan a trade, which measures what trading it would have paid after costs.
Edit this test in Workbench

What happened in the next 24 hours?

Other minutes are the same markets and dates without this condition. Each percentage is the share of measured minutes that reached that move from the starting price.

Price touched +5% or higher

When this held: 16 of 22, too few for a rate
Other minutes: 64.9% · 13,040 of 20,101 minutes

Price touched −10% or lower

When this held: 10 of 22, too few for a rate
Other minutes: 42.6% · 8,554 of 20,101 minutes

Price can touch both levels within the same 24 hours.

This counts how often price touched a level, not what trading it would have paid.

Sample and counting

All 22 matches have a full 24 hours after them.

Every condition is measured over the same 24 hours, whatever the length of its own reading. Other windows and move sizes shows shorter and longer windows.

When it happened

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

Other windows and move sizes

Matches that reached each move within each window. Counts first; the measured row is what each rate is over.
Move	1 hour	4 hours	24 hours	72 hours	7 days
Measured	22	22	22	21	14
Too recent	0	0	0	1	8
+0.1% or more	22	22	22	21	14
+0.2% or more	22	22	22	21	14
+0.5% or more	18	20	21	21	14
+1% or more	13	18	20	20	13
+2% or more	7	16	20	20	13
+5% or more	0	6	16	17	13
+10% or more	0	2	11	16	12
+15% or more	0	0	7	14	11
+20% or more	0	0	3	11	11
+30% or more	0	0	0	3	5
−0.1% or lower	22	22	22	21	14
−0.2% or lower	22	22	22	21	14
−0.5% or lower	20	20	22	21	14
−1% or lower	14	16	20	20	13
−2% or lower	10	15	20	20	13
−5% or lower	3	6	13	16	13
−10% or lower	0	1	10	14	12
−15% or lower	0	0	3	9	7
−20% or lower	0	0	1	5	6
−30% or lower	0	0	0	0	4

Each window counts only matches old enough for it, so a longer window can show fewer.

Distributions and daily counts

Upside reached · 24hThe most price moved up within 24 hours of each match: a high-water mark, never a close. 22 with a complete 24 hours.

Drawdown · 24hThe worst price moved against within 24 hours of each match: the deepest point, never the close. 22 with a complete 24 hours.

Price 30 minutes laterForward 30-minute returns across 22 matches: 64% of them finished down. 0 too recent.

How to read a distribution

Matches per UTC day

24 Aug0 matches
25 Aug0 matches
26 Aug0 matches
27 Aug0 matches
28 Aug0 matches
29 Aug0 matches
30 Aug0 matches
31 Aug0 matches
1 Sep0 matches
2 Sep0 matches
3 Sep0 matches
4 Sep0 matches
5 Sep0 matches
6 Sep0 matches
7 Sep1 match
8 Sep2 matches
9 Sep3 matches
10 Sep1 match
11 Sep1 match
12 Sep1 match
13 Sep3 matches
14 Sep1 match
15 Sep1 match
16 Sep2 matches
17 Sep0 matches
18 Sep1 match
19 Sep4 matches
20 Sep1 match
21 Sep0 matches
22 Sep0 matches
23 Sep0 matches

How this is counted

Each rate counts only matches with the full window after them.
A minute where a reading was missing is left out and reported, not read as zero.
The condition picks the setup, never the outcome: a definition that filters on what followed is rejected (OUTCOME_IN_PREDICATE). Every match is measured, winners and losers alike.
"Other minutes" is every other eligible minute in the same market and window. It is a reference, not a control group.
"Reached +5%" uses the highest price inside the window (maximum favourable excursion, MFE); "fell to −10%" uses the lowest (maximum adverse excursion, MAE). Neither is the close.
Checked 23,281 eligible market-minutes (eligible_symbol_buckets) on PONSUSDT, 2026-08-24 00:00 to 2026-09-23 00:00 UTC.

What are MFE and MAE?

Reproducibility key (q#c62919ce)

The key that re-runs this exact count. Same key, same bytes; when the record grows, the dataset revision changes.

grammar: research_query.v2
normalization: archive_normalization.v1
feature library: feature_defs.v1
dataset revision: cb0cece4e4dfc52ea8d4e9fc99df38ed85b172559a26618815247132abe6d569
query hash: c62919cee5b96cc918799a97e28c2d39b08b613ed451298cc668e3438e58e636
scanned window: 2026-08-24T00:00:00.000Z to 2026-09-23T00:00:00.000Z (UTC)

Re-run over the API

The exact search definition behind this count. Send it to the key-authed research API (or the MCP research tool) and compare the bytes; a cached rerun is free.

{
  "schema_version": "research_query.v2",
  "normalization_version": "archive_normalization.v1",
  "feature_version": "feature_defs.v1",
  "target": "record_occurrences",
  "where": {
    "all": [
      [
        "feature.candle_sweep_reclaim_1h",
        "eq",
        "bullish"
      ],
      [
        "identity.symbol",
        "eq",
        "ponsusdt"
      ],
      [
        "times.anchor_time",
        "between",
        [
          "2026-08-24T00:00:00.000Z",
          "2026-09-23T00:00:00.000Z"
        ]
      ]
    ]
  },
  "sort": [
    "times.anchor_time",
    "desc"
  ],
  "page": {
    "limit": 50,
    "cursor": null
  }
}

curl -s https://app.edgedepth.com/api/v1/research/query \
  -H 'authorization: Bearer $EDGEDEPTH_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"schema_version":"research_query.v2","normalization_version":"archive_normalization.v1","feature_version":"feature_defs.v1","target":"record_occurrences","where":{"all":[["feature.candle_sweep_reclaim_1h","eq","bullish"],["identity.symbol","eq","ponsusdt"],["times.anchor_time","between",["2026-08-24T00:00:00.000Z","2026-09-23T00:00:00.000Z"]]]},"sort":["times.anchor_time","desc"],"page":{"limit":50,"cursor":null}}'

Swept the lows and reclaimed (1h) on PONSUSDT

Read it in context

Read PONSUSDT itself

Test it on PONSUSDT, then plan it

What happened in the next 24 hours?

Price touched +5% or higher

Price touched −10% or lower