BIZTRAC BETA
Operation of sports facilities

BJØRKBAKKEN AS

Org. no. 925597279 Limited company (AS) Stjørdal Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 723,000
Operating profit NOK 102,000
Equity NOK 9.7m
Incorporated 2020
Share capital NOK 10.0m

BJØRKBAKKEN AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 925597279. The business is classified under operation of sports facilities (NACE 93.110). The company was incorporated in 2020. Registered share capital is NOK 10.0m, divided into 6 shares. The company's stated purpose is: “Bygge, drifte å leie ut aktuelt anlegg for idrett og friluftsliv i Bjørkbakken. Selskapet er uten eget økonomisk formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 723,000 in revenue and NOK 102,000 in operating profit.

Key figures · 2024

Revenue
NOK 723,000
Operating profit
NOK 102,000
Equity
NOK 9.7m
Est. value
NOK 4.6m

Financial health · 2024

Liquidity
0.09
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 BJØRKBAKKEN AS?

STJØRDALS-BLINK IL
BJØRKBAKKEN AS
NOK 723,000 rev. · NOK 102,000 profit

BJØRKBAKKEN AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BJØRKBAKKEN AS own?

BJØRKBAKKEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BJØRKBAKKEN AS

Who owns BJØRKBAKKEN AS?

STJØRDALS-BLINK IL is the largest registered owner, with 50.0%.

What is the revenue of BJØRKBAKKEN AS?

BJØRKBAKKEN AS had revenue of NOK 723,000 in 2024.

Who is the general manager of BJØRKBAKKEN AS?

Magnus Berger Skjøstad is registered as general manager of BJØRKBAKKEN AS.

Where is BJØRKBAKKEN AS based?

BJØRKBAKKEN AS has its business address in Stjørdal.

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.