Condition · recorded history

Funding pinned at the extreme of its range

Normalized funding magnitude is at 0.9 or above: funding pinned near the extreme end of its range.

What is funding?

Recorded window: 9 Sept 2026 to 8 Oct 2026 (UTC). Counted 10 Oct 2026 at 08:14 UTC.

Read it in context

  1. On one market

    Each market page compares that market with its own minutes, not with every market at once.

  2. Test it, then plan it

    Narrow it to your markets and dates in the Workbench. A tested result leads to Plan a trade, which measures what trading it would have paid after costs.

By market

No market has its own page for this condition yet. Pages are rebuilt nightly for the most-traded markets with at least 20 matches.

Every market pooled, without context

What happened in the next 24 hours?

Both moves were more common than on minutes without it.

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
55.6% · 80 of 144 minutes
Other minutes
33.8% · 7,268,725 of 21,493,148 minutes

Price touched −10% or lower

When this held
38.9% · 56 of 144 minutes
Other minutes
6.1% · 1,303,573 of 21,493,148 minutes

Price can touch both levels within the same 24 hours.

Every matching minute counts, so one long run adds many near-identical minutes. Busy markets weigh most.

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.

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

Sample and counting

All 144 matches, pooled across 524 markets, have a full 24 hours after them.

When it happened
Matches per UTC day, 2026-09-09 to 2026-10-09

About 4.6 a day, on 26 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.
Move1 hour4 hours24 hours72 hours7 days
Measured144144144143134
Too recent000110
+0.1% or more137 (95.1%)139 (96.5%)141 (97.9%)141 (98.6%)134 (100.0%)
+0.2% or more133 (92.4%)137 (95.1%)140 (97.2%)140 (97.9%)134 (100.0%)
+0.5% or more115 (79.9%)125 (86.8%)134 (93.1%)135 (94.4%)128 (95.5%)
+1% or more91 (63.2%)108 (75.0%)129 (89.6%)131 (91.6%)125 (93.3%)
+2% or more61 (42.4%)91 (63.2%)117 (81.3%)122 (85.3%)117 (87.3%)
+5% or more20 (13.9%)45 (31.3%)80 (55.6%)94 (65.7%)97 (72.4%)
+10% or more10 (6.9%)25 (17.4%)59 (41.0%)68 (47.6%)78 (58.2%)
+15% or more3 (2.1%)15 (10.4%)45 (31.3%)53 (37.1%)58 (43.3%)
+20% or more0 (0.0%)12 (8.3%)36 (25.0%)39 (27.3%)41 (30.6%)
+30% or more0 (0.0%)6 (4.2%)27 (18.8%)30 (21.0%)31 (23.1%)
+50% or more0 (0.0%)1 (0.7%)15 (10.4%)21 (14.7%)20 (14.9%)
+100% or more0 (0.0%)1 (0.7%)5 (3.5%)13 (9.1%)11 (8.2%)
+200% or more0 (0.0%)0 (0.0%)2 (1.4%)5 (3.5%)4 (3.0%)
+400% or more0 (0.0%)0 (0.0%)1 (0.7%)3 (2.1%)3 (2.2%)
−0.1% or lower144 (100.0%)144 (100.0%)144 (100.0%)143 (100.0%)134 (100.0%)
−0.2% or lower144 (100.0%)144 (100.0%)144 (100.0%)143 (100.0%)134 (100.0%)
−0.5% or lower139 (96.5%)143 (99.3%)144 (100.0%)143 (100.0%)134 (100.0%)
−1% or lower123 (85.4%)139 (96.5%)143 (99.3%)142 (99.3%)133 (99.3%)
−2% or lower91 (63.2%)120 (83.3%)134 (93.1%)135 (94.4%)129 (96.3%)
−5% or lower40 (27.8%)72 (50.0%)103 (71.5%)116 (81.1%)114 (85.1%)
−10% or lower6 (4.2%)22 (15.3%)56 (38.9%)85 (59.4%)88 (65.7%)
−15% or lower3 (2.1%)10 (6.9%)32 (22.2%)51 (35.7%)62 (46.3%)
−20% or lower1 (0.7%)3 (2.1%)17 (11.8%)26 (18.2%)40 (29.9%)
−30% or lower0 (0.0%)3 (2.1%)7 (4.9%)13 (9.1%)24 (17.9%)
−50% or lower0 (0.0%)1 (0.7%)3 (2.1%)4 (2.8%)5 (3.7%)

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

Distributions and daily counts
Upside reached · 24hUpside reached (MFE, 24h)The most price moved up within 24 hours of each match: a high-water mark, never a close. 144 with a complete 24 hours.
Drawdown · 24hDrawdown (MAE, 24h)The worst price moved against within 24 hours of each match: the deepest point, never the close. 144 with a complete 24 hours.
Price 30 minutes laterForward 30-minute returnForward 30-minute returns across 144 matches: 68% of them finished down. 0 too recent.

How to read a distribution

Matches per UTC day

  • 9 Sep3 matches
  • 10 Sep12 matches
  • 11 Sep5 matches
  • 12 Sep6 matches
  • 13 Sep9 matches
  • 14 Sep15 matches
  • 15 Sep13 matches
  • 16 Sep7 matches
  • 17 Sep7 matches
  • 18 Sep6 matches
  • 19 Sep5 matches
  • 20 Sep10 matches
  • 21 Sep3 matches
  • 22 Sep4 matches
  • 23 Sep4 matches
  • 24 Sep5 matches
  • 25 Sep5 matches
  • 26 Sep5 matches
  • 27 Sep6 matches
  • 28 Sep0 matches
  • 29 Sep0 matches
  • 30 Sep2 matches
  • 1 Oct2 matches
  • 2 Oct0 matches
  • 3 Oct1 match
  • 4 Oct1 match
  • 5 Oct5 matches
  • 6 Oct2 matches
  • 7 Oct0 matches
  • 8 Oct1 match
  • 9 Oct0 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 markets 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 22,583,758 eligible market-minutes (eligible_symbol_buckets) on 524 markets, 2026-09-09 00:00 to 2026-10-09 00:00 UTC.
  • These counts pool every market, so markets that match often weigh more. Each market page compares that market with its own reference.
  • Live status is not connected yet, so this page is recorded history only.

What are MFE and MAE?

Reproducibility key (q#b46db257)

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
6aa6f816779a152bcf5c77d802d76701e4187f3f162989b9fa25ed12f8a6dd2c
query hash
b46db257ec51ceef5445f3ad3f1a377180385eaedba8557cfc51b2857b5d3a57
scanned window
2026-09-09T00:00:00.000Z to 2026-10-09T00: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.funding_norm",
        "gte",
        0.9
      ],
      [
        "times.anchor_time",
        "between",
        [
          "2026-09-09T00:00:00.000Z",
          "2026-10-09T00: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.funding_norm","gte",0.9],["times.anchor_time","between",["2026-09-09T00:00:00.000Z","2026-10-09T00:00:00.000Z"]]]},"sort":["times.anchor_time","desc"],"page":{"limit":50,"cursor":null}}'

Past examples from the record, not a guarantee or a prediction. Nothing here is trading advice.