BIZTRAC BETA
Operation of sports facilities

BROKKE ALPINSENTER AS

Org. no. 916538227 Limited company (AS) Valle Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 9.2m
Operating profit NOK −2.6m
Equity NOK 856,000
Incorporated 2015
Employees 42
Share capital NOK 830,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,6 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BROKKE ALPINSENTER AS is registered as a limited company in Valle, Agder with organisation number 916538227. The business is classified under operation of sports facilities (NACE 93.110). The company was incorporated in 2015 and has 42 registered employees. Registered share capital is NOK 830,000, divided into 100 shares. The company's stated purpose is: “Drift av alpinanlegg, samt alt som naturlig hører med til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.2m in revenue and NOK −2.6m in operating profit.

Key figures · 2024

Revenue
NOK 9.2m
Operating profit
NOK −2.6m
Equity
NOK 856,000
Est. value
NOK 5.3m

Financial health · 2024

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

Who owns BROKKE ALPINSENTER AS?

BROKKE ALPINANLEGG AS
BROKKE ALPINSENTER AS
NOK 9.2m rev. · NOK −2.6m profit

BROKKE ALPINSENTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BROKKE ALPINSENTER AS

Who owns BROKKE ALPINSENTER AS?

BROKKE ALPINANLEGG AS is the largest registered owner, with 100.0%.

What is the revenue of BROKKE ALPINSENTER AS?

BROKKE ALPINSENTER AS had revenue of NOK 9.2m in 2024.

Where is BROKKE ALPINSENTER AS based?

BROKKE ALPINSENTER AS has its business address in Rysstad.

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.