BIZTRAC BETA
Other captive investment companies

JLP HOLDING AS

Org. no. 933526917 Limited company (AS) Bodø Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −14,000
Equity NOK 6,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

JLP HOLDING AS is registered as a limited company in Bodø, Nordland with organisation number 933526917. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Holding selskap. Selskapet skal investere i annen næringsvirksomhet, herunder aksjer og andeler, eiendom og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −14,000
Equity
NOK 6,000
Est. value
NOK 5,000

Financial health · 2025

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

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

Who owns JLP HOLDING AS?

PÅL MAGNUS STAVRUM
JLP HOLDING AS
NOK 0 rev. · NOK −14,000 profit

JLP HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does JLP HOLDING AS own?

JLP HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JLP HOLDING AS

Who owns JLP HOLDING AS?

PÅL MAGNUS STAVRUM is the largest registered owner, with 50.0%.

What is the revenue of JLP HOLDING AS?

JLP HOLDING AS had revenue of NOK 0 in 2025.

Where is JLP HOLDING AS based?

JLP HOLDING AS has its business address in Bodø.

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.