BIZTRAC BETA
Other captive investment companies

ÅK JOHNSEN INVEST AS

Org. no. 989225545 Limited company (AS) Kongsberg Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −48,000
Equity NOK 10.3m
Incorporated 2005
Share capital NOK 350,000

Signals

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

ÅK JOHNSEN INVEST AS is registered as a limited company in Kongsberg, Buskerud with organisation number 989225545. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 350,000, divided into 350 shares. The company's stated purpose is: “Drive økonomisk konsulentvirksomhet, rådgivning overfor næringsdrivende virksomheter og deltagelse i andre selskaper, generell investeringsvirksomhet, herunder handel med verdipapirer, investering i selskaper, eiendom og andre aktiva.”.

Key figures · 2025

Operating profit
NOK −48,000
Equity
NOK 10.3m
Est. value
NOK 6.2m

Financial health · 2025

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

Who owns ÅK JOHNSEN INVEST AS?

TORODD ÅK JOHNSEN
ÅK JOHNSEN INVEST AS
· NOK −48,000 profit

ÅK JOHNSEN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ÅK JOHNSEN INVEST AS own?

ÅK JOHNSEN INVEST AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about ÅK JOHNSEN INVEST AS

Who owns ÅK JOHNSEN INVEST AS?

TORODD ÅK JOHNSEN is the largest registered owner, with 100.0%.

Who is the general manager of ÅK JOHNSEN INVEST AS?

Torodd Åk Johnsen is registered as general manager of ÅK JOHNSEN INVEST AS.

Where is ÅK JOHNSEN INVEST AS based?

ÅK JOHNSEN INVEST AS has its business address in Kongsberg.

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.