BIZTRAC BETA
General medical practice activities

YAMA HOLDING AS

Org. no. 922205825 Limited company (AS) Lillestrøm Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 3.6m
Operating profit NOK 836,000
Equity NOK 295,000
Incorporated 2019
Share capital NOK 30,000

YAMA HOLDING AS is registered as a limited company in Lillestrøm, Akershus with organisation number 922205825. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Tjenester innen fastlegevirksomhet, samt derved forbunden virksomhet herunder drift av fast eiendom, handel og deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.6m in revenue and NOK 836,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.6m
Operating profit
NOK 836,000
Equity
NOK 295,000
Est. value
NOK 2.8m

Financial health · 2024

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

Who owns YAMA HOLDING AS?

YASIR MANZOOR
YAMA HOLDING AS
NOK 3.6m rev. · NOK 836,000 profit

YAMA HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does YAMA HOLDING AS own?

YAMA HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about YAMA HOLDING AS

Who owns YAMA HOLDING AS?

YASIR MANZOOR is the largest registered owner, with 100.0%.

What is the revenue of YAMA HOLDING AS?

YAMA HOLDING AS had revenue of NOK 3.6m in 2024.

Who is the general manager of YAMA HOLDING AS?

Yasir Manzoor is registered as general manager of YAMA HOLDING AS.

Where is YAMA HOLDING AS based?

YAMA HOLDING AS has its business address in Frogner.

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.