BIZTRAC BETA
Restaurant activities

HEV MOSETERTOPPEN AS

Org. no. 834271702 Limited company (AS) Ringebu Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 10.7m
Operating profit NOK 144,000
Equity NOK 51,000
Incorporated 2024
Employees 20
Share capital NOK 200,000

HEV MOSETERTOPPEN AS is registered as a limited company in Ringebu, Innlandet with organisation number 834271702. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2024 and has 20 registered employees. Registered share capital is NOK 200,000, divided into 20000 shares. The company's stated purpose is: “Drive restaurantvirksomhet på Mosetertoppen Skistadion i Hafjell og aktivitet som faller naturlig sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 10.7m in revenue and NOK 144,000 in operating profit.

Key figures · 2024

Revenue
NOK 10.7m
Operating profit
NOK 144,000
Equity
NOK 51,000
Est. value
NOK 697,000

Financial health · 2025

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

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

Who owns HEV MOSETERTOPPEN AS?

HEV HEV AS
HEV MOSETERTOPPEN AS
NOK 10.7m rev. · NOK 144,000 profit

HEV MOSETERTOPPEN AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about HEV MOSETERTOPPEN AS

Who owns HEV MOSETERTOPPEN AS?

HEV HEV AS is the largest registered owner, with 40.0%.

What is the revenue of HEV MOSETERTOPPEN AS?

HEV MOSETERTOPPEN AS had revenue of NOK 10.7m in 2024.

Who is the general manager of HEV MOSETERTOPPEN AS?

Silje Flatmoen is registered as general manager of HEV MOSETERTOPPEN AS.

Where is HEV MOSETERTOPPEN AS based?

HEV MOSETERTOPPEN AS has its business address in Ringebu.

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.