biztrac. BETA
COMPANY REGISTER PROFILE
922545952 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Non-specialised retail sale of predominately food, beverages or tobacco

AFSHA HOLDING AS

Org. no. 922545952 Limited company (AS) Oslo Incorporated 2019 Active
Operating profit NOK −45,000
Equity NOK 737,000
Incorporated 2019
Share capital NOK 130,000

Signals

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

AFSHA HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 922545952. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2019. Registered share capital is NOK 130,000, divided into 100 shares. The company's stated purpose is: “Eie aksjer i andre selskap, investering i aksjer og andre verdipapirer, eie, drift og utleie av fast eiendom, samt annen virksomhet som står i nær sammenheng med dette.”.

Key figures · 2025

Operating profit
NOK −45,000
▼ −63 %
Equity
NOK 737,000
▼ −6 %
Est. value
NOK 922,000

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 AFSHA HOLDING AS?

AFSHA HOLDING AS
· NOK −45,000 profit

AFSHA HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does AFSHA HOLDING AS own?

AFSHA HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about AFSHA HOLDING AS

Who owns AFSHA HOLDING AS?

Aksa Ilyas is the largest registered owner, with 100.0%.

Who is the general manager of AFSHA HOLDING AS?

Aksa Ilyas is registered as general manager of AFSHA HOLDING AS.

Where is AFSHA HOLDING AS based?

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