BIZTRAC BETA
Rental and operating of own or leased real estate

BJØLSTAD UTVIKLING AS

Org. no. 912366987 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 53.8m
Operating profit NOK −2.8m
Equity NOK 91.5m
Incorporated 2013
Share capital NOK 27.7m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,8 mill kr).

BJØLSTAD UTVIKLING AS is registered as a limited company in Oslo, Oslo with organisation number 912366987. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2013. Registered share capital is NOK 27.7m, divided into 100000 shares. The company's stated purpose is: “Erverv, drift, utvikling og salg av fast eiendom, også ved deltakelse i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 53.8m in revenue and NOK −2.8m in operating profit.

Key figures · 2024

Revenue
NOK 53.8m
Operating profit
NOK −2.8m
Equity
NOK 91.5m
Est. value
NOK 83.5m

Financial health · 2024

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

Who owns BJØLSTAD UTVIKLING AS?

BYHAVEN 1 AS
BJØLSTAD UTVIKLING AS
NOK 53.8m rev. · NOK −2.8m profit

BJØLSTAD UTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BJØLSTAD UTVIKLING AS own?

BJØLSTAD UTVIKLING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BJØLSTAD UTVIKLING AS

Who owns BJØLSTAD UTVIKLING AS?

BYHAVEN 1 AS is the largest registered owner, with 50.0%.

What is the revenue of BJØLSTAD UTVIKLING AS?

BJØLSTAD UTVIKLING AS had revenue of NOK 53.8m in 2024.

Where is BJØLSTAD UTVIKLING AS based?

BJØLSTAD UTVIKLING AS has its business address in Oslo.

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.