BIZTRAC BETA
Other captive investment companies

OLAV EGELAND INVEST AS

Org. no. 989126288 Limited company (AS) Trondheim Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 718,000
Operating profit NOK 656,000
Equity NOK 8.1m
Incorporated 2005
Share capital NOK 100,000

OLAV EGELAND INVEST AS is registered as a limited company in Trondheim, Trøndelag with organisation number 989126288. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Eierskap i Marine Cybernetics AS”. The most recent filed accounts, for the 2024 financial year, show NOK 718,000 in revenue and NOK 656,000 in operating profit.

Key figures · 2024

Revenue
NOK 718,000
Operating profit
NOK 656,000
Equity
NOK 8.1m
Est. value
NOK 6.4m

Financial health · 2024

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

Who owns OLAV EGELAND INVEST AS?

OLAV EGELAND
OLAV EGELAND INVEST AS
NOK 718,000 rev. · NOK 656,000 profit

OLAV EGELAND INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OLAV EGELAND INVEST AS own?

OLAV EGELAND INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about OLAV EGELAND INVEST AS

Who owns OLAV EGELAND INVEST AS?

OLAV EGELAND is the largest registered owner, with 100.0%.

What is the revenue of OLAV EGELAND INVEST AS?

OLAV EGELAND INVEST AS had revenue of NOK 718,000 in 2024.

Who is the general manager of OLAV EGELAND INVEST AS?

Olav Egeland is registered as general manager of OLAV EGELAND INVEST AS.

Where is OLAV EGELAND INVEST AS based?

OLAV EGELAND INVEST AS has its business address in Trondheim.

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.