BIZTRAC BETA
Accounting and bookkeeping

KHS HOLDING AS

Org. no. 944393609 Limited company (AS) Senja Incorporated 1987 Active
Ownership graph ↗
Revenue 2025 NOK 2,000
Operating profit NOK −8,000
Equity NOK 1.4m
Incorporated 1987
Share capital NOK 100,000

Signals

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

KHS HOLDING AS is registered as a limited company in Senja, Troms with organisation number 944393609. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 1987. Registered share capital is NOK 100,000, divided into 200 shares. The company's stated purpose is: “Regnskapstjenester for privatpersoner/næringsdrivende, kjøp/salg av aksjer, rådgivning overfor næringsdrivende, og hva derved står i forbindelse, herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 2,000 in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 2,000
Operating profit
NOK −8,000
Equity
NOK 1.4m
Est. value
NOK 848,000

Financial health · 2025

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

Who owns KHS HOLDING AS?

KJELL HUGO SOLSTAD
KHS HOLDING AS
NOK 2,000 rev. · NOK −8,000 profit

KHS HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KHS HOLDING AS own?

KHS HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KHS HOLDING AS

Who owns KHS HOLDING AS?

KJELL HUGO SOLSTAD is the largest registered owner, with 100.0%.

What is the revenue of KHS HOLDING AS?

KHS HOLDING AS had revenue of NOK 2,000 in 2025.

Where is KHS HOLDING AS based?

KHS HOLDING AS has its business address in Finnsnes.

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.