BIZTRAC BETA
Rental and operating of own or leased real estate

VASLAG EIENDOM AS

Org. no. 992047992 Limited company (AS) Melhus Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 3.9m
Operating profit NOK −115,000
Equity NOK 2.2m
Incorporated 2007
Employees 8
Share capital NOK 100,000

Signals

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

VASLAG EIENDOM AS is registered as a limited company in Melhus, Trøndelag with organisation number 992047992. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007 and has 8 registered employees. Registered share capital is NOK 100,000, divided into 200 shares. The company's stated purpose is: “Investering, drift og forvaltning av fast eiendom med tilhørende aktiviteter.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.9m in revenue and NOK −115,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.9m
Operating profit
NOK −115,000
Equity
NOK 2.2m
Est. value
NOK 7.4m

Financial health · 2025

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

Who owns VASLAG EIENDOM AS?

VASLAG HOLDING AS
VASLAG EIENDOM AS
NOK 3.9m rev. · NOK −115,000 profit

VASLAG EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VASLAG EIENDOM AS

Who owns VASLAG EIENDOM AS?

VASLAG HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of VASLAG EIENDOM AS?

VASLAG EIENDOM AS had revenue of NOK 3.9m in 2024.

Who is the general manager of VASLAG EIENDOM AS?

Arnstein Vaslag is registered as general manager of VASLAG EIENDOM AS.

Where is VASLAG EIENDOM AS based?

VASLAG EIENDOM AS has its business address in Melhus.

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.