BIZTRAC BETA
General medical practice activities

KLOSTERHAGEN LEGESENTER AS

Org. no. 933743799 Limited company (AS) Skien Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 4.8m
Operating profit NOK 6,000
Equity NOK 100,000
Incorporated 2024
Employees 5
Share capital NOK 100,000

KLOSTERHAGEN LEGESENTER AS is registered as a limited company in Skien, Telemark with organisation number 933743799. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2024 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 120 shares. The company's stated purpose is: “Drift av legekontor, samt annen virksomhet som naturlig hører innunder.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.8m in revenue and NOK 6,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.8m
Operating profit
NOK 6,000
Equity
NOK 100,000
Est. value
NOK 91,000

Financial health · 2025

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

Who owns KLOSTERHAGEN LEGESENTER AS?

HULDA BIRNA EIRIKSDOTTIR
KLOSTERHAGEN LEGESENTER AS
NOK 4.8m rev. · NOK 6,000 profit

KLOSTERHAGEN LEGESENTER AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about KLOSTERHAGEN LEGESENTER AS

Who owns KLOSTERHAGEN LEGESENTER AS?

HULDA BIRNA EIRIKSDOTTIR is the largest registered owner, with 20.8%.

What is the revenue of KLOSTERHAGEN LEGESENTER AS?

KLOSTERHAGEN LEGESENTER AS had revenue of NOK 4.8m in 2025.

Who is the general manager of KLOSTERHAGEN LEGESENTER AS?

Johanna Heiberg is registered as general manager of KLOSTERHAGEN LEGESENTER AS.

Where is KLOSTERHAGEN LEGESENTER AS based?

KLOSTERHAGEN LEGESENTER AS has its business address in Skien.

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.