BIZTRAC BETA
Rental and operating of own or leased real estate

KROKEN EIENDOM ÅLESUND AS

Org. no. 998819342 Limited company (AS) Rauma Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK 1.3m
Equity NOK 5.4m
Incorporated 2012
Share capital NOK 44,000

KROKEN EIENDOM ÅLESUND AS is registered as a limited company in Rauma, Møre og Romsdal with organisation number 998819342. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 44,000, divided into 30 shares. The company's stated purpose is: “Eie og forvalte fast eiendom samt alt som står i forbindelse med dette, herunder deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK 1.3m in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK 1.3m
Equity
NOK 5.4m
Est. value
NOK 6.3m

Financial health · 2024

Liquidity
0.70
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
39.1%
Good
Equity as a share of total capital

Who owns KROKEN EIENDOM ÅLESUND AS?

KROKEN-EIENDOM AS
KROKEN EIENDOM ÅLESUND AS
NOK 1.8m rev. · NOK 1.3m profit

KROKEN EIENDOM ÅLESUND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KROKEN EIENDOM ÅLESUND AS

Who owns KROKEN EIENDOM ÅLESUND AS?

KROKEN-EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of KROKEN EIENDOM ÅLESUND AS?

KROKEN EIENDOM ÅLESUND AS had revenue of NOK 1.8m in 2024.

Who is the general manager of KROKEN EIENDOM ÅLESUND AS?

Lars Kroken is registered as general manager of KROKEN EIENDOM ÅLESUND AS.

Where is KROKEN EIENDOM ÅLESUND AS based?

KROKEN EIENDOM ÅLESUND AS has its business address in Åndalsnes.

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.