BIZTRAC BETA
Other captive investment companies

KJELAAS HOLDING AS

Org. no. 989052136 Limited company (AS) Fredrikstad Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −113,000
Equity NOK 10.4m
Incorporated 2005
Share capital NOK 100,000

Signals

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

KJELAAS HOLDING AS is registered as a limited company in Fredrikstad, Østfold with organisation number 989052136. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Kjøp og salg av aksjer og andeler, kjøp og salg av fast eiendom, samt deltagelse i annen virksomhet med likelydende aktiviteter.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −113,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −113,000
Equity
NOK 10.4m
Est. value
NOK 7.8m

Financial health · 2024

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

Who owns KJELAAS HOLDING AS?

PER ANDERS KJELAAS
KJELAAS HOLDING AS
NOK 0 rev. · NOK −113,000 profit

KJELAAS HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KJELAAS HOLDING AS

Who owns KJELAAS HOLDING AS?

PER ANDERS KJELAAS is the largest registered owner, with 100.0%.

What is the revenue of KJELAAS HOLDING AS?

KJELAAS HOLDING AS had revenue of NOK 0 in 2024.

Who is the general manager of KJELAAS HOLDING AS?

Per Anders Kjelaas is registered as general manager of KJELAAS HOLDING AS.

Where is KJELAAS HOLDING AS based?

KJELAAS HOLDING AS has its business address in Fredrikstad.

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.