BIZTRAC BETA
Uoppgitt

BLOMHOFF HOLDING AS

Org. no. 936036007 Limited company (AS) Lillestrøm Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −7
Equity NOK 23,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

BLOMHOFF HOLDING AS is registered as a limited company in Lillestrøm, Akershus with organisation number 936036007. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −7
Equity
NOK 23,000
Est. value
NOK 28,000

Financial health · 2025

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

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

Who owns BLOMHOFF HOLDING AS?

KRISTIAN JOHNSEN BLOMHOFF
BLOMHOFF HOLDING AS
· NOK −7 profit

BLOMHOFF HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BLOMHOFF HOLDING AS own?

BLOMHOFF HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BLOMHOFF HOLDING AS

Who owns BLOMHOFF HOLDING AS?

KRISTIAN JOHNSEN BLOMHOFF is the largest registered owner, with 100.0%.

Who is the general manager of BLOMHOFF HOLDING AS?

Kristian Johnsen Blomhoff is registered as general manager of BLOMHOFF HOLDING AS.

Where is BLOMHOFF HOLDING AS based?

BLOMHOFF HOLDING AS has its business address in Lillestrøm.

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.