BIZTRAC BETA
General medical practice activities

GILDHEIM LEGESENTER AS

Org. no. 933126315 Limited company (AS) Trondheim Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 4.7m
Operating profit NOK 42,000
Equity NOK 37,000
Incorporated 2024
Share capital NOK 50,000

GILDHEIM LEGESENTER AS is registered as a limited company in Trondheim, Trøndelag with organisation number 933126315. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2024. Registered share capital is NOK 50,000, divided into 500 shares. The company's stated purpose is: “Drift av legesenter samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.7m in revenue and NOK 42,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.7m
Operating profit
NOK 42,000
Equity
NOK 37,000
Est. value
NOK 215,000

Financial health · 2025

Liquidity
1.01
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
5.9%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns GILDHEIM LEGESENTER AS?

HENRIK RICHTER HAMMEREN
GILDHEIM LEGESENTER AS
NOK 4.7m rev. · NOK 42,000 profit

GILDHEIM LEGESENTER AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about GILDHEIM LEGESENTER AS

Who owns GILDHEIM LEGESENTER AS?

HENRIK RICHTER HAMMEREN is the largest registered owner, with 20.0%.

What is the revenue of GILDHEIM LEGESENTER AS?

GILDHEIM LEGESENTER AS had revenue of NOK 4.7m in 2025.

Who is the general manager of GILDHEIM LEGESENTER AS?

Henrik Richter Hammeren is registered as general manager of GILDHEIM LEGESENTER AS.

Where is GILDHEIM LEGESENTER AS based?

GILDHEIM LEGESENTER AS has its business address in Trondheim.

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.