BIZTRAC BETA
Intermediation service activities for real estate activities

CORENS AS

Org. no. 921350031 Limited company (AS) Tromsø Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −163,000
Equity NOK 5.9m
Incorporated 2018
Share capital NOK 40,000

Signals

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

CORENS AS is registered as a limited company in Tromsø, Troms with organisation number 921350031. The business is classified under intermediation service activities for real estate activities (NACE 68.310). The company was incorporated in 2018. Registered share capital is NOK 40,000, divided into 20000 shares. The company's stated purpose is: “Investering i aksjer og andre selskap og det som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −163,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −163,000
Equity
NOK 5.9m
Est. value
NOK 5.4m

Financial health · 2024

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

Who owns CORENS AS?

DAAE STORMO AS
CORENS AS
NOK 0 rev. · NOK −163,000 profit

CORENS AS has 4 registered shareholders:

All shareholders and roles →

Which companies does CORENS AS own?

CORENS AS holds stakes in 9 companies:

See the full ownership structure →

Frequently asked questions about CORENS AS

Who owns CORENS AS?

DAAE STORMO AS is the largest registered owner, with 34.4%.

What is the revenue of CORENS AS?

CORENS AS had revenue of NOK 0 in 2024.

Who is the general manager of CORENS AS?

Tom Espen Daae Stormo is registered as general manager of CORENS AS.

Where is CORENS AS based?

CORENS AS has its business address in Tromsø.

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.