BIZTRAC BETA
Other captive investment companies

JULLUMSTRØ HOLDING AS

Org. no. 921715978 Limited company (AS) Stjørdal Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −6,000
Equity NOK 2.8m
Incorporated 2018
Share capital NOK 30,000

Signals

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

JULLUMSTRØ HOLDING AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 921715978. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Eie aksjer i andre selskaper og virksomhet i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 2.8m
Est. value
NOK 4.0m

Financial health · 2025

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

Who owns JULLUMSTRØ HOLDING AS?

JOHN ESPEN JULLUMSTRØ
JULLUMSTRØ HOLDING AS
NOK 0 rev. · NOK −6,000 profit

JULLUMSTRØ HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JULLUMSTRØ HOLDING AS own?

JULLUMSTRØ HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about JULLUMSTRØ HOLDING AS

Who owns JULLUMSTRØ HOLDING AS?

JOHN ESPEN JULLUMSTRØ is the largest registered owner, with 100.0%.

What is the revenue of JULLUMSTRØ HOLDING AS?

JULLUMSTRØ HOLDING AS had revenue of NOK 0 in 2025.

Where is JULLUMSTRØ HOLDING AS based?

JULLUMSTRØ HOLDING AS has its business address in Hell.

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.