BIZTRAC BETA
COMPANY REGISTER PROFILE
992464658 ORG. NO. 2023 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Buying and selling of own real estate

SIMCORP INVEST AS

Org. no. 992464658 Limited company (AS) Oslo Incorporated 2008 Active
Ownership graph ↗
Operating profit NOK −24,000
Equity NOK −1.0m
Incorporated 2008
Share capital NOK 400,000

Signals

4 flags
  • Negativ egenkapital 2023 Bokført egenkapital er negativ (−1,0 mill kr).
  • Driftsunderskudd 2023 Siste driftsresultat er negativt (−24k kr).
  • Utdatert regnskap Siste registrerte regnskap er fra 2023.
  • Nylig endring 2026-06-23 Under avvikling registrert 2026-06-23.

SIMCORP INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 992464658. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2008. Registered share capital is NOK 400,000, divided into 100000 shares. The company's stated purpose is: “Investeringer i verdipapirer, kjøp, salg og utleie av fast eiendom og annet som naturlig står i forbindelse med dette - herunder å delta i andre selskaper.”.

Key figures · 2023

Operating profit
NOK −24,000
Equity
NOK −1.0m

Financial health · 2023

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

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

Who owns SIMCORP INVEST AS?

No shareholders are registered for SIMCORP INVEST AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about SIMCORP INVEST AS

Who is the general manager of SIMCORP INVEST AS?

Simen Stensrud is registered as general manager of SIMCORP INVEST AS.

Where is SIMCORP INVEST AS based?

SIMCORP 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.