BIZTRAC BETA
General medical practice activities

ELVERUM HELSESENTER AS

Org. no. 928774376 Limited company (AS) Elverum Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 3.1m
Operating profit NOK 314,000
Equity NOK 309,000
Incorporated 2022
Employees 8
Share capital NOK 30,000

ELVERUM HELSESENTER AS is registered as a limited company in Elverum, Innlandet with organisation number 928774376. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2022 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å drive legesenter- og helsevirksomhet i Elverum med alt det innebærer, herunder å delta og eie i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.1m in revenue and NOK 314,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.1m
Operating profit
NOK 314,000
Equity
NOK 309,000
Est. value
NOK 1.6m

Financial health · 2025

Liquidity
1.39
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
28.1%
Good
Equity as a share of total capital

Who owns ELVERUM HELSESENTER AS?

AZHAR DAUD KHAN
ELVERUM HELSESENTER AS
NOK 3.1m rev. · NOK 314,000 profit

ELVERUM HELSESENTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ELVERUM HELSESENTER AS

Who owns ELVERUM HELSESENTER AS?

AZHAR DAUD KHAN is the largest registered owner, with 100.0%.

What is the revenue of ELVERUM HELSESENTER AS?

ELVERUM HELSESENTER AS had revenue of NOK 3.1m in 2025.

Who is the general manager of ELVERUM HELSESENTER AS?

Azhar Daud Khan is registered as general manager of ELVERUM HELSESENTER AS.

Where is ELVERUM HELSESENTER AS based?

ELVERUM HELSESENTER AS has its business address in Elverum.

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.