BIZTRAC BETA
COMPANY REGISTER PROFILE
926025309 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

AJMKOS AS

Org. no. 926025309 Limited company (AS) Stavanger Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −105,000
Equity NOK 6.2m
Incorporated 2020
Share capital NOK 550,000

Signals

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

AJMKOS AS is registered as a limited company in Stavanger, Rogaland with organisation number 926025309. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 550,000, divided into 550000 shares. The company's stated purpose is: “Aksjeinvestering, herunder kjøpe, eie og selge aksjer i andre aksjeselskaper.”.

Key figures · 2025

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

Financial health · 2025

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

Who owns AJMKOS AS?

AJMKOS AS
· NOK −105,000 profit

AJMKOS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does AJMKOS AS own?

AJMKOS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AJMKOS AS

Who owns AJMKOS AS?

ARNE JOHAN SKOGLI is the largest registered owner, with 100.0%.

Where is AJMKOS AS based?

AJMKOS AS has its business address in Hundvåg.

Property

Business address Krosshaughagen 16C, 4085 Hundvåg
Cadastral unit 1103-7/1427/0/0
Building Rekkehus · 6 units

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.