BIZTRAC BETA
General medical practice activities

DARYAZ KLINIKK AS

Org. no. 935115183 Limited company (AS) Ålesund Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 3.8m
Operating profit NOK 1.0m
Equity NOK 1.0m
Incorporated 2025
Share capital NOK 30,000

DARYAZ KLINIKK AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 935115183. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tjenester innen legevirksomhet, og medisinske pluss estetiske behandlinger, herunder injeksjonsbehandlinger og hudbehandlinger. Videre kjøp/salg og drift av fast eiendom, kjøp/salg av aksjer og andre verdipapirer og hva som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.8m in revenue and NOK 1.0m in operating profit.

Key figures · 2025

Revenue
NOK 3.8m
Operating profit
NOK 1.0m
Equity
NOK 1.0m
Est. value
NOK 4.3m

Financial health · 2025

Liquidity
1.59
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
68.8%
Very good
Equity as a share of total capital

Who owns DARYAZ KLINIKK AS?

ARAM HASSAN FARES
DARYAZ KLINIKK AS
NOK 3.8m rev. · NOK 1.0m profit

DARYAZ KLINIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DARYAZ KLINIKK AS

Who owns DARYAZ KLINIKK AS?

ARAM HASSAN FARES is the largest registered owner, with 100.0%.

What is the revenue of DARYAZ KLINIKK AS?

DARYAZ KLINIKK AS had revenue of NOK 3.8m in 2025.

Who is the general manager of DARYAZ KLINIKK AS?

Aram Hassan Fares is registered as general manager of DARYAZ KLINIKK AS.

Where is DARYAZ KLINIKK AS based?

DARYAZ KLINIKK AS has its business address in Ålesund.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.