BIZTRAC BETA
Rental and operating of own or leased real estate

BREIVIKA INDUSTRIVEG 63 AS

Org. no. 916484313 Limited company (AS) Ålesund Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 4.9m
Operating profit NOK 3.1m
Equity NOK 2.4m
Incorporated 2015
Share capital NOK 95,000

BREIVIKA INDUSTRIVEG 63 AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 916484313. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 95,000, divided into 948250 shares. The company's stated purpose is: “Eie og forvalte fast eiendom, samt annen virksomhet som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.9m in revenue and NOK 3.1m in operating profit.

Key figures · 2024

Revenue
NOK 4.9m
Operating profit
NOK 3.1m
Equity
NOK 2.4m
Est. value
NOK 4.7m

Financial health · 2024

Liquidity
3.72
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 BREIVIKA INDUSTRIVEG 63 AS?

NORDVEST NÆRINGSBYGG AS
BREIVIKA INDUSTRIVEG 63 AS
NOK 4.9m rev. · NOK 3.1m profit

BREIVIKA INDUSTRIVEG 63 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BREIVIKA INDUSTRIVEG 63 AS

Who owns BREIVIKA INDUSTRIVEG 63 AS?

NORDVEST NÆRINGSBYGG AS is the largest registered owner, with 100.0%.

What is the revenue of BREIVIKA INDUSTRIVEG 63 AS?

BREIVIKA INDUSTRIVEG 63 AS had revenue of NOK 4.9m in 2024.

Who is the general manager of BREIVIKA INDUSTRIVEG 63 AS?

Ove Bjørkavåg is registered as general manager of BREIVIKA INDUSTRIVEG 63 AS.

Where is BREIVIKA INDUSTRIVEG 63 AS based?

BREIVIKA INDUSTRIVEG 63 AS has its business address in Ålesund.

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.