biztrac. BETA
COMPANY REGISTER PROFILE
923626409 ORG. NO. 2023 ACCOUNTS 7 SECTIONS
Compulsory dissolution UPDATED 03.10.2026
⚠ARIKAN HOLDING AS is registered as “Compulsory dissolution” with the Brønnøysund Register Centre.
Restaurant activities

ARIKAN HOLDING AS

Org. no. 923626409 Limited company (AS) Oslo Incorporated 2019 Compulsory dissolution
Operating profit NOK 248,000
Equity NOK −617,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Tvangsoppløsning Selskapet er under tvangsoppløsning.

ARIKAN HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 923626409. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering i unotert/ notert aksjer og selskaper, administrativt og annet konsulentarbeid.”.

Key figures · 2023

Operating profit
NOK 248,000
▲ +128 %
Equity
NOK −617,000
▲ +29 %

Financial health · 2023

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-63.0%
Weak
Equity as a share of total capital

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

Who owns ARIKAN HOLDING AS?

ARIKAN HOLDING AS
· NOK 248,000 profit

ARIKAN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ARIKAN HOLDING AS own?

ARIKAN HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about ARIKAN HOLDING AS

Who owns ARIKAN HOLDING AS?

Ozan Arikan is the largest registered owner, with 100.0%.

Who is the general manager of ARIKAN HOLDING AS?

Ozan Arikan is registered as general manager of ARIKAN HOLDING AS.

Where is ARIKAN HOLDING AS based?

ARIKAN HOLDING 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.