BIZTRAC BETA
Other support activities for petroleum and natural gas extraction

BEERENBERG HOLDING AS

Org. no. 889694742 Limited company (AS) Bergen Incorporated 2006 Active
Ownership graph ↗
Operating profit NOK −25,000
Equity NOK 740.9m
Incorporated 2006
Share capital NOK 58.5m

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−25k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BEERENBERG HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 889694742. The business is classified under other support activities for petroleum and natural gas extraction (NACE 09.109). The company was incorporated in 2006. Registered share capital is NOK 58.5m, divided into 194226 shares. The company's stated purpose is: “Eie aksjer og delta i andre virksomheter.”.

Key figures · 2025

Operating profit
NOK −25,000
Equity
NOK 740.9m
Est. value
NOK 366.0m

Financial health · 2025

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

Who owns BEERENBERG HOLDING AS?

BEERENBERG AS
BEERENBERG HOLDING AS
· NOK −25,000 profit

BEERENBERG HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BEERENBERG HOLDING AS own?

BEERENBERG HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about BEERENBERG HOLDING AS

Who owns BEERENBERG HOLDING AS?

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

Who is the general manager of BEERENBERG HOLDING AS?

Arild Apelthun is registered as general manager of BEERENBERG HOLDING AS.

Where is BEERENBERG HOLDING AS based?

BEERENBERG HOLDING AS has its business address in Kokstad.

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.