BIZTRAC BETA
Other captive investment companies

NESØYA INVEST AS

Org. no. 928574636 Limited company (AS) Bærum Incorporated 1980 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −29,000
Equity NOK 1.1m
Incorporated 1980
Share capital NOK 1.1m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−29k kr).
  • Nylig endring 2026-06-01 Aksjekapital registrert 2026-06-01.

NESØYA INVEST AS is registered as a limited company in Bærum, Akershus with organisation number 928574636. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 1980. Registered share capital is NOK 1.1m, divided into 550 shares. The company's stated purpose is: “Handel og agenturvirksomhet og det som står i naturlig forbindelse med dette, samt eventuell deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −29,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −29,000
Equity
NOK 1.1m
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns NESØYA INVEST AS?

PER OLAV DAHL HEGGE
NESØYA INVEST AS
NOK 0 rev. · NOK −29,000 profit

NESØYA INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NESØYA INVEST AS own?

NESØYA INVEST AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about NESØYA INVEST AS

Who owns NESØYA INVEST AS?

PER OLAV DAHL HEGGE is the largest registered owner, with 100.0%.

What is the revenue of NESØYA INVEST AS?

NESØYA INVEST AS had revenue of NOK 0 in 2024.

Where is NESØYA INVEST AS based?

NESØYA INVEST AS has its business address in Høvik.

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.