BIZTRAC BETA
Other captive investment companies

ADIK AS

Org. no. 995282453 Limited company (AS) Oslo Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −30,000
Equity NOK −6.0m
Incorporated 2010
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−6,0 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−30k kr).

ADIK AS is registered as a limited company in Oslo, Oslo with organisation number 995282453. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investeringer i real og finansobjekter med formål å berike hovedaksjonær.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −30,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −30,000
Equity
NOK −6.0m

Financial health · 2024

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

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

Who owns ADIK AS?

ADAM SAGA IKDAL
ADIK AS
NOK 0 rev. · NOK −30,000 profit

ADIK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ADIK AS own?

ADIK AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about ADIK AS

Who owns ADIK AS?

ADAM SAGA IKDAL is the largest registered owner, with 100.0%.

What is the revenue of ADIK AS?

ADIK AS had revenue of NOK 0 in 2024.

Who is the general manager of ADIK AS?

Adam Saga Ikdal is registered as general manager of ADIK AS.

Where is ADIK AS based?

ADIK 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.