biztrac. BETA
COMPANY REGISTER PROFILE
932539187 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

HELGELANDSMOEN UTVIKLING AS

Org. no. 932539187 Limited company (AS) Hole Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 432,000
Operating profit NOK −84,000
Equity NOK 3.6m
Incorporated 2023
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−84k kr).

HELGELANDSMOEN UTVIKLING AS is registered as a limited company in Hole, Buskerud with organisation number 932539187. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 200,000, divided into 1000 shares. The company's stated purpose is: “Å investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 432,000 in revenue and NOK −84,000 in operating profit.

Key figures · 2025

Revenue
NOK 432,000
▼ −6 %
Operating profit
NOK −84,000
▼ −127 %
Equity
NOK 3.6m
▼ −2 %
Est. value
NOK 2.6m

Financial health · 2025

Liquidity
14.81
Very good
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
38.8%
Good
Equity as a share of total capital

Who owns HELGELANDSMOEN UTVIKLING AS?

HELGELANDSMOEN UTVIKLING AS has 9 registered shareholders:

All shareholders and roles →

Frequently asked questions about HELGELANDSMOEN UTVIKLING AS

Who owns HELGELANDSMOEN UTVIKLING AS?

JK EIENDOM AS is the largest registered owner, with 53.6%.

What is the revenue of HELGELANDSMOEN UTVIKLING AS?

HELGELANDSMOEN UTVIKLING AS had revenue of NOK 432,000 in 2025.

Where is HELGELANDSMOEN UTVIKLING AS based?

HELGELANDSMOEN UTVIKLING AS has its business address in Røyse.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.