BIZTRAC BETA
General medical practice activities

VETLIE AS

Org. no. 989994360 Limited company (AS) Oslo Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −316,000
Equity NOK 14.6m
Incorporated 2006
Share capital NOK 160,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−316k kr).

VETLIE AS is registered as a limited company in Oslo, Oslo with organisation number 989994360. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2006. Registered share capital is NOK 160,000, divided into 1000 shares. The company's stated purpose is: “Legetjenester. Investeringsvirksomhet med verdipapir samt alt som står i forbindelse med dette, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −316,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −316,000
Equity
NOK 14.6m
Est. value
NOK 38.6m

Financial health · 2024

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

Who owns VETLIE AS?

ROLF SØRLIE
VETLIE AS
NOK 0 rev. · NOK −316,000 profit

VETLIE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VETLIE AS own?

VETLIE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about VETLIE AS

Who owns VETLIE AS?

ROLF SØRLIE is the largest registered owner, with 100.0%.

What is the revenue of VETLIE AS?

VETLIE AS had revenue of NOK 0 in 2024.

Who is the general manager of VETLIE AS?

Rolf Sørlie is registered as general manager of VETLIE AS.

Where is VETLIE AS based?

VETLIE 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.