BIZTRAC BETA
Rental and operating of own or leased real estate

OLAVSHALLEN AS

Org. no. 951615390 Limited company (AS) Trondheim Incorporated 1988 Active
Ownership graph ↗
Revenue 2024 NOK 51.6m
Operating profit NOK 3.3m
Equity NOK 5.0m
Incorporated 1988
Employees 26
Share capital NOK 2.0m

OLAVSHALLEN AS is registered as a limited company in Trondheim, Trøndelag with organisation number 951615390. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1988 and has 26 registered employees. Registered share capital is NOK 2.0m. The company's stated purpose is: “Er gjennom administrasjon av Olavshallen AS sine eiendommer å fremme midtnorsk musikk- og kulturliv ved å eie, forvalte og leie ut sine eiendommer og lokaler primært til kulturelle formål, samt private og offentlige arrangement.”. The most recent filed accounts, for the 2024 financial year, show NOK 51.6m in revenue and NOK 3.3m in operating profit.

Key figures · 2024

Revenue
NOK 51.6m
Operating profit
NOK 3.3m
Equity
NOK 5.0m
Est. value
NOK 9.8m

Financial health · 2024

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

Who owns OLAVSHALLEN AS?

TRONDHEIM KOMMUNE
OLAVSHALLEN AS
NOK 51.6m rev. · NOK 3.3m profit

OLAVSHALLEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OLAVSHALLEN AS

Who owns OLAVSHALLEN AS?

TRONDHEIM KOMMUNE is the largest registered owner, with 100.0%.

What is the revenue of OLAVSHALLEN AS?

OLAVSHALLEN AS had revenue of NOK 51.6m in 2024.

Who is the general manager of OLAVSHALLEN AS?

Ann Elisabeth Wedø is registered as general manager of OLAVSHALLEN AS.

Where is OLAVSHALLEN AS based?

OLAVSHALLEN AS has its business address in Trondheim.

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.