BIZTRAC BETA
General hospital activities

ALERIS HELSE AS

Org. no. 943545634 Limited company (AS) Oslo Incorporated 1987 Active
Ownership graph ↗
Revenue 2025 NOK 1.9bn
Operating profit NOK 253.8m
Equity NOK 432.9m
Incorporated 1987
Employees 658
Share capital NOK 4.0m

ALERIS HELSE AS is registered as a limited company in Oslo, Oslo with organisation number 943545634. The business is classified under general hospital activities (NACE 86.101). The company was incorporated in 1987 and has 658 registered employees. Registered share capital is NOK 4.0m, divided into 399471 shares. The company's stated purpose is: “Eie og drive medisinske klinikker og behandlingsinstitusjoner hvor det tilbys allmenn og spesialistlegetjenester, bedriftshelsetjenester og sykehusvirksomhet innen utvalgte områder, herunder å delta i selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.9bn in revenue and NOK 253.8m in operating profit.

Key figures · 2025

Revenue
NOK 1.9bn
Operating profit
NOK 253.8m
Equity
NOK 432.9m
Est. value
NOK 1.5bn

Financial health · 2025

Liquidity
1.54
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
54.4%
Very good
Equity as a share of total capital

Who owns ALERIS HELSE AS?

ALERIS HEALTHCARE AB
ALERIS HELSE AS
NOK 1.9bn rev. · NOK 253.8m profit

ALERIS HELSE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ALERIS HELSE AS

Who owns ALERIS HELSE AS?

ALERIS HEALTHCARE AB is the largest registered owner, with 100.0%.

What is the revenue of ALERIS HELSE AS?

ALERIS HELSE AS had revenue of NOK 1.9bn in 2025.

Who is the general manager of ALERIS HELSE AS?

Anita Tunold is registered as general manager of ALERIS HELSE AS.

Where is ALERIS HELSE AS based?

ALERIS HELSE 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 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.