BIZTRAC BETA
Restaurant activities

DAMASKUS KEBAB AS

Org. no. 922033870 Limited company (AS) Tromsø Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 777,000
Operating profit NOK 57,000
Equity NOK 154,000
Incorporated 2018
Share capital NOK 30,000

DAMASKUS KEBAB AS is registered as a limited company in Tromsø, Troms with organisation number 922033870. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg av gatekjøkkenmat, samt andre tjenester som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 777,000 in revenue and NOK 57,000 in operating profit.

Key figures · 2025

Revenue
NOK 777,000
Operating profit
NOK 57,000
Equity
NOK 154,000
Est. value
NOK 310,000

Financial health · 2025

Liquidity
1.13
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
68.2%
Very good
Equity as a share of total capital

Who owns DAMASKUS KEBAB AS?

KAMAL ESSOULIMANI
DAMASKUS KEBAB AS
NOK 777,000 rev. · NOK 57,000 profit

DAMASKUS KEBAB AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DAMASKUS KEBAB AS

Who owns DAMASKUS KEBAB AS?

KAMAL ESSOULIMANI is the largest registered owner, with 100.0%.

What is the revenue of DAMASKUS KEBAB AS?

DAMASKUS KEBAB AS had revenue of NOK 777,000 in 2025.

Who is the general manager of DAMASKUS KEBAB AS?

Ikram Oumansour is registered as general manager of DAMASKUS KEBAB AS.

Where is DAMASKUS KEBAB AS based?

DAMASKUS KEBAB AS has its business address in Tromsdalen.

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.