BIZTRAC BETA
Buying and selling of own real estate

KAIHAN HOLDING AS

Org. no. 921310188 Limited company (AS) Asker Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −54,000
Equity NOK 569,000
Incorporated 2018
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−54k kr).

KAIHAN HOLDING AS is registered as a limited company in Asker, Akershus with organisation number 921310188. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2018. Registered share capital is NOK 200,000, divided into 2000 shares. The company's stated purpose is: “Investering i fast eiendom, aksjer og verdipapirer, selskapsandeler og deltagelse i andre selskaper, salg av konsulenttjenester, med salg av tjenester og produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet.”.

Key figures · 2024

Operating profit
NOK −54,000
Equity
NOK 569,000
Est. value
NOK 519,000

Financial health · 2024

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

Who owns KAIHAN HOLDING AS?

ZOLTEQAR ABDULAZIZ AZIZI
KAIHAN HOLDING AS
· NOK −54,000 profit

KAIHAN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KAIHAN HOLDING AS own?

KAIHAN HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KAIHAN HOLDING AS

Who owns KAIHAN HOLDING AS?

ZOLTEQAR ABDULAZIZ AZIZI is the largest registered owner, with 100.0%.

Who is the general manager of KAIHAN HOLDING AS?

Bushra Saddique is registered as general manager of KAIHAN HOLDING AS.

Where is KAIHAN HOLDING AS based?

KAIHAN HOLDING AS has its business address in Bødalen.

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.