BIZTRAC BETA
Other captive investment companies

KJELDA HOLDING AS

Org. no. 818802552 Limited company (AS) Gloppen Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −4,000
Equity NOK 269,000
Incorporated 2017
Share capital NOK 50,000

Signals

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

KJELDA HOLDING AS is registered as a limited company in Gloppen, Vestland with organisation number 818802552. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2017. Registered share capital is NOK 50,000, divided into 2000 shares. The company's stated purpose is: “Investeringsverksemd, medrekna forvaltning av aksjar og andelar i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −4,000
Equity
NOK 269,000
Est. value
NOK 152,000

Financial health · 2025

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

Who owns KJELDA HOLDING AS?

JANNE GIMMESTAD
KJELDA HOLDING AS
NOK 0 rev. · NOK −4,000 profit

KJELDA HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does KJELDA HOLDING AS own?

KJELDA HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Group structure

KJELDA HOLDING AS er morselskap for 1 datterselskap:

Frequently asked questions about KJELDA HOLDING AS

Who owns KJELDA HOLDING AS?

JANNE GIMMESTAD is the largest registered owner, with 50.0%.

What is the revenue of KJELDA HOLDING AS?

KJELDA HOLDING AS had revenue of NOK 0 in 2025.

Where is KJELDA HOLDING AS based?

KJELDA HOLDING AS has its business address in Sandane.

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.