CoinmarketcapCoinmarketcap historical snapshots show how crypto rankings change over time
Coinmarketcap historical snapshots show cryptocurrency rankings and market data for selected past dates. They let you compare which assets appeared in a ranking, where they stood and how their recorded valuations changed. Those dated views separate an asset’s relative position from its price performance. A move upward can reflect larger losses elsewhere, and a weekly archive can miss changes between its listed dates. The appropriate historical record depends on the date and question that you need to answer.
· updatedWeekly archive dates and daily records serve different comparisons
The weekly archive suits comparisons between its listed dates, while the API’s daily historical listings suit questions tied to a particular calendar date. Its index groups available snapshots by year and month. Individual pages show the selected date above an asset table, with navigation between weeks.
When the task concerns one asset’s price path, historical quotes provide a series across time. A market snapshot describes the ranking on one date; it does not reconstruct the route between dates. These views share data categories, yet their sampling and purpose differ. Locating a rank change within a gap between archive dates requires more closely spaced ranking observations.
What does a historical rank change actually measure?
A historical rank change measures movement within the ranked list between selected dates, under the applicable ranking rules. A lower rank number places an asset higher in that list. Circulating market capitalization uses the recorded price and circulating supply, so either input can change the valuation.
Rank changes also depend on other assets. An asset can gain positions while its own price falls if competing valuations fall further. Supply growth can support a larger capitalization without a matching gain in unit price. Eligibility rules involve data verification and market quality, so sorting every displayed valuation yourself need not reproduce the published ranking.
Snapshot columns carry different historical meanings
The available columns describe position, valuation or trading activity. Price expresses the value of one unit. Circulating supply expresses a quantity of coins or tokens, while market capitalization combines both inputs.
Percentage headers identify their own trailing windows, such as 1 hour, 24 hours or 7 days where those figures appear. A percentage on an old snapshot belongs to that historical observation. It does not measure the change from the snapshot date to today, or between any two dates that a reader chooses.
The 24-hour volume field describes reported spot trading during that window, subject to the platform’s market exclusions. It is a flow of trading activity, separate from the circulating valuation. Large volume does not establish an equally large inflow of new money, since trading includes repeated purchases and sales.
Compare past membership without selecting today’s survivors
Historical membership lets you study the assets that a ranking contained at an earlier date. Starting with today’s leading assets changes that population, excluding former constituents before the comparison even begins. This selection can make the past look more successful than it was.
A list assembled from a current watchlist inherits the same selection. It answers how today’s chosen assets behaved historically. It cannot describe the full earlier ranking when that ranking included other assets. The distinction matters whenever the question concerns persistence, turnover or the composition of the market.
Snapshot comparisons also need a consistent range of positions. An entry missing from a short later list may sit farther down the broader ranking. Treating every disappearance as a failure confuses the comparison boundary with the asset’s status.
A weekly series still samples dates. An asset may enter and leave a selected rank range between observations, so matching endpoint lists do not prove uninterrupted membership. More observations improve the description of movement within the period. They cannot establish changes that the available dates do not capture.
Asset identity connects records across rebrands
A rebrand can change a listing’s name or ticker. A token migration can involve a separate successor listing. Matching only ticker text can join different assets or split one history incorrectly.
Coinmarketcap assigns permanent numeric identifiers to listings, making them useful anchors for historical data. A successor token can have its own entry, so continuity requires the documented relationship between those records. A shared project name does not establish a continuous token price series, especially when token units change. Retaining the historical identifier and distinguishing successor entries preserves the meaning of earlier observations without assuming that a later ticker explains every past row.
Matching dates separates price returns from rank changes
Price returns require matching start and end observations in the same quote currency, with compatible asset units. A rank movement supplies neither price. Comparing ending prices with starting prices measures price performance, while comparing capitalization also includes changes in the reported circulating supply.
Historical daily listings reflect market data at the end of each UTC day. A weekly archive comparison spans its actual listed dates, which may differ from a calendar month or an event window. Changing an endpoint changes the period under examination and can change the apparent outcome. Portfolio returns require holdings and transaction records as well; a ranking alone contains neither.
Choose the record that matches the date
For a comparison around a dated market event, the weekly archive and daily historical listings offer different observation dates. Both require records that match the period under examination. The archive fits when its listed dates answer the question. Daily listings provide finer date coverage, subject to the API plan’s historical access.
- Use the weekly archive when the required observation dates appear in its index.
- Choose daily historical listings when the question needs a calendar date between indexed weeks.
- Keep the same asset range and quote currency on both sides of the comparison.
- Match asset identities, distinguishing predecessor and successor entries when applicable.
- Confirm that the records show the selected dates and cover the intended ranking range.
Substituting a nearby weekly date changes the comparison’s endpoint, so any rank difference belongs to that revised period. A nearby observation leaves an exact day-specific question unanswered, even when the table contains the expected asset.
Can an absent asset be treated as a failed project?
Absence from a selected snapshot does not establish that a project failed or that its historical value became zero. The absence may concern the selected date, the range displayed or the relationship between old and successor listings. Ranking eligibility and listing status also affect what a record shows.
Project closure, trading cessation and loss of token value are different claims that require separate evidence. When available records do not resolve an absence, leave the observation unclassified. A snapshot that lacks an asset’s row also cannot supply its price for that date.
Retain unresolved entries in the membership comparison and mark their returns as missing, so gaps do not silently change the original asset set.
What readers ask about Coinmarketcap
How far back does the historical snapshot archive go?
The public historical snapshot archive begins on 28 April 2013. That starting point describes the archive, not the launch date of every cryptocurrency or the beginning of all crypto trading. An asset’s usable history depends on when its records appear, so the archive’s earliest date does not establish coverage for a particular asset.
Can historical listings retrieve a rank from an exact time of day?
Historical listings return daily snapshots, so they do not provide a ranking for an arbitrary intraday moment. The date parameter accepts a timestamp, but the endpoint uses its date portion. Sending a time within that timestamp does not change the daily observation into an hourly ranking.
Does a dash in a historical snapshot mean there was no price change?
A dash in a price-change column indicates that the snapshot does not display a percentage for that window. It does not establish a zero price change. Keep the field missing unless a compatible historical record supplies it, since replacing missing data with zero changes a comparison.
How can I tell whether an API snapshot covers the whole ranking?
Historical listings use pagination, so a successful response can contain only part of the ranking. The start and limit parameters control the portion returned. A response that reaches the requested limit does not establish that no further entries exist. Retrieve further pages with the same date, ranking order and asset-type selection, advancing start by the number of entries returned until a successful page returns fewer entries than limit. Collecting those pages covers the selected list; an asset-type filter still excludes other assets.
Are trading fees included in historical snapshot prices?
Snapshot prices are reference market prices, not a calculation of returns after trading fees. A return reconstructed from historical quotes needs separate trading-cost assumptions when it represents an executable strategy. Fees, bid-ask spreads and slippage can change the realized outcome, even when the historical start and end prices are accurate.
Is one snapshot’s volume enough to calculate a full week’s trading volume?
A snapshot’s 24-hour volume does not measure trading across an entire week. Weekly archive spacing describes the observation schedule, while the volume field retains its shorter measurement window. Adding isolated weekly readings leaves the intervening trading periods uncounted. A weekly total requires volume observations that cover the period without gaps or overlap.