BIZTRAC BETA
Uoppgitt

KOKO AS

Org. no. 988962570 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 6.9m
Operating profit NOK −242,000
Equity NOK 64.1m
Incorporated 2005
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−242k kr).

KOKO AS is registered as a limited company in Oslo, Oslo with organisation number 988962570. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Selskapets formål er investering i aksjer, andeler og fast eiendom, samt virksomhet som har tilknytning til dette, slik at aksjonærenes ønkse om en god fremtid, et liv i balanse og økonomisk uavhengighet kan gå i oppfyllelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.9m in revenue and NOK −242,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.9m
Operating profit
NOK −242,000
Equity
NOK 64.1m
Est. value
NOK 38.2m

Financial health · 2024

Liquidity
234.80
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 KOKO AS?

HANS GEELMUYDEN
KOKO AS
NOK 6.9m rev. · NOK −242,000 profit

KOKO AS has 5 registered shareholders:

All shareholders and roles →

Which companies does KOKO AS own?

KOKO AS holds stakes in 16 companies:

See the full ownership structure →

Frequently asked questions about KOKO AS

Who owns KOKO AS?

HANS GEELMUYDEN is the largest registered owner, with 70.0%.

What is the revenue of KOKO AS?

KOKO AS had revenue of NOK 6.9m in 2024.

Who is the general manager of KOKO AS?

Hans Geelmuyden is registered as general manager of KOKO AS.

Where is KOKO AS based?

KOKO AS has its business address in Oslo.

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.