BIZTRAC BETA
Rental and operating of own or leased real estate

STIMIC INVEST AS

Org. no. 924582286 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 459,000
Incorporated 2020
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−5k kr).

STIMIC INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 924582286. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 10 shares. The company's stated purpose is: “Investering i eiendom og verdipapirer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 459,000
Est. value
NOK 353,000

Financial health · 2025

Liquidity
-178.95
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
33.1%
Good
Equity as a share of total capital

Who owns STIMIC INVEST AS?

STIAN MICHAELSEN
STIMIC INVEST AS
NOK 0 rev. · NOK −5,000 profit

STIMIC INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STIMIC INVEST AS own?

STIMIC INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STIMIC INVEST AS

Who owns STIMIC INVEST AS?

STIAN MICHAELSEN is the largest registered owner, with 100.0%.

What is the revenue of STIMIC INVEST AS?

STIMIC INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of STIMIC INVEST AS?

Stian Michaelsen is registered as general manager of STIMIC INVEST AS.

Where is STIMIC INVEST AS based?

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