BIZTRAC BETA
General medical practice activities

HELSEBANKEN LEGESENTER AS

Org. no. 934911903 Limited company (AS) Gjesdal Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 5.9m
Operating profit NOK 13
Equity NOK 300,000
Incorporated 2024
Employees 7
Share capital NOK 75,000

HELSEBANKEN LEGESENTER AS is registered as a limited company in Gjesdal, Rogaland with organisation number 934911903. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2024 and has 7 registered employees. Registered share capital is NOK 75,000, divided into 75 shares. The company's stated purpose is: “Drift av fastlegekontor og andre tjenester som naturlig er som naturlig hører til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.9m in revenue and NOK 13 in operating profit.

Key figures · 2025

Revenue
NOK 5.9m
Operating profit
NOK 13
Equity
NOK 300,000
Est. value
NOK 186,000

Financial health · 2025

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

Who owns HELSEBANKEN LEGESENTER AS?

HALLGEIR JARL HEGGEM
HELSEBANKEN LEGESENTER AS
NOK 5.9m rev. · NOK 13 profit

HELSEBANKEN LEGESENTER AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about HELSEBANKEN LEGESENTER AS

Who owns HELSEBANKEN LEGESENTER AS?

HALLGEIR JARL HEGGEM is the largest registered owner, with 33.3%.

What is the revenue of HELSEBANKEN LEGESENTER AS?

HELSEBANKEN LEGESENTER AS had revenue of NOK 5.9m in 2025.

Who is the general manager of HELSEBANKEN LEGESENTER AS?

Evita Deressa Kersbergen is registered as general manager of HELSEBANKEN LEGESENTER AS.

Where is HELSEBANKEN LEGESENTER AS based?

HELSEBANKEN LEGESENTER AS has its business address in Ålgård.

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.