BIZTRAC BETA
General medical practice activities

LEGE HILDUR GUDMUNDSDOTTIR AS

Org. no. 925557099 Limited company (AS) Arendal Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK 972,000
Equity NOK 175,000
Incorporated 2020
Share capital NOK 30,000

LEGE HILDUR GUDMUNDSDOTTIR AS is registered as a limited company in Arendal, Agder with organisation number 925557099. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Allmenn legetjeneste og alt som hører naturlig til i denne forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK 972,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
Operating profit
NOK 972,000
Equity
NOK 175,000
Est. value
NOK 3.2m

Financial health · 2025

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

Who owns LEGE HILDUR GUDMUNDSDOTTIR AS?

HILDUR GUDMUNDSDOTTIR
LEGE HILDUR GUDMUNDSDOTTIR AS
NOK 2.4m rev. · NOK 972,000 profit

LEGE HILDUR GUDMUNDSDOTTIR AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LEGE HILDUR GUDMUNDSDOTTIR AS own?

LEGE HILDUR GUDMUNDSDOTTIR AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LEGE HILDUR GUDMUNDSDOTTIR AS

Who owns LEGE HILDUR GUDMUNDSDOTTIR AS?

HILDUR GUDMUNDSDOTTIR is the largest registered owner, with 100.0%.

What is the revenue of LEGE HILDUR GUDMUNDSDOTTIR AS?

LEGE HILDUR GUDMUNDSDOTTIR AS had revenue of NOK 2.4m in 2025.

Where is LEGE HILDUR GUDMUNDSDOTTIR AS based?

LEGE HILDUR GUDMUNDSDOTTIR AS has its business address in Kolbjørnsvik.

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.