Who owns Xylish?
Xylish is owned by Meiji (Japan, TSE: 2269).[1]
This ownership is reported in official statements but has not yet been matched to a regulatory filing.
Key facts
- Current owner
- Meiji Holdings Co., Ltd. reported
- Owned since
- Not recorded
- Previous owner
- None recorded
- Owner HQ
- 🇯🇵 Japan, Tokyo
- Origin
- 🇯🇵 Japan
- Founded
- 1997
- Category
- Food › Confectionery › Gum & mints
- Parent ticker
- TSE: 2269
- Last verified
- · 1 sources
About Xylish
Xylish is a sugar-free chewing gum sweetened with xylitol, launched in 1997 when Japanese regulators approved the sweetener for food use. Xylitol gum is far more prominent in the Japanese market than in Western ones. Meiji makes it, and Japanese dental associations have actively promoted xylitol gum in a way few other countries have.
Ownership timeline of Xylish
Where Xylish sits in Meiji
Controlling ownership as of . Brands grouped under the entity that owns them; large groups are collapsed.
Open the full Meiji ownership tree →
Other brands owned by Meiji in food
Latest news about Xylish
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 Xylish?
The parent company of Xylish is Meiji, a publicly listed company headquartered in Japan.
Is Xylish Japanese?
Yes. Xylish originated in Japan in 1997 and its owner, Meiji, is also headquartered in Japan.
Is Xylish still owned by Meiji?
Yes. As of 6 September 2026, Xylish is still owned by Meiji. 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] Meiji Holdings Co., Ltd. Integrated Report 2025 — Meiji Holdings Co., Ltd., Annual report, published 30 September 2025; retrieved 6 September 2026.
Report a correction Opens a pre-filled GitHub issue. See our corrections policy.