BIZTRAC BETA
Rental and operating of own or leased real estate

VEE EIGEDOM AS

Org. no. 939903631 Limited company (AS) Årdal Incorporated 1986 Active
Ownership graph ↗
Revenue 2025 NOK 131,000
Operating profit NOK −147,000
Equity NOK 736,000
Incorporated 1986
Share capital NOK 52,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−147k kr).

VEE EIGEDOM AS is registered as a limited company in Årdal, Vestland with organisation number 939903631. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1986. Registered share capital is NOK 52,000, divided into 26 shares. The company's stated purpose is: “Utleige av eigedom og det som naturleg høyrer til dette og investering i andre selskap i tillegg til servering og overnatting.”. The most recent filed accounts, for the 2025 financial year, show NOK 131,000 in revenue and NOK −147,000 in operating profit.

Key figures · 2025

Revenue
NOK 131,000
Operating profit
NOK −147,000
Equity
NOK 736,000
Est. value
NOK 701,000

Financial health · 2025

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

Who owns VEE EIGEDOM AS?

SVERRE ØRBECK VEE
VEE EIGEDOM AS
NOK 131,000 rev. · NOK −147,000 profit

VEE EIGEDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VEE EIGEDOM AS own?

VEE EIGEDOM AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about VEE EIGEDOM AS

Who owns VEE EIGEDOM AS?

SVERRE ØRBECK VEE is the largest registered owner, with 100.0%.

What is the revenue of VEE EIGEDOM AS?

VEE EIGEDOM AS had revenue of NOK 131,000 in 2025.

Where is VEE EIGEDOM AS based?

VEE EIGEDOM AS has its business address in Øvre Årdal.

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.