BIZTRAC BETA
Uoppgitt

EVA BREKKE HOLDING AS

Org. no. 920215173 Limited company (AS) Bergen Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −12,000
Equity NOK 1.2m
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−12k kr).

EVA BREKKE HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 920215173. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøp, salg og forvaltning av aksjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −12,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −12,000
Equity
NOK 1.2m
Est. value
NOK 740,000

Financial health · 2025

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

Who owns EVA BREKKE HOLDING AS?

EVA BREKKE
EVA BREKKE HOLDING AS
NOK 0 rev. · NOK −12,000 profit

EVA BREKKE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does EVA BREKKE HOLDING AS own?

EVA BREKKE HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EVA BREKKE HOLDING AS

Who owns EVA BREKKE HOLDING AS?

EVA BREKKE is the largest registered owner, with 100.0%.

What is the revenue of EVA BREKKE HOLDING AS?

EVA BREKKE HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of EVA BREKKE HOLDING AS?

Eva Brekke is registered as general manager of EVA BREKKE HOLDING AS.

Where is EVA BREKKE HOLDING AS based?

EVA BREKKE HOLDING AS has its business address in Blomsterdalen.

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.