BIZTRAC BETA
Activities of specialist physicians, other than psychiatrists

GYNEKOLOG MARTIN ANDRESEN AS

Org. no. 925130478 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 6.9m
Operating profit NOK 3.4m
Equity NOK 1.3m
Incorporated 2020
Share capital NOK 30,000

GYNEKOLOG MARTIN ANDRESEN AS is registered as a limited company in Oslo, Oslo with organisation number 925130478. The business is classified under activities of specialist physicians, other than psychiatrists (NACE 86.221). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Spesialisthelsetjeneste samt alt annet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.9m in revenue and NOK 3.4m in operating profit.

Key figures · 2025

Revenue
NOK 6.9m
Operating profit
NOK 3.4m
Equity
NOK 1.3m
Est. value
NOK 12.1m

Financial health · 2025

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

Who owns GYNEKOLOG MARTIN ANDRESEN AS?

MARTIN ANDRESEN
GYNEKOLOG MARTIN ANDRESEN AS
NOK 6.9m rev. · NOK 3.4m profit

GYNEKOLOG MARTIN ANDRESEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GYNEKOLOG MARTIN ANDRESEN AS

Who owns GYNEKOLOG MARTIN ANDRESEN AS?

MARTIN ANDRESEN is the largest registered owner, with 100.0%.

What is the revenue of GYNEKOLOG MARTIN ANDRESEN AS?

GYNEKOLOG MARTIN ANDRESEN AS had revenue of NOK 6.9m in 2025.

Who is the general manager of GYNEKOLOG MARTIN ANDRESEN AS?

Martin Andresen is registered as general manager of GYNEKOLOG MARTIN ANDRESEN AS.

Where is GYNEKOLOG MARTIN ANDRESEN AS based?

GYNEKOLOG MARTIN ANDRESEN AS has its business address in Oslo.

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.