Who owns Onitsuka Tiger?
Onitsuka Tiger is owned by ASICS (Japan, TSE: 7936).[1]
This ownership is reported in official statements but has not yet been matched to a regulatory filing.
Key facts
- Current owner
- ASICS Corporation reported
- Owned since
- Not recorded
- Previous owner
- None recorded
- Owner HQ
- 🇯🇵 Japan, Kobe
- Origin
- 🇯🇵 Japan
- Founded
- 1949
- Category
- Apparel, footwear & accessories › Sportswear & footwear › Athletic footwear
- Parent ticker
- TSE: 7936
- Last verified
- · 1 sources
About Onitsuka Tiger
Onitsuka Tiger is the original name of the company, revived in 2002 as a heritage fashion line. Its Mexico 66 shoe, with the crossed stripes designed in 1966, was worn by Bruce Lee in a yellow tracksuit and is the brand's largest seller.
Ownership timeline of Onitsuka Tiger
Where Onitsuka Tiger sits in ASICS
Controlling ownership as of . Brands grouped under the entity that owns them; large groups are collapsed.
Open the full ASICS ownership tree →
Other brands owned by ASICS
Latest news about Onitsuka Tiger
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 Onitsuka Tiger?
The parent company of Onitsuka Tiger is ASICS, a publicly listed company headquartered in Japan.
Is Onitsuka Tiger Japanese?
Yes. Onitsuka Tiger originated in Japan in 1949 and its owner, ASICS, is also headquartered in Japan.
Is Onitsuka Tiger still owned by ASICS?
Yes. As of 6 September 2026, Onitsuka Tiger is still owned by ASICS. 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] ASICS Corporation Integrated Report 2025 — ASICS Corporation, Annual report, published 27 March 2026; retrieved 6 September 2026.
Report a correction Opens a pre-filled GitHub issue. See our corrections policy.