Enerjisa Enerji: brands it owns and its ownership tree
Enerjisa Enerji (BIST: ENJSA) is a publicly listed company headquartered in Turkey that owns 5 consumer brands.[1]
Enerjisa Enerji is a Turkish electricity distribution and retail company traded on Borsa İstanbul under the ticker ENJSA since 8 February 2018. Its own site says it continues under the partnership of Sabancı Holding and E.ON, which have equal shares, after 20 percent was floated in 2018. Its 2025 integrated annual report lists Başkent EDAŞ, AYEDAŞ and Toroslar EDAŞ with their retail companies, Enerjisa Müşteri Çözümleri and Eşarj, all 100 percent held.
-
brands owned
-
1
categories
-
0
acquisitions recorded
-
0
divestitures recorded
Company facts
- Legal name
- Enerjisa Enerji A.Ş. (also Enerjisa)
- Type
- publicly listed company · see all publicly listed company owners
- Headquarters
- 🇹🇷 Turkey
- Tickers
- BIST: ENJSA
- Website
- www.enerjisa.com.tr
- Last verified
- · 1 sources
Enerjisa Enerji in numbers
- Enerjisa Enerji owns 5 consumer brands tracked here across 1 top-level categories; the largest is energy with 5 brands.[1]
Everything Enerjisa Enerji owns
Controlling ownership as of . Brands grouped under the entity that owns them; large groups are collapsed.
Full-screen interactive tree →
Brand portfolio by category
Recent changes to this record
Frequently asked questions
What brands does Enerjisa Enerji own?
Enerjisa Enerji owns 5 consumer brands tracked here, including Enerjisa, Başkent EDAŞ, Eşarj, AYEDAŞ and Toroslar EDAŞ.
Is Enerjisa Enerji a Turkish company?
Yes. Enerjisa Enerji is headquartered in Turkey.
Who owns Enerjisa Enerji?
Enerjisa Enerji is a publicly listed company owned by its shareholders; it trades as ENJSA on the BIST.
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] Enerjisa Enerji 2025 Integrated Annual Report — Enerjisa Enerji A.Ş., Annual report; retrieved 5 October 2026.
Report a correction Opens a pre-filled GitHub issue. See our corrections policy.