BIZTRAC BETA
Rental and operating of own or leased real estate

BJØRKELANGEN TORG AS

Org. no. 988808423 Limited company (AS) Surnadal Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 16.7m
Operating profit NOK 5.4m
Equity NOK 70.7m
Incorporated 2005
Share capital NOK 4.6m

BJØRKELANGEN TORG AS is registered as a limited company in Surnadal, Møre og Romsdal with organisation number 988808423. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 4.6m, divided into 4600 shares. The company's stated purpose is: “Anskaffelse, drift, utleie og salg av fast eiendom, samt hva som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 16.7m in revenue and NOK 5.4m in operating profit.

Key figures · 2024

Revenue
NOK 16.7m
Operating profit
NOK 5.4m
Equity
NOK 70.7m
Est. value
NOK 56.8m

Financial health · 2024

Liquidity
0.22
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
19.9%
Good
Equity as a share of total capital

Who owns BJØRKELANGEN TORG AS?

COOP ØST SA
BJØRKELANGEN TORG AS
NOK 16.7m rev. · NOK 5.4m profit

BJØRKELANGEN TORG AS has 4 registered shareholders:

All shareholders and roles →

Which companies does BJØRKELANGEN TORG AS own?

BJØRKELANGEN TORG AS holds a stake in 1 company:

See the full ownership structure →

Group structure

BJØRKELANGEN TORG AS er morselskap for 1 datterselskap:

Frequently asked questions about BJØRKELANGEN TORG AS

Who owns BJØRKELANGEN TORG AS?

COOP ØST SA is the largest registered owner, with 43.5%.

What is the revenue of BJØRKELANGEN TORG AS?

BJØRKELANGEN TORG AS had revenue of NOK 16.7m in 2024.

Where is BJØRKELANGEN TORG AS based?

BJØRKELANGEN TORG AS has its business address in Surnadal.

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.