BIZTRAC BETA
Rental and operating of own or leased real estate

KI-HOLDING AS

Org. no. 892645892 Limited company (AS) Risør Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 432,000
Operating profit NOK 49,000
Equity NOK 1.7m
Incorporated 2008
Share capital NOK 100,000

KI-HOLDING AS is registered as a limited company in Risør, Agder with organisation number 892645892. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eie, drift og utleie av fast eiendom, eie aksjer i andre selskap, utleie av varer, samt annen virksomhet som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 432,000 in revenue and NOK 49,000 in operating profit.

Key figures · 2024

Revenue
NOK 432,000
Operating profit
NOK 49,000
Equity
NOK 1.7m
Est. value
NOK 1.2m

Financial health · 2024

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

Who owns KI-HOLDING AS?

KÅRE ISAKSEN
KI-HOLDING AS
NOK 432,000 rev. · NOK 49,000 profit

KI-HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KI-HOLDING AS own?

KI-HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KI-HOLDING AS

Who owns KI-HOLDING AS?

KÅRE ISAKSEN is the largest registered owner, with 100.0%.

What is the revenue of KI-HOLDING AS?

KI-HOLDING AS had revenue of NOK 432,000 in 2024.

Who is the general manager of KI-HOLDING AS?

Kåre Isaksen is registered as general manager of KI-HOLDING AS.

Where is KI-HOLDING AS based?

KI-HOLDING AS has its business address in Risør.

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.