BIZTRAC BETA
Other captive investment companies

BJØRNHOLMEN INVEST AS

Org. no. 899649532 Limited company (AS) Ålesund Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −18,000
Equity NOK 17.5m
Incorporated 2013
Share capital NOK 30,000

Signals

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

BJØRNHOLMEN INVEST AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 899649532. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investering i andre selskaper og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −18,000
Equity
NOK 17.5m
Est. value
NOK 14.8m

Financial health · 2024

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

Who owns BJØRNHOLMEN INVEST AS?

ØYVIND TØRLEN
BJØRNHOLMEN INVEST AS
NOK 0 rev. · NOK −18,000 profit

BJØRNHOLMEN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BJØRNHOLMEN INVEST AS own?

BJØRNHOLMEN INVEST AS holds stakes in 6 companies:

See the full ownership structure →

Frequently asked questions about BJØRNHOLMEN INVEST AS

Who owns BJØRNHOLMEN INVEST AS?

ØYVIND TØRLEN is the largest registered owner, with 100.0%.

What is the revenue of BJØRNHOLMEN INVEST AS?

BJØRNHOLMEN INVEST AS had revenue of NOK 0 in 2024.

Where is BJØRNHOLMEN INVEST AS based?

BJØRNHOLMEN INVEST AS has its business address in Ålesund.

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.