BIZTRAC BETA
Restaurant activities

VERTSHUSET RESTAURANT AS

Org. no. 994284231 Limited company (AS) Nome Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 3.8m
Operating profit NOK 229,000
Equity NOK 179,000
Incorporated 2009
Employees 6
Share capital NOK 100,000

VERTSHUSET RESTAURANT AS is registered as a limited company in Nome, Telemark with organisation number 994284231. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2009 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift av restaurant og kafeer, og eie aksjer i andre selskaper samt finansiering og annen økonomisk virksomhet som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.8m in revenue and NOK 229,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.8m
Operating profit
NOK 229,000
Equity
NOK 179,000
Est. value
NOK 944,000

Financial health · 2024

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

Who owns VERTSHUSET RESTAURANT AS?

XIAOLAN CHEN
VERTSHUSET RESTAURANT AS
NOK 3.8m rev. · NOK 229,000 profit

VERTSHUSET RESTAURANT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VERTSHUSET RESTAURANT AS

Who owns VERTSHUSET RESTAURANT AS?

XIAOLAN CHEN is the largest registered owner, with 50.0%.

What is the revenue of VERTSHUSET RESTAURANT AS?

VERTSHUSET RESTAURANT AS had revenue of NOK 3.8m in 2024.

Who is the general manager of VERTSHUSET RESTAURANT AS?

Zeng Ning Feng is registered as general manager of VERTSHUSET RESTAURANT AS.

Where is VERTSHUSET RESTAURANT AS based?

VERTSHUSET RESTAURANT AS has its business address in Ulefoss.

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.