biztrac. BETA
COMPANY REGISTER PROFILE
922607273 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

DEG 18 DRIFT AS

Org. no. 922607273 Limited company (AS) Oslo Incorporated 2019 Active
Revenue 2025 NOK 14.4m
Operating profit NOK −1.1m
Equity NOK 2.6m
Incorporated 2019
Employees 14
Share capital NOK 1.0m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,1 mill kr).

DEG 18 DRIFT AS is registered as a limited company in Oslo, Oslo with organisation number 922607273. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2019 and has 14 registered employees. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Restaurantvirksomhet, samt hva hermed står i naturlig forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 14.4m in revenue and NOK −1.1m in operating profit.

Key figures · 2025

Revenue
NOK 14.4m
▼ −11 %
Operating profit
NOK −1.1m
▼ −171 %
Equity
NOK 2.6m
▼ −26 %
Est. value
NOK 10.8m

Financial health · 2025

Liquidity
1.06
Satisfactory
Current assets ÷ current liabilities
Profitability
-13.4%
Not satisfactory
Return on total assets
Solidity
38.0%
Good
Equity as a share of total capital

Who owns DEG 18 DRIFT AS?

DEG 18 DRIFT AS
NOK 14.4m rev. · NOK −1.1m profit

DEG 18 DRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DEG 18 DRIFT AS

Who owns DEG 18 DRIFT AS?

TRØFFEL AS is the largest registered owner, with 100.0%.

What is the revenue of DEG 18 DRIFT AS?

DEG 18 DRIFT AS had revenue of NOK 14.4m in 2025.

Who is the general manager of DEG 18 DRIFT AS?

Eirik Strøm Lillebø is registered as general manager of DEG 18 DRIFT AS.

Where is DEG 18 DRIFT AS based?

DEG 18 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 03.10.2026.

Report a problem

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