BIZTRAC BETA
Restaurant activities

NESTEN SOM HJEMME AS

Org. no. 929553500 Limited company (AS) Flå Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 4.8m
Operating profit NOK 112,000
Equity NOK 52,000
Incorporated 2022
Employees 12
Share capital NOK 30,000

NESTEN SOM HJEMME AS is registered as a limited company in Flå, Buskerud with organisation number 929553500. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2022 and has 12 registered employees. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Drift av restaurant, kafe og catering cateringvirksomhet, samt salg av andre varer som naturlig tilhører driften.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.8m in revenue and NOK 112,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.8m
Operating profit
NOK 112,000
Equity
NOK 52,000
Est. value
NOK 419,000

Financial health · 2024

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

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

Who owns NESTEN SOM HJEMME AS?

NESTEN SOM HJEMME HOLDING AS
NESTEN SOM HJEMME AS
NOK 4.8m rev. · NOK 112,000 profit

NESTEN SOM HJEMME AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NESTEN SOM HJEMME AS

Who owns NESTEN SOM HJEMME AS?

NESTEN SOM HJEMME HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of NESTEN SOM HJEMME AS?

NESTEN SOM HJEMME AS had revenue of NOK 4.8m in 2024.

Who is the general manager of NESTEN SOM HJEMME AS?

Kristin Dahle is registered as general manager of NESTEN SOM HJEMME AS.

Where is NESTEN SOM HJEMME AS based?

NESTEN SOM HJEMME AS has its business address in Flå.

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.