BIZTRAC BETA
Rental and operating of own or leased real estate

ØVRE KRONA II AS

Org. no. 922292434 Limited company (AS) Ålesund Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK 1.1m
Equity NOK 5.7m
Incorporated 2019
Share capital NOK 1.0m

ØVRE KRONA II AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 922292434. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 1.0m, divided into 20000 shares. The company's stated purpose is: “Kjøp, salg, utleie, forvaltning, drift og utbygging av fast eiendom, medvirke i andre selskaper innen samme virksomhet, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK 1.1m
Equity
NOK 5.7m
Est. value
NOK 5.6m

Financial health · 2024

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

Who owns ØVRE KRONA II AS?

MØRE NÆRINGSBYGG AS
ØVRE KRONA II AS
NOK 1.8m rev. · NOK 1.1m profit

ØVRE KRONA II AS has 1 registered shareholder:

All shareholders and roles →

Group structure

ØVRE KRONA II AS er morselskap for 4 datterselskaper:

Frequently asked questions about ØVRE KRONA II AS

Who owns ØVRE KRONA II AS?

MØRE NÆRINGSBYGG AS is the largest registered owner, with 100.0%.

What is the revenue of ØVRE KRONA II AS?

ØVRE KRONA II AS had revenue of NOK 1.8m in 2024.

Who is the general manager of ØVRE KRONA II AS?

Knut-Arild Emblem is registered as general manager of ØVRE KRONA II AS.

Where is ØVRE KRONA II AS based?

ØVRE KRONA II AS has its business address in Ålesund.

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.