BIZTRAC BETA
Other captive investment companies

BH INVESTERING AS

Org. no. 999196853 Limited company (AS) Stavanger Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −38,000
Equity NOK 3.1m
Incorporated 2012
Share capital NOK 30,000

Signals

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

BH INVESTERING AS is registered as a limited company in Stavanger, Rogaland with organisation number 999196853. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av aksjer og andre verdipapirer samt aktiviteter som naturlig faller sammen med dette, herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −38,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −38,000
Equity
NOK 3.1m
Est. value
NOK 4.1m

Financial health · 2025

Liquidity
8778.76
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 BH INVESTERING AS?

ANNE GUNN BERG
BH INVESTERING AS
NOK 0 rev. · NOK −38,000 profit

BH INVESTERING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BH INVESTERING AS own?

BH INVESTERING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BH INVESTERING AS

Who owns BH INVESTERING AS?

ANNE GUNN BERG is the largest registered owner, with 100.0%.

What is the revenue of BH INVESTERING AS?

BH INVESTERING AS had revenue of NOK 0 in 2025.

Where is BH INVESTERING AS based?

BH INVESTERING AS has its business address in Stavanger.

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.