BIZTRAC BETA
Development of building projects

MOSETERTOPPEN TOPYARD AS

Org. no. 929207521 Limited company (AS) Øyer Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −69,000
Equity NOK 3.8m
Incorporated 2022
Share capital NOK 2.0m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−69k kr).

MOSETERTOPPEN TOPYARD AS is registered as a limited company in Øyer, Innlandet with organisation number 929207521. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2022. Registered share capital is NOK 2.0m, divided into 1000 shares. The company's stated purpose is: “Kjøp, utvikling og salg av fast eiendom og det som naturlig står i forbindelse med det.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −69,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −69,000
Equity
NOK 3.8m
Est. value
NOK 3.5m

Financial health · 2024

Liquidity
1251.76
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
99.9%
Very good
Equity as a share of total capital

Who owns MOSETERTOPPEN TOPYARD AS?

MOSETERTOPPEN HAFJELL AS
MOSETERTOPPEN TOPYARD AS
NOK 0 rev. · NOK −69,000 profit

MOSETERTOPPEN TOPYARD AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MOSETERTOPPEN TOPYARD AS

Who owns MOSETERTOPPEN TOPYARD AS?

MOSETERTOPPEN HAFJELL AS is the largest registered owner, with 50.0%.

What is the revenue of MOSETERTOPPEN TOPYARD AS?

MOSETERTOPPEN TOPYARD AS had revenue of NOK 0 in 2024.

Who is the general manager of MOSETERTOPPEN TOPYARD AS?

Roar Øien is registered as general manager of MOSETERTOPPEN TOPYARD AS.

Where is MOSETERTOPPEN TOPYARD AS based?

MOSETERTOPPEN TOPYARD AS has its business address in Øyer.

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.