BIZTRAC BETA
COMPANY REGISTER PROFILE
835490122 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

KOH HOLDING AS

Org. no. 835490122 Limited company (AS) Karmøy Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −12,000
Equity NOK 4.5m
Incorporated 2025
Share capital NOK 30,000

Signals

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

KOH HOLDING AS is registered as a limited company in Karmøy, Rogaland with organisation number 835490122. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 75 shares. The company's stated purpose is: “Eie av aksjer og andre investeringsprodukter.”.

Key figures · 2025

Operating profit
NOK −12,000
Equity
NOK 4.5m
Est. value
NOK 5.1m

Financial health · 2025

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

Who owns KOH HOLDING AS?

KOH HOLDING AS
· NOK −12,000 profit

KOH HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KOH HOLDING AS own?

KOH HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about KOH HOLDING AS

Who owns KOH HOLDING AS?

KJELL OVE HANSEN is the largest registered owner, with 100.0%.

Where is KOH HOLDING AS based?

KOH HOLDING AS has its business address in Avaldsnes.

Property

Business address Kleivavegen 2, 4262 Avaldsnes
Cadastral unit 1149-82/178/0/0
Building Enebolig · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.