Who owns Bulleit?
Bulleit is owned by Diageo (the United Kingdom, LSE: DGE).[1]
Key facts
- Current owner
- Diageo plc verified
- Owned since
- Not recorded
- Previous owner
- None recorded
- Owner HQ
- 🇬🇧 United Kingdom, London
- Origin
- 🇺🇸 United States, Kentucky
- Founded
- 1987
- Category
- Beverages › Spirits › Whisky & bourbon
- Parent ticker
- LSE: DGE NYSE: DEO
- Last verified
- · 1 sources
About Bulleit
Bulleit is a high-rye bourbon revived in 1987 by Tom Bulleit, who reconstructed a family recipe from the 1830s. Diageo acquired the brand in 1997 and built it through the cocktail revival of the 2000s, when the higher rye content suited bartenders making classic drinks.
Ownership timeline of Bulleit
Where Bulleit sits in Diageo
Controlling ownership as of . Brands grouped under the entity that owns them; large groups are collapsed.
Open the full Diageo ownership tree →
Other brands owned by Diageo in beverages
Latest news about Bulleit
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 Bulleit?
The parent company of Bulleit is Diageo, a publicly listed company headquartered in the United Kingdom.
Is Bulleit American or British?
Bulleit originated in the United States in 1987, but it is owned today by Diageo, which is headquartered in the United Kingdom. So Bulleit is an American-origin brand under British ownership.
Is Bulleit still owned by Diageo?
Yes. As of 6 September 2026, Bulleit is still owned by Diageo. 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] Diageo plc Annual Report on Form 20-F filed 2026-08-18 — SEC EDGAR, SEC Form 20-F, published 18 August 2026; retrieved 6 September 2026.
Report a correction Opens a pre-filled GitHub issue. See our corrections policy.