biztrac. BETA
COMPANY REGISTER PROFILE
889042222 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other captive investment companies

KJAPPEN HOLDING AS

Org. no. 889042222 Limited company (AS) Drammen Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −15,000
Equity NOK 25.2m
Incorporated 2005
Share capital NOK 320,000

Signals

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

KJAPPEN HOLDING AS is registered as a limited company in Drammen, Buskerud with organisation number 889042222. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 320,000, divided into 320 shares. The company's stated purpose is: “Kjøp, salg, investering i aksjer og andre verdipapirer samt kjøp, salg og investering i fast eiendom med dertil tilhørende virksomhet.”.

Key figures · 2025

Operating profit
NOK −15,000
▼ −5 %
Equity
NOK 25.2m
▲ +7 %
Est. value
NOK 20.0m

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
8.3%
Satisfactory
Return on total assets
Solidity
94.7%
Very good
Equity as a share of total capital

Who owns KJAPPEN HOLDING AS?

KJAPPEN HOLDING AS
· NOK −15,000 profit

KJAPPEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KJAPPEN HOLDING AS own?

KJAPPEN HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about KJAPPEN HOLDING AS

Who owns KJAPPEN HOLDING AS?

Henrik Christopher Melsom Ornum is the largest registered owner, with 100.0%.

Who is the general manager of KJAPPEN HOLDING AS?

Henrik Christopher Melsom Ornum is registered as general manager of KJAPPEN HOLDING AS.

Where is KJAPPEN HOLDING AS based?

KJAPPEN HOLDING AS has its business address in Drammen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.