BIZTRAC BETA
Other captive investment companies

SIMONSEN INVEST AS

Org. no. 913884698 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 18,000
Operating profit NOK −153,000
Equity NOK 16.0m
Incorporated 2014
Share capital NOK 30,000

Signals

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

SIMONSEN INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 913884698. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investeringer i ulike formuesobjekter, deltakelse i og administrasjon av andre selskaper samt annen virksomhet i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 18,000 in revenue and NOK −153,000 in operating profit.

Key figures · 2024

Revenue
NOK 18,000
Operating profit
NOK −153,000
Equity
NOK 16.0m
Est. value
NOK 8.8m

Financial health · 2024

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

Who owns SIMONSEN INVEST AS?

BJØRN SIMONSEN
SIMONSEN INVEST AS
NOK 18,000 rev. · NOK −153,000 profit

SIMONSEN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SIMONSEN INVEST AS own?

SIMONSEN INVEST AS holds stakes in 26 companies:

See the full ownership structure →

Frequently asked questions about SIMONSEN INVEST AS

Who owns SIMONSEN INVEST AS?

BJØRN SIMONSEN is the largest registered owner, with 100.0%.

What is the revenue of SIMONSEN INVEST AS?

SIMONSEN INVEST AS had revenue of NOK 18,000 in 2024.

Where is SIMONSEN INVEST AS based?

SIMONSEN INVEST AS has its business address in Oslo.

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.