Who owns Elastine?
Elastine is owned by LG H&H (South Korea, KRX: 051900).[1]
This ownership is reported in official statements but has not yet been matched to a regulatory filing.
Key facts
- Current owner
- LG H&H Co., Ltd. reported
- Owned since
- Not recorded
- Previous owner
- None recorded
- Owner HQ
- 🇰🇷 South Korea, Seoul
- Origin
- 🇰🇷 South Korea
- Founded
- 2002
- Category
- Personal care & beauty › Hair care › Shampoo & conditioner
- Parent ticker
- KRX: 051900
- Last verified
- · 1 sources
About Elastine
Elastine is a hair care brand launched in 2002 and one of the leading shampoo lines in South Korea, positioned around damage repair and sold across Asia alongside LG H&H's other household brands. Korean hair care has a strong emphasis on damage from colouring and heat styling, which is the concern the range was built around.
Ownership timeline of Elastine
Where Elastine sits in LG H&H
Controlling ownership as of . Brands grouped under the entity that owns them; large groups are collapsed.
Open the full LG H&H ownership tree →
Other brands owned by LG H&H in personal care & beauty
Latest news about Elastine
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 Elastine?
The parent company of Elastine is LG H&H, a publicly listed company headquartered in South Korea.
Is Elastine South Korean?
Yes. Elastine originated in South Korea in 2002 and its owner, LG H&H, is also headquartered in South Korea.
Is Elastine still owned by LG H&H?
Yes. As of 6 September 2026, Elastine is still owned by LG H&H. 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] LG H&H Co., Ltd. Annual Report 2025 — LG H&H Co., Ltd., Annual report, published 20 March 2026; retrieved 6 September 2026.
Report a correction Opens a pre-filled GitHub issue. See our corrections policy.