Who owns Calorie Mate?
Calorie Mate is owned by Otsuka (Japan, TSE: 4578).[1]
This ownership is reported in official statements but has not yet been matched to a regulatory filing.
Key facts
- Current owner
- Otsuka Holdings Co., Ltd. reported
- Owned since
- Not recorded
- Previous owner
- None recorded
- Owner HQ
- 🇯🇵 Japan, Tokyo
- Origin
- 🇯🇵 Japan
- Founded
- 1983
- Category
- Food › Nutrition & supplements › Nutrition bars
- Parent ticker
- TSE: 4578
- Last verified
- · 1 sources
About Calorie Mate
Calorie Mate is a dense block-shaped nutrition bar sold in Japan since 1983, designed as a balanced meal replacement rather than a snack. It is a fixture of Japanese convenience stores and of student and office desks. Its blocks come sealed in foil in pairs, and the company also sells the same formulation as a jelly drink.
Ownership timeline of Calorie Mate
Where Calorie Mate sits in Otsuka
Controlling ownership as of . Brands grouped under the entity that owns them; large groups are collapsed.
Open the full Otsuka ownership tree →
Other brands owned by Otsuka
Latest news about Calorie Mate
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 Calorie Mate?
The parent company of Calorie Mate is Otsuka, a publicly listed company headquartered in Japan.
Is Calorie Mate Japanese?
Yes. Calorie Mate originated in Japan in 1983 and its owner, Otsuka, is also headquartered in Japan.
Is Calorie Mate still owned by Otsuka?
Yes. As of 6 September 2026, Calorie Mate is still owned by Otsuka. 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] Otsuka Holdings Annual Report 2025 — Otsuka Holdings Co., Ltd., Annual report, published 27 March 2026; retrieved 6 September 2026.
Report a correction Opens a pre-filled GitHub issue. See our corrections policy.