Who owns Pepero?
Pepero is owned by Lotte (South Korea, KRX: 004990).[1]
This ownership is reported in official statements but has not yet been matched to a regulatory filing.
Key facts
- Current owner
- Lotte Corporation reported
- Owned since
- Not recorded
- Previous owner
- None recorded
- Owner HQ
- 🇰🇷 South Korea, Seoul
- Origin
- 🇰🇷 South Korea
- Founded
- 1983
- Category
- Food › Confectionery › Chocolate
- Parent ticker
- KRX: 004990
- Last verified
- · 1 sources
About Pepero
Pepero is a chocolate-coated biscuit stick launched in 1983 and closely resembling the Japanese Pocky. Pepero Day on 11 November, chosen because the date resembles four sticks, has become a substantial informal gift-giving occasion in Korea. Lotte says the date was adopted by schoolgirls before the company began promoting it.
Ownership timeline of Pepero
Where Pepero sits in Lotte
Controlling ownership as of . Brands grouped under the entity that owns them; large groups are collapsed.
Open the full Lotte ownership tree →
Other brands owned by Lotte in food
Latest news about Pepero
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 Pepero?
The parent company of Pepero is Lotte, a publicly listed company headquartered in South Korea.
Is Pepero South Korean?
Yes. Pepero originated in South Korea in 1983 and its owner, Lotte, is also headquartered in South Korea.
Is Pepero still owned by Lotte?
Yes. As of 6 September 2026, Pepero is still owned by Lotte. 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] Lotte Corporation — business and brands — Lotte Corporation, Official document; retrieved 6 September 2026.
Report a correction Opens a pre-filled GitHub issue. See our corrections policy.