BIZTRAC BETA
Other captive investment companies

BJØRKHAUG HOLDING AS

Org. no. 918307001 Limited company (AS) Ullensvang Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −1,000
Equity NOK 47,000
Incorporated 2016
Share capital NOK 30,000

Signals

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

BJØRKHAUG HOLDING AS is registered as a limited company in Ullensvang, Vestland with organisation number 918307001. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Selskapet formål er å eige, kjøpa og selja aksjer”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −1,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −1,000
Equity
NOK 47,000
Est. value
NOK 43,000

Financial health · 2025

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

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

Who owns BJØRKHAUG HOLDING AS?

MARIE OPHEIM
BJØRKHAUG HOLDING AS
NOK 0 rev. · NOK −1,000 profit

BJØRKHAUG HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does BJØRKHAUG HOLDING AS own?

BJØRKHAUG HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about BJØRKHAUG HOLDING AS

Who owns BJØRKHAUG HOLDING AS?

MARIE OPHEIM is the largest registered owner, with 33.3%.

What is the revenue of BJØRKHAUG HOLDING AS?

BJØRKHAUG HOLDING AS had revenue of NOK 0 in 2025.

Where is BJØRKHAUG HOLDING AS based?

BJØRKHAUG HOLDING AS has its business address in Odda.

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.