BIZTRAC BETA
Construction of residential and non-residential buildings

JRKPI HOLDING AS

Org. no. 926923811 Limited company (AS) Nes Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −15,000
Equity NOK 414,000
Incorporated 2021
Share capital NOK 60,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−15k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

JRKPI HOLDING AS is registered as a limited company in Nes, Akershus with organisation number 926923811. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2021. Registered share capital is NOK 60,000, divided into 30000 shares. The company's stated purpose is: “Investering i og forvaltning av verdipapirer, herunder aksjer. Videre kjøp, salg og forvaltning av fast eiendom, deltagelse i andre virksomheter.”.

Key figures · 2024

Operating profit
NOK −15,000
Equity
NOK 414,000
Est. value
NOK 2.4m

Financial health · 2024

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

Who owns JRKPI HOLDING AS?

PPI AS
JRKPI HOLDING AS
· NOK −15,000 profit

JRKPI HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does JRKPI HOLDING AS own?

JRKPI HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about JRKPI HOLDING AS

Who owns JRKPI HOLDING AS?

PPI AS is the largest registered owner, with 50.0%.

Who is the general manager of JRKPI HOLDING AS?

Jørn Roar Korneliussen is registered as general manager of JRKPI HOLDING AS.

Where is JRKPI HOLDING AS based?

JRKPI HOLDING AS has its business address in Årnes.

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.