BIZTRAC BETA
COMPANY REGISTER PROFILE
989026666 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other captive investment companies

AJAK AS

Org. no. 989026666 Limited company (AS) Frogn Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −61,000
Equity NOK 13.3m
Incorporated 2005
Share capital NOK 100,000

Signals

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

AJAK AS is registered as a limited company in Frogn, Akershus with organisation number 989026666. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Deltakelse i andre virksomheter og kortsiktige kapitalplasseringer.”.

Key figures · 2025

Operating profit
NOK −61,000
▲ +53 %
Equity
NOK 13.3m
▲ +7 %
Est. value
NOK 10.5m

Financial health · 2025

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

Who owns AJAK AS?

AJAK AS
· NOK −61,000 profit

AJAK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AJAK AS

Who owns AJAK AS?

AXEL KRISTIAN STRØM is the largest registered owner, with 100.0%.

Where is AJAK AS based?

AJAK AS has its business address in Nordre Frogn.

Property

Business address C/O Axel k. Strøm Sindingveien 18, 1455 Nordre Frogn
Cadastral unit 3214-51/257/0/0
Building Helårsbolig benyttes som fritidsbolig · 1 unit

2 companies are registered at this address.

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.