MARSCOINUSDT · historical base rate

Swept the lows and reclaimed (1h) on MARSCOINUSDT

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

What has happened on MARSCOINUSDT when it held

Historically, when Swept the lows and reclaimed (1h) on MARSCOINUSDT held (24 occurrences in the scanned window, 24 with a computable 24h horizon), the market reached +5% within 24h in 14 of 24 (58.3) and drew down 10%+ in 16 of 24 (66.7). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

Outcome distribution

WHAT FOLLOWED · ALL 24 MATCHES

24 of 24 (100.0%) reached +0% or more within 1 hour · smallest move size with matches, picked for you

Pick a window and a move size: how often did a move at least that big follow?

WINDOWMOVE SIZE

🔒 Measured after every match, never by keeping winners. 24 of the matches have a complete 1 hour forward.

What are MFE and MAE?

Why 72 hours can show fewer than 1 hour: a match too recent for a complete 72 hours is left out of that count entirely, even if it already reached the level within 1 hour. The two counts cover different sets of matches.

When they happened - one bar per UTC day, all 24 matches
503MATCHES PER UTC DAY · MAX 5 ON 2026-09-132333112511208-2408-3109-0709-142026-08-19 TO 2026-09-18 · 31 UTC DAYS · ZERO DAYS KEEP THEIR SLOT

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

Where the next 30 minutes landed - 24 measured, 0 too recent
≥ +0: 13 OF 2441212111245≤−100−2−1−0.5−0.2−0.1<00++0.1+0.2+0.5+1+2≥+400

Forward 30-minute returns across 24 matches: close to an even split, which is what a coin flip looks like.

How to read a distribution
Upside reached · 24hUpside reached (MFE, 24h)The most price moved up within 24h of each occurrence: a high-water mark, never a close. 24 with a complete 24h.
Drawdown · 24hDrawdown (MAE, 24h)The worst price moved against within 24h of each occurrence: the deepest point, never the close. 24 with a complete 24h.

Versus baseline

Historically, when any eligible MARSCOINUSDT minute in the window (baseline) held (21,061 occurrences in the scanned window, 19,621 with a computable 24h horizon), the market reached +5% within 24h in 14,061 of 19,621 (71.7) and drew down 10%+ in 12,623 of 19,621 (64.3). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

The full record

The same setup counted over every recorded day on MARSCOINUSDT (2026-08-19 to 2026-09-18), growing daily.

Historically, when Swept the lows and reclaimed (1h) on MARSCOINUSDT over the full record held (24 occurrences in the scanned window, 24 with a computable 24h horizon), the market reached +5% within 24h in 14 of 24 (58.3) and drew down 10%+ in 16 of 24 (66.7). Maximum favorable (MFE) and maximum adverse (MAE) excursions, both computed forward.

WHAT FOLLOWED · ALL 24 MATCHES

24 of 24 (100.0%) reached +0% or more within 1 hour · smallest move size with matches, picked for you

Pick a window and a move size: how often did a move at least that big follow?

WINDOWMOVE SIZE

🔒 Measured after every match, never by keeping winners. 24 of the matches have a complete 1 hour forward.

What are MFE and MAE?

Why 72 hours can show fewer than 1 hour: a match too recent for a complete 72 hours is left out of that count entirely, even if it already reached the level within 1 hour. The two counts cover different sets of matches.

When they happened - one bar per UTC day, all 24 matches
503MATCHES PER UTC DAY · MAX 5 ON 2026-09-132333112511208-2408-3109-0709-142026-08-19 TO 2026-09-18 · 31 UTC DAYS · ZERO DAYS KEEP THEIR SLOT

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

Where the next 30 minutes landed - 24 measured, 0 too recent
≥ +0: 13 OF 2441212111245≤−100−2−1−0.5−0.2−0.1<00++0.1+0.2+0.5+1+2≥+400

Forward 30-minute returns across 24 matches: close to an even split, which is what a coin flip looks like.

How to read a distribution
Check our work: the key that re-runs this exact count (q#d33da5e1)
grammar
research_query.v2
normalization
archive_normalization.v1
feature library
feature_defs.v1
dataset revision
8904ef0442c6f623ec772df2b59d7baf1e49aaa808b5b11ac31546605549e3bb
query hash
d33da5e1d73beef64082e5947fb6fb3fb3b4c85e2b4c836a606719acabc94a5e
scanned window
2026-08-19T00:00:00.000Z to 2026-09-18T00:00:00.000Z (UTC)

Same key, same bytes. This receipt reruns; it does not retell. When the record grows, the dataset revision changes and says so.

Re-run this yourself, over the API or from an AI agent

This is the exact search definition behind the receipt. 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",
        "marscoinusdt"
      ],
      [
        "times.anchor_time",
        "between",
        [
          "2026-08-19T00:00:00.000Z",
          "2026-09-18T00: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","marscoinusdt"],["times.anchor_time","between",["2026-08-19T00:00:00.000Z","2026-09-18T00:00:00.000Z"]]]},"sort":["times.anchor_time","desc"],"page":{"limit":50,"cursor":null}}'

How to read this

  • Counts ship with denominators: occurrences across the eligible symbol-buckets scanned. A rate is over the occurrences with a computable horizon (present), never the total.
  • Absent is absent. When a feature was not warm at a minute, that bucket leaves the denominator and is reported; it is never coerced to zero.
  • This selects a setup, never its outcome. The grammar forbids filtering on what followed (OUTCOME_IN_PREDICATE), so the distribution below is over every occurrence, not a survivorship-picked subset.

Occurrences are observed examples in a selected archive, not a guarantee. Outcomes are computed forward from each anchor and are descriptive, never a filter and never a prediction. Nothing here is trading advice.

Everything measured on MARSCOINUSDT right now: the MARSCOINUSDT research page