BIZTRAC BETA
Uoppgitt

KRAAKA KAPITAL AS

Org. no. 928221202 Limited company (AS) Skien Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −4,000
Equity NOK −664
Incorporated 2021
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−664 kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4k kr).

KRAAKA KAPITAL AS is registered as a limited company in Skien, Telemark with organisation number 928221202. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −4,000
Equity
NOK −664

Financial health · 2025

Liquidity
0.83
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-0.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns KRAAKA KAPITAL AS?

JON HALVOR HAMSDOKKA
KRAAKA KAPITAL AS
· NOK −4,000 profit

KRAAKA KAPITAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KRAAKA KAPITAL AS own?

KRAAKA KAPITAL AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KRAAKA KAPITAL AS

Who owns KRAAKA KAPITAL AS?

JON HALVOR HAMSDOKKA is the largest registered owner, with 100.0%.

Who is the general manager of KRAAKA KAPITAL AS?

Jon Halvor Hamsdokka is registered as general manager of KRAAKA KAPITAL AS.

Where is KRAAKA KAPITAL AS based?

KRAAKA KAPITAL AS has its business address in Skien.

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.