Zain Group
Kuwaiti multinational telecommunications company
Mobile Telecommunications Company K.S.C.P. (doing business as Zain) (زين [zeːn]) is a Kuwaiti mobile telecommunications company founded on 22 June 1983 in Kuwait as MTC (an abbreviation for its predecessor's former name, the Mobile Telecommunications Company), and later rebranded as Zain in 2007. Zain has a commercial presence in eight countries across the Middle East with 50.9 million active customers as of 31 December 2025. The Vice Chairman and Group CEO is Bader Nasser Al-Kharafi, who was appointed in March 2017.
As of 2024, the two major stakeholders are Kuwait Investment Authority with 15.9% and Omantel with 21.9%.
The Zain brand is one of the most recognized telecom brands across the MENA region, with a brand value of US$3.5 billion (2025).
Zain Group was ranked 35th on Forbes Middle East's Top 100 Listed Companies 2025 list.
History
It was founded on 22 June 1983 in Kuwait as MTC (an abbreviation for its predecessor's former name, the Mobile Telecommunications Company), and later rebranded as Zain in 2007. Zain is listed on the Kuwait Stock Exchange.
For FY-2025, Zain Group generated consolidated revenue of KD 2.3 billion (US$7.44 billion), up 14% YoY. Consolidated EBITDA for the period reached KD 780 million (US$2.54 billion), with EBITDA growth of 11%, reflecting an EBITDA margin of 34%. Consolidated net income reached KD 239 million (US$777 million), up 103% YoY. Earnings per share amounted to 55 fils (US$0.18)
Operations
Zain has presence in a number of countries.
This brief starts where responsible research should: with the source description of “Zain Group” as kuwaiti multinational telecommunications company. Everything that follows is an evidence route, not borrowed authority.
Why this record matters
The subject matters to the history & society register because the source frames it as kuwaiti multinational telecommunications company. Its deeper value depends on whether names, dates, institutions and citations support that framing.
Contemporary correspondence, administrative files and participant testimony can test how later narratives organized the event or institution. The source revision retrieved here is dated Sep 21, 2026. The linked authority identifier is Q144364. None of the 2 selected statements returned an explicit reference. The first chronological checks are 1983, 2007, 2025 and 2017.
Later summaries often reconcile disputed chronology or motive more neatly than the contemporary record permits. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Compare institutional narratives with records created by participants and affected communities. Dates and formal titles are useful anchors, but not substitutes for context.
- Event chronology
- Institutional context
- Locating named record creators
Contemporary correspondence, government or organizational records, oral histories and cited historical scholarship.
Three-step research path
- Establish the record: confirm the title “Zain Group”, its source revision and the description used here.
- Expand the search: follow Zain Group primary sources, Zain Group archive and Zain research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Zain Group”?
- What chronology connects this entry to wider political or social change?
- Who created the surviving record, and for what administrative purpose?
Search terms from this dossier
This entry incorporates text from “Zain Group” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.