BIZTRAC BETA
General medical practice activities

CHERRY ENTERPRISES AS

Org. no. 832994162 Limited company (AS) Ullensaker Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −18,000
Equity NOK 165,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

CHERRY ENTERPRISES AS is registered as a limited company in Ullensaker, Akershus with organisation number 832994162. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −18,000
Equity
NOK 165,000
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns CHERRY ENTERPRISES AS?

JUNED MAHMOOD
CHERRY ENTERPRISES AS
· NOK −18,000 profit

CHERRY ENTERPRISES AS has 3 registered shareholders:

All shareholders and roles →

Which companies does CHERRY ENTERPRISES AS own?

CHERRY ENTERPRISES AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about CHERRY ENTERPRISES AS

Who owns CHERRY ENTERPRISES AS?

JUNED MAHMOOD is the largest registered owner, with 33.3%.

Who is the general manager of CHERRY ENTERPRISES AS?

Juned Mahmood is registered as general manager of CHERRY ENTERPRISES AS.

Where is CHERRY ENTERPRISES AS based?

CHERRY ENTERPRISES AS has its business address in Jessheim.

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.