How did BTC subsequently move after different Fear & Greed ranges in the available history? · By CoinNudge Research · Method reviewed 2026-09-14 · Guide updated 2026-09-14 · Source stale · Observation range: – · Calculation fear-greed-forward-return-study-2.1 · Recalculated about hourly; newest source input changes after the UTC daily close
What happened to Bitcoin after fear and greed readings?
Current answer: As of , using Alternative.me Fear & Greed Index and Binance BTCUSDT daily closes: This materialization is overdue; do not describe it as current. Alternative.me provides 3144 source sentiment days; 1838 have a same-UTC-day Binance BTC close and 1306 do not. The fixed numeric analysis buckets differ from the provider's text label on 204 rows, so both fields are published rather than silently relabeled.
Source stale
Explore data products · Check Market Events sample · Explore Telegram alerts
Current source-backed snapshot
A sentiment index is often used as a contrarian slogan, but the useful question is empirical: after a reading was published, what did Bitcoin do over fixed forward windows? This page aligns Alternative.me's daily Fear & Greed observations with Binance BTCUSDT daily closes and groups the next 1-day, 7-day and 30-day reference returns. Incomplete recent horizons remain missing, and the results are descriptive rather than an executable strategy.
Input documentation: Alternative.me Fear & Greed · Binance Spot Klines · CoinNudge methodology
Observation window: Available daily sentiment history
Calculation cadence: Recalculated about hourly; newest source input changes after the UTC daily close
Calculation version: fear-greed-forward-return-study-2.1
Download current dataset: JSON · CSV Raw values retain the dataset's published precision. Free fair-use limit: 60 requests per minute per IP, shared across all Research JSON and CSV endpoints.

| Analysis bucket | Fixed index range | Source days | BTC-aligned days | Missing BTC close | 1d complete N | Median next 1d % | 7d complete N | Median next 7d % | 30d complete N | Median next 30d % | 30d block CI low | 30d block CI high | All-day 30d baseline | Bucket minus baseline | Entry-only N | Entry-only 30d median |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Extreme Fear | 0–24 | 679 | 391 | 288 | 391 | 0.0453 | 391 | 0.2960 | 391 | 0.9731 | -2.7284 | 3.8935 | 0.6972 | 0.2759 | 56 | -3.7161 |
| Fear | 25–44 | 915 | 467 | 448 | 467 | -0.0347 | 467 | 0.0613 | 463 | -0.4570 | -7.1843 | 4.2615 | 0.6972 | -1.1543 | 109 | -1.1112 |
| Neutral | 45–55 | 494 | 339 | 155 | 339 | -0.0785 | 339 | 0.0798 | 338 | 4.9009 | -3.8700 | 11.5715 | 0.6972 | 4.2037 | 98 | 2.1379 |
| Greed | 56–74 | 726 | 504 | 222 | 503 | 0.0103 | 497 | 0.3676 | 479 | 1.5222 | -2.4530 | 6.4340 | 0.6972 | 0.8250 | 82 | -0.1356 |
| Extreme Greed | 75–100 | 330 | 137 | 193 | 137 | 0.0095 | 137 | 0.0256 | 137 | -2.6850 | -7.8437 | 3.7235 | 0.6972 | -3.3822 | 35 | -0.8560 |
Observation evidence
First 30 of 3144 observations. JSON and CSV contain all published evidence. CSV dataset_section distinguishes summary and observation rows.
| date | event_time | value | source_classification | analysis_bucket | alignment_status | btc_close | return_1d_pct | return_7d_pct | return_30d_pct | calculation_version |
|---|---|---|---|---|---|---|---|---|---|---|
| 2026-09-14 | 2026-09-14 00:00:00 UTC | 57 | Greed | Greed | missing same-UTC-day BTC close | — | — | — | — | fear-greed-forward-return-study-2.1 |
| 2026-09-13 | 2026-09-13 00:00:00 UTC | 61 | Greed | Greed | aligned | 76842.0100 | — | — | — | fear-greed-forward-return-study-2.1 |
| 2026-09-12 | 2026-09-12 00:00:00 UTC | 63 | Greed | Greed | aligned | 77278.7300 | -0.5651 | — | — | fear-greed-forward-return-study-2.1 |
| 2026-09-11 | 2026-09-11 00:00:00 UTC | 56 | Greed | Greed | aligned | 77225.7000 | 0.0687 | — | — | fear-greed-forward-return-study-2.1 |
| 2026-09-10 | 2026-09-10 00:00:00 UTC | 69 | Greed | Greed | aligned | 76568.7200 | 0.8580 | — | — | fear-greed-forward-return-study-2.1 |
| 2026-09-09 | 2026-09-09 00:00:00 UTC | 66 | Greed | Greed | aligned | 78306.4300 | -2.2191 | — | — | fear-greed-forward-return-study-2.1 |
| 2026-09-08 | 2026-09-08 00:00:00 UTC | 69 | Greed | Greed | aligned | 78455.8000 | -0.1904 | — | — | fear-greed-forward-return-study-2.1 |
| 2026-09-07 | 2026-09-07 00:00:00 UTC | 71 | Greed | Greed | aligned | 79112.0100 | -0.8295 | — | — | fear-greed-forward-return-study-2.1 |
| 2026-09-06 | 2026-09-06 00:00:00 UTC | 73 | Greed | Greed | aligned | 80341.8300 | -1.5307 | -4.3562 | — | fear-greed-forward-return-study-2.1 |
| 2026-09-05 | 2026-09-05 00:00:00 UTC | 73 | Greed | Greed | aligned | 79831.7500 | 0.6389 | -3.1980 | — | fear-greed-forward-return-study-2.1 |
| 2026-09-04 | 2026-09-04 00:00:00 UTC | 74 | Greed | Greed | aligned | 79660.7700 | 0.2146 | -3.0568 | — | fear-greed-forward-return-study-2.1 |
| 2026-09-03 | 2026-09-03 00:00:00 UTC | 65 | Greed | Greed | aligned | 81270.3700 | -1.9805 | -5.7852 | — | fear-greed-forward-return-study-2.1 |
| 2026-09-02 | 2026-09-02 00:00:00 UTC | 63 | Greed | Greed | aligned | 77340.0100 | 5.0819 | 1.2496 | — | fear-greed-forward-return-study-2.1 |
| 2026-09-01 | 2026-09-01 00:00:00 UTC | 69 | Greed | Greed | aligned | 77439 | -0.1278 | 1.3130 | — | fear-greed-forward-return-study-2.1 |
| 2026-08-31 | 2026-08-31 00:00:00 UTC | 62 | Greed | Greed | aligned | 78581.2900 | -1.4536 | 0.6754 | — | fear-greed-forward-return-study-2.1 |
| 2026-08-30 | 2026-08-30 00:00:00 UTC | 69 | Greed | Greed | aligned | 77682 | 1.1577 | 3.4240 | — | fear-greed-forward-return-study-2.1 |
| 2026-08-29 | 2026-08-29 00:00:00 UTC | 68 | Greed | Greed | aligned | 78230 | -0.7005 | 2.0475 | — | fear-greed-forward-return-study-2.1 |
| 2026-08-28 | 2026-08-28 00:00:00 UTC | 73 | Greed | Greed | aligned | 77845.8700 | 0.4934 | 2.3314 | — | fear-greed-forward-return-study-2.1 |
| 2026-08-27 | 2026-08-27 00:00:00 UTC | 71 | Greed | Greed | aligned | 80249.5800 | -2.9953 | 1.2720 | — | fear-greed-forward-return-study-2.1 |
| 2026-08-26 | 2026-08-26 00:00:00 UTC | 65 | Greed | Greed | aligned | 79023.7500 | 1.5512 | -2.1307 | — | fear-greed-forward-return-study-2.1 |
| 2026-08-25 | 2026-08-25 00:00:00 UTC | 74 | Greed | Greed | aligned | 78539.1400 | 0.6170 | -1.4008 | — | fear-greed-forward-return-study-2.1 |
| 2026-08-24 | 2026-08-24 00:00:00 UTC | 73 | Greed | Greed | aligned | 78992.7500 | -0.5742 | -0.5209 | — | fear-greed-forward-return-study-2.1 |
| 2026-08-23 | 2026-08-23 00:00:00 UTC | 66 | Greed | Greed | aligned | 77734 | 1.6193 | -0.0669 | — | fear-greed-forward-return-study-2.1 |
| 2026-08-22 | 2026-08-22 00:00:00 UTC | 71 | Greed | Greed | aligned | 77074.9300 | 0.8551 | 1.4986 | — | fear-greed-forward-return-study-2.1 |
| 2026-08-21 | 2026-08-21 00:00:00 UTC | 72 | Greed | Greed | aligned | 78338.0300 | -1.6124 | -0.6283 | — | fear-greed-forward-return-study-2.1 |
| 2026-08-20 | 2026-08-20 00:00:00 UTC | 62 | Greed | Greed | aligned | 73025.1500 | 7.2754 | 9.8931 | — | fear-greed-forward-return-study-2.1 |
| 2026-08-19 | 2026-08-19 00:00:00 UTC | 46 | Fear | Neutral | aligned | 69334.7900 | 5.3225 | 13.9742 | — | fear-greed-forward-return-study-2.1 |
| 2026-08-18 | 2026-08-18 00:00:00 UTC | 41 | Fear | Fear | aligned | 64725.4200 | 7.1214 | 21.3420 | — | fear-greed-forward-return-study-2.1 |
| 2026-08-17 | 2026-08-17 00:00:00 UTC | 31 | Fear | Fear | aligned | 64532.1000 | 0.2996 | 22.4085 | — | fear-greed-forward-return-study-2.1 |
| 2026-08-16 | 2026-08-16 00:00:00 UTC | 34 | Fear | Fear | aligned | 62900 | 2.5948 | 23.5835 | — | fear-greed-forward-return-study-2.1 |
This is an unconditional descriptive grouping, not a trading strategy. Daily rows and forward windows overlap. Primary intervals resample the full calendar timeline in 30-day circular blocks before filtering each bucket; 7/60-day block sensitivity is published in JSON/CSV. Missing days remain empty calendar positions. With fewer than 20 complete outcomes, fewer than two blocks of calendar history, or any empty replicate, the interval is null. Entry-only results remain sensitivity analysis, not non-overlapping samples.
How to read this page
- How did BTC subsequently move after different Fear & Greed ranges in the available history?
- Serially dependent unconditional groups with no regime controls, fees or execution model; sentiment association is not causation.
- Inspect the table before relying on the summary.
- JSON and CSV preserve the published evidence.
What can this page tell you quickly?
- Question answered
- How did BTC subsequently move after different Fear & Greed ranges in the available history?
- Measured scope
- Available daily Alternative.me and BTC close history
- Update schedule
- Recalculated about every 6 hours from stored source observations.
- Do not infer
- Serially dependent unconditional groups with no regime controls, fees or execution model; sentiment association is not causation.
Does extreme fear automatically mean buy?
No. Extreme fear describes the index inputs at that time. It can occur near a local bottom, during a continuing decline or in a prolonged high-volatility regime. A contrarian rule needs defined entry timing, exit timing and risk controls.
The table reports forward reference returns and mature sample sizes so users can see whether a popular claim survives even a basic historical check.
How are sentiment and Bitcoin prices aligned?
Each daily sentiment value is paired with the Binance BTCUSDT close for the same UTC date. A forward window is published only when its future close exists; recent 30-day outcomes therefore remain missing by design.
This avoids treating pending outcomes as zero. It also means results describe one spot venue reference and can differ from an execution on another exchange or at another time of day.
Why are these observations not independent trials?
Daily readings cluster: a week of fear creates seven related observations whose forward windows overlap. Treating them as seven independent experiments would understate uncertainty.
A stronger study can sample regime transitions or non-overlapping episodes. The downloadable ledger provides the raw dates needed to build that extension.
How can I verify and cite this result?
Download the page JSON for the complete snapshot and CSV for tabular evidence. Record the API dataset key `fear-greed-forward-returns`, the returned calculation_version, observation interval and named source alongside any quoted number. The visible table rounds values for readability; the downloads retain the published precision.
The stable URL remains unchanged when the data refreshes. A new calculation time does not prove every input changed, so compare source-observed timestamps and the stated available daily alternative.me and btc close history. Missing rows remain missing rather than becoming zero or a favorable estimate.
What is measured, and what is not?
| Measured claim | Evidence on this page | Boundary |
|---|---|---|
| How did BTC subsequently move after different Fear & Greed ranges in the available history? | The current table and downloadable rows using calculation contract fear-greed-forward-returns. | Serially dependent unconditional groups with no regime controls, fees or execution model; sentiment association is not causation. |
| The answer can be independently inspected. | Publish the full Alternative.me source count separately from rows aligned to a same-UTC-date Binance BTCUSDT close. Preserve the provider's text classification and also calculate fixed analysis buckets 0–24, 25–44, 45–55, 56–74 and 75–100; do not pretend they are identical. Publish mature N, medians, the all-aligned-day baseline, bucket-minus-baseline, primary 30-calendar-day block-bootstrap intervals with 7/60-day sensitivity and an entry-only sensitivity that keeps the first day after entering each bucket. Resample the full source calendar timeline including missing days before filtering into the bucket and finite 30d outcomes. Seed label is fear-greed|bucket; reset seed for each block-size run. Require 20 complete outcomes, two blocks of calendar history, and all 1,000 draws nonempty; otherwise CI is null. Entry-only sensitivity is still overlapping. Deterministic contract: RNG xorshift32 uses unsigned 32-bit x ^= (x<<13)&0xffffffff; x ^= x>>17; x ^= (x<<5)&0xffffffff. Seed is first four SHA-256 bytes of UTF-8 seed_label, unsigned big-endian; zero initializes as 1. Advance RNG once per block; start=state modulo calendar-day count; circular consecutive days, concatenate and truncate to calendar-day count. Carry state across 1,000 iterations. Median averages the middle two for even N. CI uses sorted estimates and linear interpolation at h=(N-1)*p for p=.025/.975. Numeric seeds are public in JSON/CSV. | Coverage and missingness constrain every conclusion. |
Take the next step with this evidence.
Reading about what happened to bitcoin after fear and greed readings?? Choose ongoing notifications or a dataset you can inspect in your own research workflow.
Receive qualifying events in Telegram.
Use the ready-made alert checklist, message explanations and daily briefing. Check the supported categories and coins before subscribing; every Research page is not a separate alert category.
Check the alert list · View alert plans
Inspect the data before choosing a plan.
Market Events v1 connects recorded events and comparison rows with context, later outcomes and quality flags. Paid access provides customer API keys and daily JSON, CSV and Parquet files.
Check Market Events sample · Explore the full data catalog · Compare data plans
Researcher and Research Desk currently include Market Events v1 only, for its specified pairs and published history. This page's full dataset is not automatically included. Other data families require coverage, date, field and source-use confirmation before purchase. Telegram Pro and data access are separate subscriptions.
Method and data boundary
Publish the full Alternative.me source count separately from rows aligned to a same-UTC-date Binance BTCUSDT close. Preserve the provider's text classification and also calculate fixed analysis buckets 0–24, 25–44, 45–55, 56–74 and 75–100; do not pretend they are identical. Publish mature N, medians, the all-aligned-day baseline, bucket-minus-baseline, primary 30-calendar-day block-bootstrap intervals with 7/60-day sensitivity and an entry-only sensitivity that keeps the first day after entering each bucket. Resample the full source calendar timeline including missing days before filtering into the bucket and finite 30d outcomes. Seed label is fear-greed|bucket; reset seed for each block-size run. Require 20 complete outcomes, two blocks of calendar history, and all 1,000 draws nonempty; otherwise CI is null. Entry-only sensitivity is still overlapping. Deterministic contract: RNG xorshift32 uses unsigned 32-bit x ^= (x<<13)&0xffffffff; x ^= x>>17; x ^= (x<<5)&0xffffffff. Seed is first four SHA-256 bytes of UTF-8 seed_label, unsigned big-endian; zero initializes as 1. Advance RNG once per block; start=state modulo calendar-day count; circular consecutive days, concatenate and truncate to calendar-day count. Carry state across 1,000 iterations. Median averages the middle two for even N. CI uses sorted estimates and linear interpolation at h=(N-1)*p for p=.025/.975. Numeric seeds are public in JSON/CSV.
Serially dependent unconditional groups with no regime controls, fees or execution model; sentiment association is not causation.
Sources and verification
- Alternative.me Fear & GreedDaily Bitcoin-led sentiment index.
- Binance Spot KlinesBTCUSDT daily close fields.
- CoinNudge methodologyTime and missing-outcome boundaries.
Frequently asked questions
What happens after extreme fear?
The table shows median next 1d, 7d and 30d BTC returns for the available mature observations.
Is Fear & Greed a buy signal?
No. This page describes historical association and does not provide an entry or execution rule.
Why are recent 30-day results missing?
Their future observation window has not matured.
Is this per-coin sentiment?
No. Alternative.me describes a Bitcoin-led crypto sentiment index.
Can overlapping days bias confidence?
Yes. Serial dependence and overlapping windows are explicitly disclosed.
Want this condition monitored for you?
See every Pro alert category, qualifying rule and Telegram delivery example before subscribing.
Explore the alert list