BIZTRAC BETA
General medical practice activities

GURO HAVIG AS

Org. no. 920252990 Limited company (AS) Ringsaker Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 3.4m
Operating profit NOK 677,000
Equity NOK 349,000
Incorporated 2017
Share capital NOK 30,000

GURO HAVIG AS is registered as a limited company in Ringsaker, Innlandet with organisation number 920252990. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Fastlege og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.4m in revenue and NOK 677,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.4m
Operating profit
NOK 677,000
Equity
NOK 349,000
Est. value
NOK 2.7m

Financial health · 2025

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

Who owns GURO HAVIG AS?

GURO HAVIG
GURO HAVIG AS
NOK 3.4m rev. · NOK 677,000 profit

GURO HAVIG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GURO HAVIG AS own?

GURO HAVIG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GURO HAVIG AS

Who owns GURO HAVIG AS?

GURO HAVIG is the largest registered owner, with 100.0%.

What is the revenue of GURO HAVIG AS?

GURO HAVIG AS had revenue of NOK 3.4m in 2025.

Who is the general manager of GURO HAVIG AS?

Guro Havig is registered as general manager of GURO HAVIG AS.

Where is GURO HAVIG AS based?

GURO HAVIG AS has its business address in Moelv.

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.