BIZTRAC BETA
Restaurant activities

DILEMEN RESTAURANT AS

Org. no. 933175146 Limited company (AS) Stjørdal Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 4.3m
Operating profit NOK 53,000
Equity NOK 72,000
Incorporated 2024
Employees 17
Share capital NOK 30,000

DILEMEN RESTAURANT AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 933175146. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2024 and has 17 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drift restaurant og andre produkter som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.3m in revenue and NOK 53,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.3m
Operating profit
NOK 53,000
Equity
NOK 72,000
Est. value
NOK 285,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns DILEMEN RESTAURANT AS?

LILLIANN DVERGSDAL HAUGEN
DILEMEN RESTAURANT AS
NOK 4.3m rev. · NOK 53,000 profit

DILEMEN RESTAURANT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about DILEMEN RESTAURANT AS

Who owns DILEMEN RESTAURANT AS?

LILLIANN DVERGSDAL HAUGEN is the largest registered owner, with 50.0%.

What is the revenue of DILEMEN RESTAURANT AS?

DILEMEN RESTAURANT AS had revenue of NOK 4.3m in 2024.

Who is the general manager of DILEMEN RESTAURANT AS?

Lilliann Dvergsdal Haugen is registered as general manager of DILEMEN RESTAURANT AS.

Where is DILEMEN RESTAURANT AS based?

DILEMEN RESTAURANT AS has its business address in Stjørdal.

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.