BIZTRAC BETA
Development of building projects

BREKKE-ØVSTHUS UTVIKLING AS

Org. no. 920536786 Limited company (AS) Voss Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 142,000
Operating profit NOK 2
Equity NOK 40,000
Incorporated 2018
Share capital NOK 40,000

BREKKE-ØVSTHUS UTVIKLING AS is registered as a limited company in Voss, Vestland with organisation number 920536786. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2018. Registered share capital is NOK 40,000, divided into 40 shares. The company's stated purpose is: “Utvikling og drift av fast eiendom samt hva med dette hører til.”. The most recent filed accounts, for the 2025 financial year, show NOK 142,000 in revenue and NOK 2 in operating profit.

Key figures · 2025

Revenue
NOK 142,000
Operating profit
NOK 2
Equity
NOK 40,000
Est. value
NOK 28,000

Financial health · 2025

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

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

Who owns BREKKE-ØVSTHUS UTVIKLING AS?

EILEV ØVSTHUS
BREKKE-ØVSTHUS UTVIKLING AS
NOK 142,000 rev. · NOK 2 profit

BREKKE-ØVSTHUS UTVIKLING AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about BREKKE-ØVSTHUS UTVIKLING AS

Who owns BREKKE-ØVSTHUS UTVIKLING AS?

EILEV ØVSTHUS is the largest registered owner, with 25.0%.

What is the revenue of BREKKE-ØVSTHUS UTVIKLING AS?

BREKKE-ØVSTHUS UTVIKLING AS had revenue of NOK 142,000 in 2025.

Who is the general manager of BREKKE-ØVSTHUS UTVIKLING AS?

Dagny Vangen is registered as general manager of BREKKE-ØVSTHUS UTVIKLING AS.

Where is BREKKE-ØVSTHUS UTVIKLING AS based?

BREKKE-ØVSTHUS UTVIKLING AS has its business address in Voss.

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.