BIZTRAC BETA
Restaurant activities

BISLETT KEBAB HOUSE DRIFT AS

Org. no. 918837841 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 189.7m
Operating profit NOK 17.5m
Equity NOK 8.1m
Incorporated 2017
Employees 142
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BISLETT KEBAB HOUSE DRIFT AS is registered as a limited company in Oslo, Oslo with organisation number 918837841. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2017 and has 142 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Restaurant- og bevertningsvirksomhet og det som naturlig hører til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 189.7m in revenue and NOK 17.5m in operating profit.

Key figures · 2024

Revenue
NOK 189.7m
Operating profit
NOK 17.5m
Equity
NOK 8.1m
Est. value
NOK 69.6m

Financial health · 2024

Liquidity
0.92
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
13.5%
Satisfactory
Equity as a share of total capital

Who owns BISLETT KEBAB HOUSE DRIFT AS?

BISLETT KEBAB HOUSE AS
BISLETT KEBAB HOUSE DRIFT AS
NOK 189.7m rev. · NOK 17.5m profit

BISLETT KEBAB HOUSE DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BISLETT KEBAB HOUSE DRIFT AS

Who owns BISLETT KEBAB HOUSE DRIFT AS?

BISLETT KEBAB HOUSE AS is the largest registered owner, with 100.0%.

What is the revenue of BISLETT KEBAB HOUSE DRIFT AS?

BISLETT KEBAB HOUSE DRIFT AS had revenue of NOK 189.7m in 2024.

Where is BISLETT KEBAB HOUSE DRIFT AS based?

BISLETT KEBAB HOUSE DRIFT AS has its business address in Oslo.

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.