BIZTRAC BETA
Rental and operating of own or leased real estate

VESTROM IN VEST AS

Org. no. 992097205 Limited company (AS) Sør-Aurdal Incorporated 2007 Active
Ownership graph ↗
Revenue 2025 NOK 7,000
Operating profit NOK 5,000
Equity NOK 12.5m
Incorporated 2007
Share capital NOK 1.7m

VESTROM IN VEST AS is registered as a limited company in Sør-Aurdal, Innlandet with organisation number 992097205. 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 1.7m, divided into 100 shares. The company's stated purpose is: “Investering i andre selskaper, investering i fast eiendom mv, samt utøvelse av konsulentvirksomhet innenfor områdene økonomi, administrative styringssystemer og rapportering.”. The most recent filed accounts, for the 2025 financial year, show NOK 7,000 in revenue and NOK 5,000 in operating profit.

Key figures · 2025

Revenue
NOK 7,000
Operating profit
NOK 5,000
Equity
NOK 12.5m
Est. value
NOK 8.6m

Financial health · 2025

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

Who owns VESTROM IN VEST AS?

MAGNE INGVAR RUUD
VESTROM IN VEST AS
NOK 7,000 rev. · NOK 5,000 profit

VESTROM IN VEST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VESTROM IN VEST AS

Who owns VESTROM IN VEST AS?

MAGNE INGVAR RUUD is the largest registered owner, with 100.0%.

What is the revenue of VESTROM IN VEST AS?

VESTROM IN VEST AS had revenue of NOK 7,000 in 2025.

Who is the general manager of VESTROM IN VEST AS?

Magne Ingvar Ruud is registered as general manager of VESTROM IN VEST AS.

Where is VESTROM IN VEST AS based?

VESTROM IN VEST AS has its business address in Hedalen.

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.