Brandtree

Who owns Kerasys?

Kerasys is owned by Aekyung (South Korea, KRX: 018250).[1]

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

Evidence: LUNA - Beauty brand page (Aekyung Industrial), Aekyung Industrial Co., Ltd. Last checked .

Key facts

Current owner
Aekyung Industrial Co., Ltd. reported
Owner HQ
🇰🇷 South Korea, Seoul
Origin
🇰🇷 South Korea
Category
Personal care & beauty › Hair care › Shampoo & conditioner
Parent ticker
KRX: 018250
Trademark registrant
Aekyung Industrial Co., Ltd. (USPTO)
Last verified
· 2 sources

About Kerasys

Kerasys is a hair-care brand of Aekyung Industrial. Its page says it was born from a mission to let people have professional salon-style hair clinic care at home, with its own damage-care technology and systems for different hair concerns. It lists shampoos and treatments, and a company-cited Kantar ranking by volume.

Trademark record for Kerasys

The USPTO record for the Kerasys mark lists Aekyung Industrial Co., Ltd. as the owner of record (serial number 78528476). That name matches the owner named above.[2]

Ownership timeline of Kerasys

  1. Current owner Aekyung [1] reported

Where Kerasys sits in Aekyung

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

Where Kerasys sits in Aekyung Tree of 14 brands under Aekyung. Aekyung Kerasys A-Solution AGE20'S Alpist Black Forêt By Color and 8 more

Open the full Aekyung ownership tree →

See the full Aekyung brand portfolio (14) →

Other brands owned by Aekyung

Aekyung controls 14 brands on Brandtree, 9 of them in personal care & beauty.

Also in personal care & beauty

All Aekyung brands →

Other brands in shampoo & conditioner, and who owns them

The 55 brands in shampoo & conditioner on Brandtree belong to 30 owners. The largest is Unilever, with 7; Aekyung has 3.

BrandOwnerOwner based in
Clear Unilever 🇬🇧 United Kingdom
Brillare Emami 🇮🇳 India
Garnier L'Oréal 🇫🇷 France
Aujua Milbon 🇯🇵 Japan
Movit Movit 🇺🇬 Uganda
Head & Shoulders Procter & Gamble 🇺🇸 United States
SebiRinse Ego Pharmaceuticals 🇦🇺 Australia
Tío Nacho Genomma Lab 🇲🇽 Mexico

Every brand in shampoo & conditioner and its owner →

About the owner: Aekyung

Aekyung is a publicly listed company headquartered in Seoul, South Korea. Brandtree records 14 brands under its control, and it is listed as KRX: 018250.

Aekyung Industrial is a South Korean beauty, personal-care and home-care company whose address is Yanghwa-ro, Mapo-gu, Seoul. Its website groups its brands into beauty (cosmetics), personal care (hair, body and dental care) and home care (hygiene, fabric care and kitchen living). The brand pages used here are in Korean and do not state ownership of the company itself, so no parent or stake is recorded above it.

Aekyung: full profile, brands and acquisition history →

🇰🇷 Kerasys and other South Korean brands

Brandtree records a controlling owner for 185 brands that began in South Korea. 7 of them (4%) are now controlled by a company headquartered in another country; Kerasys is not one of them.

All South Korean brands and who owns them →

Frequently asked questions

Who is the parent company of Kerasys?

The parent company of Kerasys is Aekyung, a publicly listed company headquartered in South Korea.

Is Kerasys South Korean?

Yes. Kerasys originated in South Korea and its owner, Aekyung, is also headquartered in South Korea.

Is Kerasys still owned by Aekyung?

Yes. As of 6 October 2026, Kerasys is still owned by Aekyung. The ownership record was last checked against primary sources on that date.

Sources (2) & 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] LUNA - Beauty brand page (Aekyung Industrial) — Aekyung Industrial Co., Ltd., Official document; retrieved 4 October 2026.
  2. [2] USPTO: KERASYS, serial 78528476 — United States Patent and Trademark Office, Trademark registry; retrieved 6 October 2026.

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