Brandtree

Who owns Lipovitan D?

Lipovitan D is owned by Taisho Pharmaceutical (Japan).[1]

This ownership is reported in official statements but has not yet been matched to a regulatory filing.

Evidence: Taisho Pharmaceutical: History, Taisho Pharmaceutical Co., Ltd. Last checked .

Key facts

Current owner
Taisho Pharmaceutical Holdings Co., Ltd. reported
Owner HQ
🇯🇵 Japan, Tokyo
Origin
🇯🇵 Japan
Founded
1962
Category
Beverages › Soft drinks › Energy drinks
Last verified
· 1 sources

About Lipovitan D

Energy drink released by Taisho in 1962, when medicines packaged in ampoules were the norm; Taisho enlarged the volume, flavoured and chilled it for drinking. Exports began to Taiwan in 1963 and to Thailand in 1965. Deregulation in 1999 let it be sold in convenience stores as a quasi-drug. Overseas versions are adapted to local taste, in cans, sweetened with honey or carbonated.

Ownership timeline of Lipovitan D

Owners of Lipovitan D over 1962 to 2026 Taisho Pharmaceutical start not recorded–present Taisho Pharmaceutical (start not recorded) 197019801990200020102020
  1. Current owner Taisho Pharmaceutical [1] reported

Where Lipovitan D sits in Taisho Pharmaceutical

Controlling ownership as of . Brands grouped under the entity that owns them; large groups are collapsed.

Where Lipovitan D sits in Taisho Pharmaceutical Tree of 7 brands under Taisho Pharmaceutical. Taisho Pharmaceutical Lipovitan D Biofermin Dafalgan Efferalgan Hapacol Naron and 1 more

Open the full Taisho Pharmaceutical ownership tree →

See the full Taisho Pharmaceutical brand portfolio (7) →

Other brands owned by Taisho Pharmaceutical

Taisho Pharmaceutical controls 7 brands on Brandtree.

Founded in the 1960s

All Taisho Pharmaceutical brands →

Other brands in energy drinks, and who owns them

The 44 brands in energy drinks on Brandtree belong to 34 owners. The largest is Monster Beverage, with 5.

BrandOwnerOwner based in
Bang Energy Monster Beverage 🇺🇸 United States
Climax Heineken 🇳🇱 Netherlands
M-150 Osotspa 🇹🇭 Thailand
Alani Nu Celsius Holdings 🇺🇸 United States
Baikal Chernogolovka 🇷🇺 Russia
Boost A.G. Barr 🇬🇧 United Kingdom
Volt AJE 🇵🇪 Peru
Collab Bera 🇮🇸 Iceland

Every brand in energy drinks and its owner →

About the owner: Taisho Pharmaceutical

Taisho Pharmaceutical is a privately held company headquartered in Tokyo, Japan, founded in 1912. Brandtree records 7 brands under its control.

Japanese pharmaceutical and over-the-counter health company, founded in 1912 and based in Toshima-ku, Tokyo. Its shares were delisted from the stock exchange on 9 April 2024, so it is now unlisted. Outside Japan it bought Bristol-Myers Squibb's Asian OTC trademarks in 2009 and took control of Vietnam's Duoc Hau Giang (DHG) and France's UPSA in 2019; Taisho also sells some brands in Japan under licence from other owners (for example Vicks and Claritin), which are not listed here.

Taisho Pharmaceutical: full profile, brands and acquisition history →

🇯🇵 Lipovitan D and other Japanese brands

Brandtree records a controlling owner for 437 brands that began in Japan. 21 of them (5%) are now controlled by a company headquartered in another country; Lipovitan D is not one of them.

All Japanese brands and who owns them →

Frequently asked questions

Who is the parent company of Lipovitan D?

The parent company of Lipovitan D is Taisho Pharmaceutical, a privately held company headquartered in Japan.

Is Lipovitan D Japanese?

Yes. Lipovitan D originated in Japan in 1962 and its owner, Taisho Pharmaceutical, is also headquartered in Japan.

Is Lipovitan D still owned by Taisho Pharmaceutical?

Yes. As of 4 October 2026, Lipovitan D is still owned by Taisho Pharmaceutical. 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. [1] Taisho Pharmaceutical: History — Taisho Pharmaceutical Co., Ltd., Official document; retrieved 4 October 2026.

Report a correction Opens a pre-filled GitHub issue. See our corrections policy.