Which tracked altcoins lost less, or gained, on the same days that Bitcoin fell? · By CoinNudge Research · Method reviewed 2026-09-13 · Guide updated 2026-09-13 · Historical study updated · Observation range: – · Calculation historical-evidence-1.2 · Auto-refresh about every 21600 seconds
Altcoin returns on Bitcoin down days: 30-day Binance study
Current answer: As of , using CoinNudge local archive; source and scope stated in each row: 17 of 19 rows pass the full-window gate. First: LSKUSDT; median BTC-down-day excess 1.51 percentage points. Eligible rows require 31 consecutive daily closes and at least five matched BTC-down days. Ranked by median same-day excess return, not guaranteed protection.
Historical study updated
Subscribe to research data · Check a real sample · Get Telegram alerts
Current source-backed snapshot
This study conditions the comparison on Bitcoin's negative daily returns, rather than ranking coins over all market conditions. It reports each eligible altcoin's median return and median same-day excess return on those matched dates. A row requires 31 consecutive daily closes and at least five BTC-down days. Positive excess return means relative resilience, not necessarily an absolute gain. The universe is selected from currently liquid Binance Spot markets, so it cannot represent delisted or historically excluded assets.
Input documentation: Binance Spot candle field documentation · CoinNudge methodology
Observation window: Requested windows and actual coverage are recorded separately
Calculation cadence: Auto-refresh about every 21600 seconds
Calculation version: historical-evidence-1.2
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.

| Market | Coverage | BTC down days | Median down-day return % | Median excess vs BTC pp | Outperform days |
|---|---|---|---|---|---|
| LSKUSDT | eligible | 13 | 0.6790 | 1.5084 | 10 |
| TRXUSDT | eligible | 13 | 0.0295 | 1.0276 | 10 |
| BNBUSDT | eligible | 13 | -1.1320 | 0.2330 | 8 |
| STEEMUSDT | eligible | 13 | -0.6732 | 0.1823 | 7 |
| DOGEUSDT | eligible | 13 | -1.4243 | 0.0294 | 7 |
| ZECUSDT | eligible | 13 | -0.7498 | -0.0248 | 6 |
| ETHUSDT | eligible | 13 | -1.2098 | -0.0797 | 5 |
| NEARUSDT | eligible | 13 | -1.7304 | -0.3674 | 6 |
| REZUSDT | eligible | 13 | -0.6529 | -0.5251 | 6 |
| XRPUSDT | eligible | 13 | -1.8827 | -0.6226 | 3 |
| UNIUSDT | eligible | 13 | -1.5163 | -0.6868 | 5 |
| SOLUSDT | eligible | 13 | -1.9338 | -0.6872 | 4 |
| VTHOUSDT | eligible | 13 | -2.1672 | -0.7749 | 3 |
| THEUSDT | eligible | 13 | -1.2841 | -0.9893 | 6 |
| HOLOUSDT | eligible | 13 | -2.1053 | -1.2758 | 2 |
| SUIUSDT | eligible | 13 | -3.5079 | -1.5685 | 3 |
| PUMPUSDT | eligible | 13 | -3.0864 | -2.0898 | 3 |
| 牛来USDT | insufficient | 1 | — | — | — |
| MARSCOINUSDT | insufficient | 4 | — | — | — |
Actual candle coverage
Requested history is not guaranteed coverage. Missing bars remain counted.
| Market | First UTC | Last UTC | Available bars | Expected bars | Missing bars |
|---|---|---|---|---|---|
| BTCUSDT | 2026-08-13 00:00:00 UTC | 2026-09-13 00:00:00 UTC | 31 | 31 | 0 |
| ETHUSDT | 2026-08-13 00:00:00 UTC | 2026-09-13 00:00:00 UTC | 31 | 31 | 0 |
| ZECUSDT | 2026-08-13 00:00:00 UTC | 2026-09-13 00:00:00 UTC | 31 | 31 | 0 |
| LSKUSDT | 2026-08-13 00:00:00 UTC | 2026-09-13 00:00:00 UTC | 31 | 31 | 0 |
| SOLUSDT | 2026-08-13 00:00:00 UTC | 2026-09-13 00:00:00 UTC | 31 | 31 | 0 |
| THEUSDT | 2026-08-13 00:00:00 UTC | 2026-09-13 00:00:00 UTC | 31 | 31 | 0 |
| XRPUSDT | 2026-08-13 00:00:00 UTC | 2026-09-13 00:00:00 UTC | 31 | 31 | 0 |
| BNBUSDT | 2026-08-13 00:00:00 UTC | 2026-09-13 00:00:00 UTC | 31 | 31 | 0 |
| 牛来USDT | 2026-09-09 00:00:00 UTC | 2026-09-13 00:00:00 UTC | 4 | 31 | 27 |
| HOLOUSDT | 2026-08-13 00:00:00 UTC | 2026-09-13 00:00:00 UTC | 31 | 31 | 0 |
| REZUSDT | 2026-08-13 00:00:00 UTC | 2026-09-13 00:00:00 UTC | 31 | 31 | 0 |
| NEARUSDT | 2026-08-13 00:00:00 UTC | 2026-09-13 00:00:00 UTC | 31 | 31 | 0 |
| SUIUSDT | 2026-08-13 00:00:00 UTC | 2026-09-13 00:00:00 UTC | 31 | 31 | 0 |
| UNIUSDT | 2026-08-13 00:00:00 UTC | 2026-09-13 00:00:00 UTC | 31 | 31 | 0 |
| VTHOUSDT | 2026-08-13 00:00:00 UTC | 2026-09-13 00:00:00 UTC | 31 | 31 | 0 |
| PUMPUSDT | 2026-08-13 00:00:00 UTC | 2026-09-13 00:00:00 UTC | 31 | 31 | 0 |
| DOGEUSDT | 2026-08-13 00:00:00 UTC | 2026-09-13 00:00:00 UTC | 31 | 31 | 0 |
| MARSCOINUSDT | 2026-09-04 00:00:00 UTC | 2026-09-13 00:00:00 UTC | 9 | 31 | 22 |
| STEEMUSDT | 2026-08-13 00:00:00 UTC | 2026-09-13 00:00:00 UTC | 31 | 31 | 0 |
| TRXUSDT | 2026-08-13 00:00:00 UTC | 2026-09-13 00:00:00 UTC | 31 | 31 | 0 |
Observation evidence
First 30 of 221 observations. JSON and CSV contain all published evidence. CSV dataset_section distinguishes summary and observation rows.
| symbol | day | btc_return_pct | asset_return_pct | excess_vs_btc_pct | outperformed_btc | asset_first_close | asset_last_close | btc_first_close | btc_last_close | source | calculation_version |
|---|---|---|---|---|---|---|---|---|---|---|---|
| ETHUSDT | 2026-08-14 00:00:00 UTC | -0.7045 | -0.2094 | 0.4951 | true | 1886.1500 | 1882.2000 | 63490.8600 | 63043.5600 | Binance Spot | historical-evidence-1.2 |
| ETHUSDT | 2026-08-16 00:00:00 UTC | -0.2949 | -0.3527 | -0.0578 | false | 1882.6400 | 1876 | 63086.0100 | 62900 | Binance Spot | historical-evidence-1.2 |
| ETHUSDT | 2026-08-22 00:00:00 UTC | -1.6124 | -3.7237 | -2.1113 | false | 2516.3000 | 2422.6000 | 78338.0300 | 77074.9300 | Binance Spot | historical-evidence-1.2 |
| ETHUSDT | 2026-08-25 00:00:00 UTC | -0.5742 | -1.5981 | -1.0239 | false | 2482.3100 | 2442.6400 | 78992.7500 | 78539.1400 | Binance Spot | historical-evidence-1.2 |
| ETHUSDT | 2026-08-28 00:00:00 UTC | -2.9953 | -2.7137 | 0.2816 | true | 2510.9400 | 2442.8000 | 80249.5800 | 77845.8700 | Binance Spot | historical-evidence-1.2 |
| ETHUSDT | 2026-08-30 00:00:00 UTC | -0.7005 | -1.6597 | -0.9592 | false | 2457.6700 | 2416.8800 | 78230 | 77682 | Binance Spot | historical-evidence-1.2 |
| ETHUSDT | 2026-09-01 00:00:00 UTC | -1.4536 | -1.9889 | -0.5353 | false | 2467.6500 | 2418.5700 | 78581.2900 | 77439 | Binance Spot | historical-evidence-1.2 |
| ETHUSDT | 2026-09-02 00:00:00 UTC | -0.1278 | -1.1019 | -0.9741 | false | 2418.5700 | 2391.9200 | 77439 | 77340.0100 | Binance Spot | historical-evidence-1.2 |
| ETHUSDT | 2026-09-04 00:00:00 UTC | -1.9805 | -2.0602 | -0.0797 | false | 2507.5100 | 2455.8500 | 81270.3700 | 79660.7700 | Binance Spot | historical-evidence-1.2 |
| ETHUSDT | 2026-09-07 00:00:00 UTC | -1.5307 | -0.9672 | 0.5635 | true | 2514.4800 | 2490.1600 | 80341.8300 | 79112.0100 | Binance Spot | historical-evidence-1.2 |
| ETHUSDT | 2026-09-08 00:00:00 UTC | -0.8295 | -0.2048 | 0.6247 | true | 2490.1600 | 2485.0600 | 79112.0100 | 78455.8000 | Binance Spot | historical-evidence-1.2 |
| ETHUSDT | 2026-09-09 00:00:00 UTC | -0.1904 | -0.6813 | -0.4909 | false | 2485.0600 | 2468.1300 | 78455.8000 | 78306.4300 | Binance Spot | historical-evidence-1.2 |
| ETHUSDT | 2026-09-10 00:00:00 UTC | -2.2191 | -1.2098 | 1.0093 | true | 2468.1300 | 2438.2700 | 78306.4300 | 76568.7200 | Binance Spot | historical-evidence-1.2 |
| ZECUSDT | 2026-08-14 00:00:00 UTC | -0.7045 | 0.4766 | 1.1812 | true | 490.9300 | 493.2700 | 63490.8600 | 63043.5600 | Binance Spot | historical-evidence-1.2 |
| ZECUSDT | 2026-08-16 00:00:00 UTC | -0.2949 | -0.3197 | -0.0248 | false | 487.9600 | 486.4000 | 63086.0100 | 62900 | Binance Spot | historical-evidence-1.2 |
| ZECUSDT | 2026-08-22 00:00:00 UTC | -1.6124 | 9.2391 | 10.8515 | true | 734.2700 | 802.1100 | 78338.0300 | 77074.9300 | Binance Spot | historical-evidence-1.2 |
| ZECUSDT | 2026-08-25 00:00:00 UTC | -0.5742 | -7.5908 | -7.0166 | false | 830.8700 | 767.8000 | 78992.7500 | 78539.1400 | Binance Spot | historical-evidence-1.2 |
| ZECUSDT | 2026-08-28 00:00:00 UTC | -2.9953 | -1.1790 | 1.8163 | true | 810 | 800.4500 | 80249.5800 | 77845.8700 | Binance Spot | historical-evidence-1.2 |
| ZECUSDT | 2026-08-30 00:00:00 UTC | -0.7005 | -0.7498 | -0.0493 | false | 841.6000 | 835.2900 | 78230 | 77682 | Binance Spot | historical-evidence-1.2 |
| ZECUSDT | 2026-09-01 00:00:00 UTC | -1.4536 | -2.1554 | -0.7018 | false | 848.1000 | 829.8200 | 78581.2900 | 77439 | Binance Spot | historical-evidence-1.2 |
| ZECUSDT | 2026-09-02 00:00:00 UTC | -0.1278 | -1.7221 | -1.5942 | false | 829.8200 | 815.5300 | 77439 | 77340.0100 | Binance Spot | historical-evidence-1.2 |
| ZECUSDT | 2026-09-04 00:00:00 UTC | -1.9805 | 7.3739 | 9.3544 | true | 952.6900 | 1022.9400 | 81270.3700 | 79660.7700 | Binance Spot | historical-evidence-1.2 |
| ZECUSDT | 2026-09-07 00:00:00 UTC | -1.5307 | -7.1228 | -5.5921 | false | 1227.6000 | 1140.1600 | 80341.8300 | 79112.0100 | Binance Spot | historical-evidence-1.2 |
| ZECUSDT | 2026-09-08 00:00:00 UTC | -0.8295 | 3.3030 | 4.1325 | true | 1140.1600 | 1177.8200 | 79112.0100 | 78455.8000 | Binance Spot | historical-evidence-1.2 |
| ZECUSDT | 2026-09-09 00:00:00 UTC | -0.1904 | 5.6426 | 5.8330 | true | 1177.8200 | 1244.2800 | 78455.8000 | 78306.4300 | Binance Spot | historical-evidence-1.2 |
| ZECUSDT | 2026-09-10 00:00:00 UTC | -2.2191 | -13.2060 | -10.9869 | false | 1244.2800 | 1079.9600 | 78306.4300 | 76568.7200 | Binance Spot | historical-evidence-1.2 |
| LSKUSDT | 2026-08-14 00:00:00 UTC | -0.7045 | 0.5115 | 1.2160 | true | 0.0782 | 0.0786 | 63490.8600 | 63043.5600 | Binance Spot | historical-evidence-1.2 |
| LSKUSDT | 2026-08-16 00:00:00 UTC | -0.2949 | 2.3747 | 2.6695 | true | 0.0758 | 0.0776 | 63086.0100 | 62900 | Binance Spot | historical-evidence-1.2 |
| LSKUSDT | 2026-08-22 00:00:00 UTC | -1.6124 | -2.7382 | -1.1259 | false | 0.0913 | 0.0888 | 78338.0300 | 77074.9300 | Binance Spot | historical-evidence-1.2 |
| LSKUSDT | 2026-08-25 00:00:00 UTC | -0.5742 | -2.0563 | -1.4820 | false | 0.0924 | 0.0905 | 78992.7500 | 78539.1400 | Binance Spot | historical-evidence-1.2 |
Historical reconstruction is not proof of information available then or an executed return.
How to read this page
- Which tracked altcoins lost less, or gained, on the same days that Bitcoin fell?
- Current liquid Binance USDT spot selection, matched against BTC on a 30-day calendar.
- Read actual coverage and missing values before comparing outcomes.
- Download the evidence; distinguish historical reconstruction from locally recorded events.
What can this page tell you quickly?
- Best for
- Which tracked altcoins lost less, or gained, on the same days that Bitcoin fell?
- Measured scope
- Current liquid Binance USDT spot selection, matched against BTC on a 30-day calendar.
- Update schedule
- Recalculated every six hours; completed-window studies exclude the ongoing UTC day.
- Do not infer
- No guaranteed trading edge, complete point-in-time history or automatic entitlement to every data family.
Does outperforming Bitcoin mean that a coin made money?
No. An altcoin falling 2% while BTC falls 4% has a positive two-percentage-point excess return but still lost value. Read the median asset return beside the excess statistic to separate protection relative to BTC from an absolute positive result.
Likewise, outperforming on many days does not establish a better compounded outcome. A few large losses can dominate a sequence of small relative wins. This page describes conditional daily behavior, not a portfolio equity curve.
Why not use ordinary correlation or beta instead?
Correlation and beta usually summarize both positive and negative benchmark days. A coin may track BTC closely on average yet behave differently specifically during declines. Conditioning on negative BTC days targets the user's downside question directly.
This selection also reduces the number of observations. A quiet month may offer few negative benchmark days, making the estimate unstable. The five-day minimum is a publication threshold for descriptive evidence, not a claim of statistical certainty.
How can this help shortlist further research?
Begin with qualified rows and compare both absolute loss and relative excess. Inspect whether the sample contains severe selloffs or only small down days, then compare current liquidity and the longer-window beta page before interpreting resilience as persistent.
The basket is based on today's surviving liquid markets. Missing or delisted historical constituents are not reconstructed. This survivorship boundary must accompany any use in a report and prevents treating the ranking as an investable historical universe.
How can I audit and cite this measurement?
| Check | What to verify | Why it changes interpretation |
|---|---|---|
| Scope | Current liquid Binance USDT spot selection, matched against BTC on a 30-day calendar. | Do not generalize a named sample to the whole crypto market. |
| Formula | Select up to 20 current Binance USDT spot markets by descending quote turnover above the shared one-million-dollar liquidity floor, excluding classified non-crypto assets. Add BTC as benchmark. Require 31 consecutive daily closes in the fixed 30-day window. On dates where BTC close-to-close return is negative, compute asset return minus BTC return. Rank eligible rows by the median of paired excess returns; suppress results below five matched down days. | A similarly named indicator can use a different convention. |
| Data time | Observation window versus materialization time | A fresh computation is not necessarily a fresh source observation. |
| Delivery | Public evidence versus subscribed Market Events v1 | Inspect the data catalog before assuming commercial inclusion. |
What is measured, and what is not?
| Measured claim | Evidence on this page | Boundary |
|---|---|---|
| Which tracked altcoins lost less, or gained, on the same days that Bitcoin fell? | The current table and downloadable rows using downside-resilience. | Current liquid Binance USDT spot selection, matched against BTC on a 30-day calendar. |
| Results can be checked against an explicit computation. | Select up to 20 current Binance USDT spot markets by descending quote turnover above the shared one-million-dollar liquidity floor, excluding classified non-crypto assets. Add BTC as benchmark. Require 31 consecutive daily closes in the fixed 30-day window. On dates where BTC close-to-close return is negative, compute asset return minus BTC return. Rank eligible rows by the median of paired excess returns; suppress results below five matched down days. | Archive availability and revisions constrain historical reproducibility. |
Method and data boundary
Select up to 20 current Binance USDT spot markets by descending quote turnover above the shared one-million-dollar liquidity floor, excluding classified non-crypto assets. Add BTC as benchmark. Require 31 consecutive daily closes in the fixed 30-day window. On dates where BTC close-to-close return is negative, compute asset return minus BTC return. Rank eligible rows by the median of paired excess returns; suppress results below five matched down days.
Current liquid Binance USDT spot selection, matched against BTC on a 30-day calendar. Historical results are descriptive, not executed profits or guaranteed future behavior.
Sources and verification
- Binance Spot candle field documentationField definitions; statistical selection and outcome formulas are CoinNudge's own disclosed methods.
- CoinNudge methodologyShared boundaries, data time semantics and calculation contracts.
Frequently asked questions
Which tracked altcoins lost less, or gained, on the same days that Bitcoin fell?
This study conditions the comparison on Bitcoin's negative daily returns, rather than ranking coins over all market conditions. It reports each eligible altcoin's median return and median same-day excess return on those matched dates. A row requires 31 consecutive daily closes and at least five BTC-down days. Positive excess return means relative resilience, not necessarily an absolute gain. The universe is selected from currently liquid Binance Spot markets, so it cannot represent delisted or historically excluded assets.
How often do the numbers change?
A bounded background calculation runs at most every six hours. Look at the actual observation interval as well as the calculation time; missing and pending data are not filled with zero.