BIZTRAC BETA
Uoppgitt

ERIK BREKKE HOLDING AS

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

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−10k kr).

ERIK BREKKE HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 920215084. 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 2024 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −10,000
Equity
NOK 1.2m
Est. value
NOK 2.0m

Financial health · 2024

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

Who owns ERIK BREKKE HOLDING AS?

ERIK BREKKE
ERIK BREKKE HOLDING AS
NOK 0 rev. · NOK −10,000 profit

ERIK BREKKE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ERIK BREKKE HOLDING AS own?

ERIK BREKKE HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ERIK BREKKE HOLDING AS

Who owns ERIK BREKKE HOLDING AS?

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

What is the revenue of ERIK BREKKE HOLDING AS?

ERIK BREKKE HOLDING AS had revenue of NOK 0 in 2024.

Who is the general manager of ERIK BREKKE HOLDING AS?

Erik Brekke is registered as general manager of ERIK BREKKE HOLDING AS.

Where is ERIK BREKKE HOLDING AS based?

ERIK BREKKE HOLDING AS has its business address in Rådal.

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.