BIZTRAC BETA
Plumbing installation

BROVOLD EIENDOM AS

Org. no. 918592199 Limited company (AS) Hustadvika Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 514,000
Operating profit NOK 177,000
Equity NOK 34,000
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BROVOLD EIENDOM AS is registered as a limited company in Hustadvika, Møre og Romsdal with organisation number 918592199. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Utleie av fast eiendom, samt alt som står i forbindelse med dette, herunder deltagelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 514,000 in revenue and NOK 177,000 in operating profit.

Key figures · 2025

Revenue
NOK 514,000
Operating profit
NOK 177,000
Equity
NOK 34,000
Est. value
NOK 472,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BROVOLD EIENDOM AS?

I BROVOLD & SØNN AS
BROVOLD EIENDOM AS
NOK 514,000 rev. · NOK 177,000 profit

BROVOLD EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BROVOLD EIENDOM AS

Who owns BROVOLD EIENDOM AS?

I BROVOLD & SØNN AS is the largest registered owner, with 100.0%.

What is the revenue of BROVOLD EIENDOM AS?

BROVOLD EIENDOM AS had revenue of NOK 514,000 in 2025.

Where is BROVOLD EIENDOM AS based?

BROVOLD EIENDOM AS has its business address in Eide.

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.