BIZTRAC BETA
Operation of sports facilities

ROSENBORG BALLKLUB HOLDING AS

Org. no. 925542253 Limited company (AS) Trondheim Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −8,000
Equity NOK 39.0m
Incorporated 2020
Share capital NOK 1.2m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−8k kr).

ROSENBORG BALLKLUB HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 925542253. The business is classified under operation of sports facilities (NACE 93.110). The company was incorporated in 2020. Registered share capital is NOK 1.2m, divided into 30 shares. The company's stated purpose is: “Investering i næringsvirksomhet, herunder aksjer og andeler, samt deltagelse i andre selskaper med lignende virksomhet.”.

Key figures · 2024

Operating profit
NOK −8,000
Equity
NOK 39.0m
Est. value
NOK 48.8m

Financial health · 2024

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

Who owns ROSENBORG BALLKLUB HOLDING AS?

ROSENBORG BALLKLUB
ROSENBORG BALLKLUB HOLDING AS
· NOK −8,000 profit

ROSENBORG BALLKLUB HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ROSENBORG BALLKLUB HOLDING AS own?

ROSENBORG BALLKLUB HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about ROSENBORG BALLKLUB HOLDING AS

Who owns ROSENBORG BALLKLUB HOLDING AS?

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

Who is the general manager of ROSENBORG BALLKLUB HOLDING AS?

Tore Bjørseth Berdal is registered as general manager of ROSENBORG BALLKLUB HOLDING AS.

Where is ROSENBORG BALLKLUB HOLDING AS based?

ROSENBORG BALLKLUB HOLDING 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.