BIZTRAC BETA
Activities of amusement parks and theme parks

NEDSTRAND UTVIKLING AS

Org. no. 911630621 Limited company (AS) Vindafjord Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 469,000
Operating profit NOK −761,000
Equity NOK 7.3m
Incorporated 2013
Share capital NOK 9.7m

Signals

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

NEDSTRAND UTVIKLING AS is registered as a limited company in Vindafjord, Rogaland with organisation number 911630621. The business is classified under activities of amusement parks and theme parks (NACE 93.210). The company was incorporated in 2013. Registered share capital is NOK 9.7m, divided into 9716970 shares. The company's stated purpose is: “Å utvikle og drifte et reiselivsanlegg, samt salg av hytter og båtplasser og hva hermed står i forbindelse, herunder å kunne delta i foretak som driver tilsvarende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 469,000 in revenue and NOK −761,000 in operating profit.

Key figures · 2024

Revenue
NOK 469,000
Operating profit
NOK −761,000
Equity
NOK 7.3m
Est. value
NOK 9.2m

Financial health · 2024

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

Who owns NEDSTRAND UTVIKLING AS?

BERGSHAGEN INVEST AS
NEDSTRAND UTVIKLING AS
NOK 469,000 rev. · NOK −761,000 profit

NEDSTRAND UTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NEDSTRAND UTVIKLING AS

Who owns NEDSTRAND UTVIKLING AS?

BERGSHAGEN INVEST AS is the largest registered owner, with 90.1%.

What is the revenue of NEDSTRAND UTVIKLING AS?

NEDSTRAND UTVIKLING AS had revenue of NOK 469,000 in 2024.

Where is NEDSTRAND UTVIKLING AS based?

NEDSTRAND UTVIKLING AS has its business address in Ølensvåg.

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.