BIZTRAC BETA
Other technical consultancy

SIMEN ANDERSEN INVEST AS

Org. no. 926695916 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 33,000
Operating profit NOK 515
Equity NOK 70,000
Incorporated 2021
Share capital NOK 30,000

SIMEN ANDERSEN INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 926695916. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investere egenkapital i andre selskap og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 33,000 in revenue and NOK 515 in operating profit.

Key figures · 2025

Revenue
NOK 33,000
Operating profit
NOK 515
Equity
NOK 70,000
Est. value
NOK 38,000

Financial health · 2025

Liquidity
0.22
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
52.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SIMEN ANDERSEN INVEST AS?

SIMEN SANNERUD ANDERSEN
SIMEN ANDERSEN INVEST AS
NOK 33,000 rev. · NOK 515 profit

SIMEN ANDERSEN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SIMEN ANDERSEN INVEST AS own?

SIMEN ANDERSEN INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SIMEN ANDERSEN INVEST AS

Who owns SIMEN ANDERSEN INVEST AS?

SIMEN SANNERUD ANDERSEN is the largest registered owner, with 100.0%.

What is the revenue of SIMEN ANDERSEN INVEST AS?

SIMEN ANDERSEN INVEST AS had revenue of NOK 33,000 in 2025.

Where is SIMEN ANDERSEN INVEST AS based?

SIMEN ANDERSEN 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.