BIZTRAC BETA
Other captive investment companies

KNM HOLDING AS

Org. no. 921528191 Limited company (AS) Bærum Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −14,000
Equity NOK 6.8m
Incorporated 2018
Share capital NOK 80,000

Signals

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

KNM HOLDING AS is registered as a limited company in Bærum, Akershus with organisation number 921528191. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2018. Registered share capital is NOK 80,000, divided into 500 shares. The company's stated purpose is: “Investeringsvirksomhet i aksjer og andre finansielle eiendeler samt alt hva som eller her hører til.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −14,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −14,000
Equity
NOK 6.8m
Est. value
NOK 5.4m

Financial health · 2024

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

Who owns KNM HOLDING AS?

KRZYSZTOF NURZYNSKI
KNM HOLDING AS
NOK 0 rev. · NOK −14,000 profit

KNM HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does KNM HOLDING AS own?

KNM HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KNM HOLDING AS

Who owns KNM HOLDING AS?

KRZYSZTOF NURZYNSKI is the largest registered owner, with 65.0%.

What is the revenue of KNM HOLDING AS?

KNM HOLDING AS had revenue of NOK 0 in 2024.

Who is the general manager of KNM HOLDING AS?

Krzysztof Nurzynski is registered as general manager of KNM HOLDING AS.

Where is KNM HOLDING AS based?

KNM HOLDING AS has its business address in Høvik.

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.