BIZTRAC BETA
Buying and selling of own real estate

NY ØKERN SENTRUM AS

Org. no. 833310712 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 20.1m
Operating profit NOK −9.9m
Equity NOK 893.1m
Incorporated 2024
Share capital NOK 1.0m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−9,9 mill kr).

NY ØKERN SENTRUM AS is registered as a limited company in Oslo, Oslo with organisation number 833310712. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2024. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Investering i fast eiendom og alt som herved står i forbindelse, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 20.1m in revenue and NOK −9.9m in operating profit.

Key figures · 2025

Revenue
NOK 20.1m
Operating profit
NOK −9.9m
Equity
NOK 893.1m
Est. value
NOK 641.3m

Financial health · 2025

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

Who owns NY ØKERN SENTRUM AS?

STOREBRAND ØKERN AS
NY ØKERN SENTRUM AS
NOK 20.1m rev. · NOK −9.9m profit

NY ØKERN SENTRUM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does NY ØKERN SENTRUM AS own?

NY ØKERN SENTRUM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about NY ØKERN SENTRUM AS

Who owns NY ØKERN SENTRUM AS?

STOREBRAND ØKERN AS is the largest registered owner, with 50.0%.

What is the revenue of NY ØKERN SENTRUM AS?

NY ØKERN SENTRUM AS had revenue of NOK 20.1m in 2025.

Where is NY ØKERN SENTRUM AS based?

NY ØKERN SENTRUM 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.