Who owns Elden Ring?
Elden Ring is owned by Bandai Namco (Japan, TSE: 7832).[1]
This ownership is reported in official statements but has not yet been matched to a regulatory filing.
Key facts
- Current owner
- BANDAI NAMCO Holdings Inc. reported
- Owned since
- Not recorded
- Previous owner
- None recorded
- Owner HQ
- 🇯🇵 Japan, Tokyo
- Origin
- 🇯🇵 Japan
- Founded
- 2022
- Category
- Internet & digital › Platforms & devices › Video games
- Parent ticker
- TSE: 7832
- Last verified
- · 1 sources
About Elden Ring
Elden Ring was developed by FromSoftware with the novelist George R. R. Martin contributing to its world, and Bandai Namco publishes it. It sold more than twenty-five million copies and won the major game of the year awards for 2022.
Ownership timeline of Elden Ring
- 2022 – present Bandai Namco [1] reported
Where Elden Ring sits in Bandai Namco
Controlling ownership as of . Brands grouped under the entity that owns them; large groups are collapsed.
Open the full Bandai Namco ownership tree →
Other brands owned by Bandai Namco
Latest news about Elden Ring
No tagged news items yet. Headlines are added nightly from public feeds; only titles and links are stored.
Headlines link to the original publisher. Brandtree does not reproduce article text.
Frequently asked questions
Who is the parent company of Elden Ring?
The parent company of Elden Ring is Bandai Namco, a publicly listed company headquartered in Japan.
Is Elden Ring Japanese?
Yes. Elden Ring originated in Japan in 2022 and its owner, Bandai Namco, is also headquartered in Japan.
Is Elden Ring still owned by Bandai Namco?
Yes. As of 8 September 2026, Elden Ring is still owned by Bandai Namco. The ownership record was last checked against primary sources on that date.
Sources (1) & corrections
Last verified . Every ownership fact above is backed by one of these primary documents. Numbers in brackets in the text refer to this list.
- [1] BANDAI NAMCO Holdings Integrated Report 2025 — BANDAI NAMCO Holdings Inc., Annual report, published 12 September 2025; retrieved 8 September 2026.
Report a correction Opens a pre-filled GitHub issue. See our corrections policy.