Who owns Formosa?
Formosa is owned by TTL (Taiwan).[1]
This ownership is reported in official statements but has not yet been matched to a regulatory filing.
Key facts
- Current owner
- Taiwan Tobacco & Liquor Corporation reported
- Owned since
- Not recorded
- Previous owner
- None recorded
- Owner HQ
- 🇹🇼 Taiwan, Taipei
- Origin
- 🇹🇼 Taiwan
- Category
- Tobacco & nicotine › Tobacco products › Cigarettes
- Last verified
- · 1 sources
About Formosa
Formosa is a cigarette product line from Taiwan Tobacco & Liquor Corporation, named on TTL's own English-language corporate history page alongside a "Tien Leaf Formosa" variant, part of the range TTL developed with varying packaging, design, taste and price positioning after Taiwan's tobacco and alcohol monopoly system ended in 2002.
Ownership timeline of Formosa
Where Formosa sits in TTL
Controlling ownership as of . Brands grouped under the entity that owns them; large groups are collapsed.
Open the full TTL ownership tree →
Other brands owned by TTL in tobacco & nicotine
Latest news about Formosa
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 Formosa?
The parent company of Formosa is TTL, a state-owned company headquartered in Taiwan.
Is Formosa Taiwanese?
Yes. Formosa originated in Taiwan and its owner, TTL, is also headquartered in Taiwan.
Is Formosa still owned by TTL?
Yes. As of 21 September 2026, Formosa is still owned by TTL. 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] 台灣菸酒股份有限公司 — 沿革 (Company History) — Taiwan Tobacco & Liquor Corporation, Official document; retrieved 21 September 2026.
Report a correction Opens a pre-filled GitHub issue. See our corrections policy.