BIZTRAC BETA
Repair and maintenance of motor vehicles

BREIVOLLVEIEN EIENDOM AS

Org. no. 991670831 Limited company (AS) Oslo Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 7.9m
Operating profit NOK 7.1m
Equity NOK 1.7m
Incorporated 2007
Share capital NOK 100,000

BREIVOLLVEIEN EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 991670831. The business is classified under repair and maintenance of motor vehicles (NACE 95.310). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie, forvalte og utvikle eiendom og alt som naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.9m in revenue and NOK 7.1m in operating profit.

Key figures · 2024

Revenue
NOK 7.9m
Operating profit
NOK 7.1m
Equity
NOK 1.7m
Est. value
NOK 20.7m

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
12.6%
Satisfactory
Equity as a share of total capital

Who owns BREIVOLLVEIEN EIENDOM AS?

BAUDA AS
BREIVOLLVEIEN EIENDOM AS
NOK 7.9m rev. · NOK 7.1m profit

BREIVOLLVEIEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BREIVOLLVEIEN EIENDOM AS er morselskap for 16 datterselskaper:

Frequently asked questions about BREIVOLLVEIEN EIENDOM AS

Who owns BREIVOLLVEIEN EIENDOM AS?

BAUDA AS is the largest registered owner, with 100.0%.

What is the revenue of BREIVOLLVEIEN EIENDOM AS?

BREIVOLLVEIEN EIENDOM AS had revenue of NOK 7.9m in 2024.

Who is the general manager of BREIVOLLVEIEN EIENDOM AS?

Henrik Baumann is registered as general manager of BREIVOLLVEIEN EIENDOM AS.

Where is BREIVOLLVEIEN EIENDOM AS based?

BREIVOLLVEIEN EIENDOM 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.