BIZTRAC BETA
Temporary employment agency activities and other human resource provisions

JPD HOLDING AS

Org. no. 934751280 Limited company (AS) Flesberg Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK −1.2m
Equity NOK 2.8m
Incorporated 2024
Share capital NOK 50,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,2 mill kr).

JPD HOLDING AS is registered as a limited company in Flesberg, Buskerud with organisation number 934751280. The business is classified under temporary employment agency activities and other human resource provisions (NACE 78.200). The company was incorporated in 2024. Registered share capital is NOK 50,000, divided into 500 shares. The company's stated purpose is: “Utleie av arbeidskraft og salg av konsulentytelser samt kjøp og salg av aksjer og andeler i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK −1.2m in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK −1.2m
Equity
NOK 2.8m
Est. value
NOK 3.8m

Financial health · 2024

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

Who owns JPD HOLDING AS?

JAN PAUL DOKKEN
JPD HOLDING AS
NOK 2.1m rev. · NOK −1.2m profit

JPD HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JPD HOLDING AS own?

JPD HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about JPD HOLDING AS

Who owns JPD HOLDING AS?

JAN PAUL DOKKEN is the largest registered owner, with 100.0%.

What is the revenue of JPD HOLDING AS?

JPD HOLDING AS had revenue of NOK 2.1m in 2024.

Where is JPD HOLDING AS based?

JPD HOLDING AS has its business address in Svene.

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.