Who owns Sayaendo?
Sayaendo is owned by Calbee (Japan, TSE: 2229).[1]
This ownership is reported in official statements but has not yet been matched to a regulatory filing.
Key facts
- Current owner
- Calbee, Inc. reported
- Owned since
- Not recorded
- Previous owner
- None recorded
- Owner HQ
- 🇯🇵 Japan, Tokyo
- Origin
- 🇯🇵 Japan
- Founded
- 1993
- Category
- Food › Snacks › Salty snacks
- Parent ticker
- TSE: 2229
- Last verified
- · 1 sources
About Sayaendo
Sayaendo is a green pea snack launched in 1993 and shaped like peas in a pod, with a mascot character on the package that also appeared in television advertising. It is sold in Thailand under the local name BunBun, and its recipe became the basis for Harvest Snaps, the brand Calbee built for North America.
Ownership timeline of Sayaendo
Where Sayaendo sits in Calbee
Controlling ownership as of . Brands grouped under the entity that owns them; large groups are collapsed.
Open the full Calbee ownership tree →
Other brands owned by Calbee in food
Latest news about Sayaendo
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 Sayaendo?
The parent company of Sayaendo is Calbee, a publicly listed company headquartered in Japan.
Is Sayaendo Japanese?
Yes. Sayaendo originated in Japan in 1993 and its owner, Calbee, is also headquartered in Japan.
Is Sayaendo still owned by Calbee?
Yes. As of 16 September 2026, Sayaendo is still owned by Calbee. 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] Calbee Group Integrated Report 2025 — Calbee, Inc., Annual report; retrieved 16 September 2026.
Report a correction Opens a pre-filled GitHub issue. See our corrections policy.