Who owns Olvi Vichy?
Olvi Vichy is owned by Olvi (Finland, HEL: OLVAS).[1]
This ownership is reported in official statements but has not yet been matched to a regulatory filing.
Key facts
- Current owner
- Olvi plc reported
- Owned since
- Not recorded
- Previous owner
- None recorded
- Owner HQ
- 🇫🇮 Finland, Iisalmi
- Origin
- 🇫🇮 Finland
- Category
- Beverages › Soft drinks › Bottled water
- Parent ticker
- HEL: OLVAS
- Last verified
- · 1 sources
About Olvi Vichy
Olvi Vichy is a vichy-type mineral water made by Olvi in Finland. According to Olvi's 2025 annual report it is the most purchased vichy-type mineral water in the Finnish retail market, one of the non-alcoholic products the Iisalmi brewer highlights as it works to raise the share of non-alcoholic drinks in its total sales volume.
Ownership timeline of Olvi Vichy
Where Olvi Vichy sits in Olvi
Controlling ownership as of . Brands grouped under the entity that owns them; large groups are collapsed.
Open the full Olvi ownership tree →
Other brands owned by Olvi in beverages
Latest news about Olvi Vichy
No tagged news items yet. Deals, regulatory actions and recalls are added from SEC filings, regulators and trade press; 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 Olvi Vichy?
The parent company of Olvi Vichy is Olvi, a publicly listed company headquartered in Finland.
Is Olvi Vichy Finnish?
Yes. Olvi Vichy originated in Finland and its owner, Olvi, is also headquartered in Finland.
Is Olvi Vichy still owned by Olvi?
Yes. As of 16 September 2026, Olvi Vichy is still owned by Olvi. 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] Olvi Group Annual Report 2025 — Olvi plc, Annual report; retrieved 16 September 2026.
Report a correction Opens a pre-filled GitHub issue. See our corrections policy.