BIZTRAC BETA
Other captive investment companies

KA NYGÅRD HOLDING AS

Org. no. 997871413 Limited company (AS) Molde Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −38,000
Equity NOK 117,000
Incorporated 2012
Share capital NOK 50,000

Signals

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

KA NYGÅRD HOLDING AS is registered as a limited company in Molde, Møre og Romsdal with organisation number 997871413. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2012. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Kjøp, eie, salg og forvaltning av aksjer, selskapsandeler og dertil hørende aktiviteter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −38,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −38,000
Equity
NOK 117,000
Est. value
NOK 107,000

Financial health · 2025

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

Who owns KA NYGÅRD HOLDING AS?

KJARTAN ANDRE NYGÅRD
KA NYGÅRD HOLDING AS
NOK 0 rev. · NOK −38,000 profit

KA NYGÅRD HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KA NYGÅRD HOLDING AS own?

KA NYGÅRD HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KA NYGÅRD HOLDING AS

Who owns KA NYGÅRD HOLDING AS?

KJARTAN ANDRE NYGÅRD is the largest registered owner, with 100.0%.

What is the revenue of KA NYGÅRD HOLDING AS?

KA NYGÅRD HOLDING AS had revenue of NOK 0 in 2025.

Where is KA NYGÅRD HOLDING AS based?

KA NYGÅRD HOLDING AS has its business address in Midsund.

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.