BIZTRAC BETA
Rental and operating of own or leased real estate

KCH HOLDING AS

Org. no. 913690346 Limited company (AS) Hvaler Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −9,000
Equity NOK 572,000
Incorporated 2014
Share capital NOK 30,000

Signals

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

KCH HOLDING AS is registered as a limited company in Hvaler, Østfold with organisation number 913690346. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investering i andre selskap og eiendommer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −9,000
Equity
NOK 572,000
Est. value
NOK 522,000

Financial health · 2025

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

Who owns KCH HOLDING AS?

CHRISTOPHER HUTH
KCH HOLDING AS
NOK 0 rev. · NOK −9,000 profit

KCH HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KCH HOLDING AS own?

KCH HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KCH HOLDING AS

Who owns KCH HOLDING AS?

CHRISTOPHER HUTH is the largest registered owner, with 100.0%.

What is the revenue of KCH HOLDING AS?

KCH HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of KCH HOLDING AS?

Christopher Huth is registered as general manager of KCH HOLDING AS.

Where is KCH HOLDING AS based?

KCH HOLDING AS has its business address in Skjærhalden.

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.