BIZTRAC BETA
Rental and operating of own or leased real estate

ØLEN SENTRUMSUTVIKLING AS

Org. no. 915267300 Limited company (AS) Haugesund Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 5.3m
Operating profit NOK 2.8m
Equity NOK 13.4m
Incorporated 2015
Share capital NOK 14.7m

ØLEN SENTRUMSUTVIKLING AS is registered as a limited company in Haugesund, Rogaland with organisation number 915267300. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 14.7m, divided into 8700 shares. The company's stated purpose is: “Kjøpe, eie, utvikle, forvalte og selge eiendommer, samt delta i andre selskaper med hvilket som helst formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.3m in revenue and NOK 2.8m in operating profit.

Key figures · 2024

Revenue
NOK 5.3m
Operating profit
NOK 2.8m
Equity
NOK 13.4m
Est. value
NOK 13.3m

Financial health · 2024

Liquidity
0.12
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
17.3%
Satisfactory
Equity as a share of total capital

Who owns ØLEN SENTRUMSUTVIKLING AS?

NOKUS AS
ØLEN SENTRUMSUTVIKLING AS
NOK 5.3m rev. · NOK 2.8m profit

ØLEN SENTRUMSUTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ØLEN SENTRUMSUTVIKLING AS

Who owns ØLEN SENTRUMSUTVIKLING AS?

NOKUS AS is the largest registered owner, with 50.0%.

What is the revenue of ØLEN SENTRUMSUTVIKLING AS?

ØLEN SENTRUMSUTVIKLING AS had revenue of NOK 5.3m in 2024.

Who is the general manager of ØLEN SENTRUMSUTVIKLING AS?

Tore Lilleland is registered as general manager of ØLEN SENTRUMSUTVIKLING AS.

Where is ØLEN SENTRUMSUTVIKLING AS based?

ØLEN SENTRUMSUTVIKLING AS has its business address in Haugesund.

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.