BIZTRAC BETA
Operation of sports facilities

LERKENDAL STADION AS

Org. no. 818985002 Limited company (AS) Trondheim Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 27.7m
Operating profit NOK 10.3m
Equity NOK 108.1m
Incorporated 2017
Share capital NOK 33.4m

Signals

1 flags
  • Nylig endring 2026-03-05 Aksjekapital registrert 2026-03-05.

LERKENDAL STADION AS is registered as a limited company in Trondheim, Trøndelag with organisation number 818985002. The business is classified under operation of sports facilities (NACE 93.110). The company was incorporated in 2017. Registered share capital is NOK 33.4m, divided into 38927 shares. The company's stated purpose is: “Oppføring, eie, drift og utleie av fast eiendom i Trondheim, samt virksomhet med tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 27.7m in revenue and NOK 10.3m in operating profit.

Key figures · 2024

Revenue
NOK 27.7m
Operating profit
NOK 10.3m
Equity
NOK 108.1m
Est. value
NOK 70.4m

Financial health · 2024

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

Who owns LERKENDAL STADION AS?

ROSENBORG BALLKLUB HOLDING AS
LERKENDAL STADION AS
NOK 27.7m rev. · NOK 10.3m profit

LERKENDAL STADION AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LERKENDAL STADION AS

Who owns LERKENDAL STADION AS?

ROSENBORG BALLKLUB HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LERKENDAL STADION AS?

LERKENDAL STADION AS had revenue of NOK 27.7m in 2024.

Who is the general manager of LERKENDAL STADION AS?

Tore Bjørseth Berdal is registered as general manager of LERKENDAL STADION AS.

Where is LERKENDAL STADION AS based?

LERKENDAL STADION 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.