BIZTRAC BETA
COMPANY REGISTER PROFILE
989220438 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Retail sale of games and toys

KENKO AS

Org. no. 989220438 Limited company (AS) Bergen Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −28,000
Equity NOK 14.8m
Incorporated 2005
Share capital NOK 130,000

Signals

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

KENKO AS is registered as a limited company in Bergen, Vestland with organisation number 989220438. The business is classified under retail sale of games and toys (NACE 47.640). The company was incorporated in 2005. Registered share capital is NOK 130,000, divided into 130 shares. The company's stated purpose is: “Forvaltning av eierskap i andre selskap.”.

Key figures · 2025

Operating profit
NOK −28,000
▲ +51 %
Equity
NOK 14.8m
▲ +526 %
Est. value
NOK 100.1m

Financial health · 2025

Liquidity
4.96
Very good
Current assets ÷ current liabilities
Profitability
131.2%
Very good
Return on total assets
Solidity
80.4%
Very good
Equity as a share of total capital

Who owns KENKO AS?

KENKO AS
· NOK −28,000 profit

KENKO AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KENKO AS own?

KENKO AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about KENKO AS

Who owns KENKO AS?

KENNETH KOLSRUD is the largest registered owner, with 100.0%.

Where is KENKO AS based?

KENKO AS has its business address in Nesttun.

Property

Business address Skjoldhøgda 106, 5222 Nesttun
Cadastral unit 4601-40/993/0/0
Building Rekkehus · 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.