SanDisk will join the S&P 500 index📈

SanDisk (SNDK.US) moved into the S&P 500, but it failed to boost short-term sentiments around the company shares as investors awaited this move since weeks. SanDisk is a data-storage technology company specializing in products such as flash memory, SSDs (solid-state drives), and high-performance storage solutions used across consumer electronics, cloud infrastructure, enterprise hardware and increasingly, AI-driven data centers. After its spinoff from Western Digital, SanDisk has been carving out a niche as a pure-play memory and storage manufacturer—one heavily leveraged to the explosion of AI workloads.

SanDisk joins the S&P 500 this Friday, replacing Interpublic Group, which is being acquired by Omnicom.
The stock has surged more than 500% since it was spun off from Western Digital in February making it one of 2025’s standout performers.
Demand for memory in AI infrastructure has fueled SanDisk’s rally, as data-heavy AI models require enormous amounts of fast storage.
Entering the S&P 500 typically brings added demand from institutional funds that must track the benchmark.
SanDisk now holds a market value above $33 billion, already larger than many long-standing S&P 500 constituents.
The company is moving up from the S&P 600 small-cap index, where it will be replaced by PTC Therapeutics.
The tech sector sell-off has triggered short-term pressure—SanDisk fell about 3% this morning after a 13% jump yesterday—but its year-long trend remains exceptional.
Recent S&P 500 entrants like Solstice Advance Materials and Qnity show a pattern: corporate spinoffs are increasingly becoming vehicles for fast-track index upgrades.

Investors usually pay attention when a company gets added to the S&P 500 because index funds must buy the stock, increasing demand, more analyst coverage and institutional visibility often follow. What's more it serves as a validation of business scale, profitability, and relevance in the broader market. SanDisk’s rapid ascent—from a February spinoff to a $33B index member—highlights how the AI boom is reshaping winners across the semiconductor and storage landscape.

Source: xStation5

Cookie name	Description
SERVERID
userBranchSymbol	Expiration date 1 day
adobe_unique_id	Expiration date 364 days
SESSID	Expiration date 1 day
__cf_bm	Expiration date 1 hour
intercom-id-iojaybix	Expiration date 270 days
intercom-session-iojaybix	Expiration date 6 days
xtbCookiesSettings	Expiration date 364 days
TS5b68a4e1027
xtbLanguageSettings	Expiration date 364 days
userPreviousBranchSymbol	Expiration date 364 days
countryIsoCode
intercom-device-id-iojaybix	Expiration date 270 days
test_cookie	Expiration date 1 hour
_cfuvid
OClmoOot	Expiration date 18262 days

Cookie name	Description
_gid	Expiration date 1 day
_gat_UA-121192761-1	Expiration date 1 hour
_gat_UA-190421227-1	Expiration date 1 hour
_ga_CBPL72L2EC	Expiration date 729 days
_ga	Expiration date 729 days
AnalyticsSyncHistory	Expiration date 29 days
__hstc	Expiration date 179 days
__hssrc
__hssc	Expiration date 1 hour
_vwo_uuid_v2	Expiration date 365 days
_gcl_au	Expiration date 89 days
_ga_TC79BEJ20L	Expiration date 729 days
_vwo_uuid	Expiration date 365 days
_vwo_ds	Expiration date 29 days
_vwo_sn	Expiration date 1 hour
_vis_opt_s	Expiration date 99 days
_vis_opt_test_cookie
af_id	Expiration date 394 days
afUserId	Expiration date 730 days
AF_SYNC	Expiration date 6 days
guest_id	Expiration date 729 days

Cookie name	Description
_omappvp	Expiration date 3998 days
_omappvs	Expiration date 1 hour
_fbp	Expiration date 89 days
fr	Expiration date 89 days
muc_ads	Expiration date 729 days
lang
_ttp	Expiration date 89 days
_tt_enable_cookie	Expiration date 89 days
hubspotutk	Expiration date 179 days
IDE	Expiration date 389 days
li_sugr	Expiration date 89 days
_uetsid	Expiration date 1 day
_uetvid	Expiration date 389 days
MUID	Expiration date 389 days
guest_id_marketing	Expiration date 729 days
guest_id_ads	Expiration date 729 days
MSPTC	Expiration date 389 days
_rdt_uuid	Expiration date 89 days

Cookie name	Description
personalization_id	Expiration date 729 days
UserMatchHistory	Expiration date 29 days
bcookie	Expiration date 364 days
lidc	Expiration date 1 day
lang
bscookie	Expiration date 364 days
li_gc	Expiration date 179 days