BIZTRAC BETA
Uoppgitt

BLOMMENHOLM HOLDING AS

Org. no. 934339282 Limited company (AS) Bærum Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −10,000
Equity NOK 1,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

BLOMMENHOLM HOLDING AS is registered as a limited company in Bærum, Akershus with organisation number 934339282. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i andre selskaper, og alt annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

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

Financial health · 2025

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

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

Who owns BLOMMENHOLM HOLDING AS?

JOAKIM HOWLID
BLOMMENHOLM HOLDING AS
NOK 0 rev. · NOK −10,000 profit

BLOMMENHOLM HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BLOMMENHOLM HOLDING AS own?

BLOMMENHOLM HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BLOMMENHOLM HOLDING AS

Who owns BLOMMENHOLM HOLDING AS?

JOAKIM HOWLID is the largest registered owner, with 100.0%.

What is the revenue of BLOMMENHOLM HOLDING AS?

BLOMMENHOLM HOLDING AS had revenue of NOK 0 in 2025.

Where is BLOMMENHOLM HOLDING AS based?

BLOMMENHOLM HOLDING AS has its business address in Blommenholm.

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.