BIZTRAC BETA
General medical practice activities

M. GUNDERSEN AS

Org. no. 922100683 Limited company (AS) Haugesund Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 51,000
Operating profit NOK 27,000
Equity NOK 9.0m
Incorporated 2019
Share capital NOK 30,000

M. GUNDERSEN AS is registered as a limited company in Haugesund, Rogaland with organisation number 922100683. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investering i aksjer knyttet til legevirksomhet, annen helserelatert virksomhet og fast eiendom, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 51,000 in revenue and NOK 27,000 in operating profit.

Key figures · 2025

Revenue
NOK 51,000
Operating profit
NOK 27,000
Equity
NOK 9.0m
Est. value
NOK 5.7m

Financial health · 2025

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

Who owns M. GUNDERSEN AS?

MORTEN PENSGÅRD GUNDERSEN
M. GUNDERSEN AS
NOK 51,000 rev. · NOK 27,000 profit

M. GUNDERSEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does M. GUNDERSEN AS own?

M. GUNDERSEN AS holds stakes in 3 companies:

See the full ownership structure →

Group structure

M. GUNDERSEN AS er morselskap for 1 datterselskap:

Frequently asked questions about M. GUNDERSEN AS

Who owns M. GUNDERSEN AS?

MORTEN PENSGÅRD GUNDERSEN is the largest registered owner, with 100.0%.

What is the revenue of M. GUNDERSEN AS?

M. GUNDERSEN AS had revenue of NOK 51,000 in 2025.

Where is M. GUNDERSEN AS based?

M. GUNDERSEN AS has its business address in Haugesund.

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.