Who owns Somersby?
Somersby is owned by Carlsberg (Denmark, CPH: CARL-B).[1]
This ownership is reported in official statements but has not yet been matched to a regulatory filing.
Key facts
- Current owner
- Carlsberg A/S reported
- Owned since
- Not recorded
- Previous owner
- None recorded
- Owner HQ
- 🇩🇰 Denmark, Copenhagen
- Origin
- 🇩🇰 Denmark
- Founded
- 2008
- Category
- Beverages › Beer › Cider
- Parent ticker
- CPH: CARL-B
- Last verified
- · 1 sources
About Somersby
Somersby is a cider Carlsberg launched in 2008 and rolled out across more than fifty markets, giving the group a substantial position in a category dominated in its home markets by British and Irish producers. It is brewed under licence in many countries, which is how it reached that many markets so quickly.
Ownership timeline of Somersby
Where Somersby sits in Carlsberg
Controlling ownership as of . Brands grouped under the entity that owns them; large groups are collapsed.
Open the full Carlsberg ownership tree →
Other brands owned by Carlsberg in beverages
Latest news about Somersby
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 Somersby?
The parent company of Somersby is Carlsberg, a publicly listed company headquartered in Denmark.
Is Somersby Danish?
Yes. Somersby originated in Denmark in 2008 and its owner, Carlsberg, is also headquartered in Denmark.
Is Somersby still owned by Carlsberg?
Yes. As of 6 September 2026, Somersby is still owned by Carlsberg. 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] Carlsberg A/S Annual Report 2025 — Carlsberg A/S, Annual report, published 5 February 2026; retrieved 6 September 2026.
Report a correction Opens a pre-filled GitHub issue. See our corrections policy.