BIZTRAC BETA
Rental and operating of own or leased real estate

VSO EIENDOM AS

Org. no. 990814961 Limited company (AS) Tynset Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 2.3m
Operating profit NOK 1.2m
Equity NOK 2.2m
Incorporated 2007
Share capital NOK 3.0m

VSO EIENDOM AS is registered as a limited company in Tynset, Innlandet with organisation number 990814961. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 3.0m, divided into 3000 shares. The company's stated purpose is: “Drive eiendomsutvikling, kjøp og salg av fast eiendom samt utleie og alt som naturlig hører til, herunder også engasjere seg i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.3m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 2.3m
Operating profit
NOK 1.2m
Equity
NOK 2.2m
Est. value
NOK 3.7m

Financial health · 2024

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

Who owns VSO EIENDOM AS?

VIKERN HOLDING AS
VSO EIENDOM AS
NOK 2.3m rev. · NOK 1.2m profit

VSO EIENDOM AS has 4 registered shareholders:

All shareholders and roles →

Which companies does VSO EIENDOM AS own?

VSO EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VSO EIENDOM AS

Who owns VSO EIENDOM AS?

VIKERN HOLDING AS is the largest registered owner, with 40.0%.

What is the revenue of VSO EIENDOM AS?

VSO EIENDOM AS had revenue of NOK 2.3m in 2024.

Who is the general manager of VSO EIENDOM AS?

Ola Petter Søndmør is registered as general manager of VSO EIENDOM AS.

Where is VSO EIENDOM AS based?

VSO EIENDOM AS has its business address in Tynset.

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.