Who owns SUNAO?
SUNAO is owned by Glico (Japan, TSE: 2206).[1]
This ownership is reported in official statements but has not yet been matched to a regulatory filing.
Key facts
- Current owner
- Ezaki Glico Co., Ltd. reported
- Owned since
- Not recorded
- Previous owner
- None recorded
- Owner HQ
- 🇯🇵 Japan, Osaka
- Origin
- 🇯🇵 Japan
- Founded
- 2017
- Category
- Food › Frozen food › Ice cream
- Parent ticker
- TSE: 2206
- Last verified
- · 1 sources
About SUNAO
SUNAO is Glico's lower-carbohydrate range, launched in 2017 as an ice cream that uses soy milk and corn fibre to keep its rich taste. Biscuits with half the carbohydrates of ordinary soft biscuits followed in 2018, then pasta and sauce in 2022 and frozen fresh pasta in 2024, all marketed as staples and sweets with appropriate sugar content.
Ownership timeline of SUNAO
Where SUNAO sits in Glico
Controlling ownership as of . Brands grouped under the entity that owns them; large groups are collapsed.
Open the full Glico ownership tree →
Other brands owned by Glico in food
Latest news about SUNAO
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 SUNAO?
The parent company of SUNAO is Glico, a publicly listed company headquartered in Japan.
Is SUNAO Japanese?
Yes. SUNAO originated in Japan in 2017 and its owner, Glico, is also headquartered in Japan.
Is SUNAO still owned by Glico?
Yes. As of 16 September 2026, SUNAO is still owned by Glico. 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] Ezaki Glico — Business Introduction — Ezaki Glico Co., Ltd., Official document; retrieved 16 September 2026.
Report a correction Opens a pre-filled GitHub issue. See our corrections policy.