BIZTRAC BETA
Development of building projects

BØE UTVIKLING AS

Org. no. 929767276 Limited company (AS) Kristiansund Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 17.9m
Operating profit NOK 1.2m
Equity NOK 218,000
Incorporated 2022
Share capital NOK 300,000

BØE UTVIKLING AS is registered as a limited company in Kristiansund, Møre og Romsdal with organisation number 929767276. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2022. Registered share capital is NOK 300,000, divided into 300 shares. The company's stated purpose is: “Kjøp og salg av eiendom og utvikling av eiendom, samt andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 17.9m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 17.9m
Operating profit
NOK 1.2m
Equity
NOK 218,000
Est. value
NOK 2.5m

Financial health · 2024

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

Who owns BØE UTVIKLING AS?

MB-T HOLDING AS
BØE UTVIKLING AS
NOK 17.9m rev. · NOK 1.2m profit

BØE UTVIKLING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BØE UTVIKLING AS

Who owns BØE UTVIKLING AS?

MB-T HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of BØE UTVIKLING AS?

BØE UTVIKLING AS had revenue of NOK 17.9m in 2024.

Who is the general manager of BØE UTVIKLING AS?

Morgan Bøe is registered as general manager of BØE UTVIKLING AS.

Where is BØE UTVIKLING AS based?

BØE UTVIKLING AS has its business address in Frei.

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.