BIZTRAC BETA
Activities of specialist physicians, other than psychiatrists

GYNEKOLOG GG DALE AS

Org. no. 933790649 Limited company (AS) Stavanger Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK 12,000
Equity NOK 55,000
Incorporated 2024
Share capital NOK 30,000

GYNEKOLOG GG DALE AS is registered as a limited company in Stavanger, Rogaland with organisation number 933790649. The business is classified under activities of specialist physicians, other than psychiatrists (NACE 86.221). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 3 shares. The company's stated purpose is: “Legetjenester innen spesialiteten fødselshjelp og kvinnesykdommer.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK 12,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
Operating profit
NOK 12,000
Equity
NOK 55,000
Est. value
NOK 103,000

Financial health · 2025

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

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

Who owns GYNEKOLOG GG DALE AS?

GRETE GODTLIBSEN DALE
GYNEKOLOG GG DALE AS
NOK 1.7m rev. · NOK 12,000 profit

GYNEKOLOG GG DALE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GYNEKOLOG GG DALE AS

Who owns GYNEKOLOG GG DALE AS?

GRETE GODTLIBSEN DALE is the largest registered owner, with 100.0%.

What is the revenue of GYNEKOLOG GG DALE AS?

GYNEKOLOG GG DALE AS had revenue of NOK 1.7m in 2025.

Who is the general manager of GYNEKOLOG GG DALE AS?

Grete Godtlibsen Dale is registered as general manager of GYNEKOLOG GG DALE AS.

Where is GYNEKOLOG GG DALE AS based?

GYNEKOLOG GG DALE AS has its business address in Stavanger.

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.