biztrac. BETA
COMPANY REGISTER PROFILE
959662932 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

STAVANGER STORSENTER AS

Org. no. 959662932 Limited company (AS) Surnadal Incorporated 1990 Active
Ownership graph ↗
Revenue 2025 NOK 39.5m
Operating profit NOK 21.8m
Equity NOK 195.2m
Incorporated 1990
Share capital NOK 3.9m

STAVANGER STORSENTER AS is registered as a limited company in Surnadal, Møre og Romsdal with organisation number 959662932. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1990. Registered share capital is NOK 3.9m, divided into 6000 shares. The company's stated purpose is: “Å erverve fast eiendom for utvikling, utleie og hva hermed står i forbindelse, samt delta i andre selskaper med tilsvarende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 39.5m in revenue and NOK 21.8m in operating profit.

Former names: BØHLER AS

Key figures · 2025

Revenue
NOK 39.5m
▼ −0 %
Operating profit
NOK 21.8m
▼ −6 %
Equity
NOK 195.2m
▼ −3 %
Est. value
NOK 187.8m

Financial health · 2025

Liquidity
1.29
Satisfactory
Current assets ÷ current liabilities
Profitability
1.8%
Weak
Return on total assets
Solidity
50.6%
Very good
Equity as a share of total capital

Who owns STAVANGER STORSENTER AS?

STAVANGER STORSENTER AS
NOK 39.5m rev. · NOK 21.8m profit

STAVANGER STORSENTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STAVANGER STORSENTER AS

Who owns STAVANGER STORSENTER AS?

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

What is the revenue of STAVANGER STORSENTER AS?

STAVANGER STORSENTER AS had revenue of NOK 39.5m in 2025.

Where is STAVANGER STORSENTER AS based?

STAVANGER STORSENTER AS has its business address in Surnadal.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.