BIZTRAC BETA
Activities of specialist physicians, other than psychiatrists

GYNEKOLOG S EHRIG AS

Org. no. 830813942 Limited company (AS) Tønsberg Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 109,000
Equity NOK 502,000
Incorporated 2023
Share capital NOK 30,000

GYNEKOLOG S EHRIG AS is registered as a limited company in Tønsberg, Vestfold with organisation number 830813942. The business is classified under activities of specialist physicians, other than psychiatrists (NACE 86.221). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Legevirksomhet, herunder spesialistbehandling innen gynekologi, drift av gynekologisk klinikk, salg av varer og tjenester i denne forbindelse, investering og deltakelse i andre selskaper, investering i aksjer og andeler og hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 109,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 109,000
Equity
NOK 502,000
Est. value
NOK 888,000

Financial health · 2025

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

Who owns GYNEKOLOG S EHRIG AS?

SABINE EHRIG-WESLING
GYNEKOLOG S EHRIG AS
NOK 1.5m rev. · NOK 109,000 profit

GYNEKOLOG S EHRIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GYNEKOLOG S EHRIG AS

Who owns GYNEKOLOG S EHRIG AS?

SABINE EHRIG-WESLING is the largest registered owner, with 100.0%.

What is the revenue of GYNEKOLOG S EHRIG AS?

GYNEKOLOG S EHRIG AS had revenue of NOK 1.5m in 2025.

Where is GYNEKOLOG S EHRIG AS based?

GYNEKOLOG S EHRIG AS has its business address in Revetal.

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.