BIZTRAC BETA
Rental and operating of own or leased real estate

VETTRE HOTELL EIENDOM AS

Org. no. 981910850 Limited company (AS) Oslo Incorporated 2000 Active
Ownership graph ↗
Revenue 2024 NOK 19.6m
Operating profit NOK 11.8m
Equity NOK 27.7m
Incorporated 2000
Share capital NOK 1.0m

VETTRE HOTELL EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 981910850. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2000. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Å erverve, eie og utvikle hotelleiendommen Vettre Hotell og Konferansesenter - gnr.54 bnr.344 samt gnr.58 bnr.188, Asker kommune.”. The most recent filed accounts, for the 2024 financial year, show NOK 19.6m in revenue and NOK 11.8m in operating profit.

Key figures · 2024

Revenue
NOK 19.6m
Operating profit
NOK 11.8m
Equity
NOK 27.7m
Est. value
NOK 39.3m

Financial health · 2024

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

Who owns VETTRE HOTELL EIENDOM AS?

THON HOTELLBYGG AS
VETTRE HOTELL EIENDOM AS
NOK 19.6m rev. · NOK 11.8m profit

VETTRE HOTELL EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does VETTRE HOTELL EIENDOM AS own?

VETTRE HOTELL EIENDOM AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about VETTRE HOTELL EIENDOM AS

Who owns VETTRE HOTELL EIENDOM AS?

THON HOTELLBYGG AS is the largest registered owner, with 50.0%.

What is the revenue of VETTRE HOTELL EIENDOM AS?

VETTRE HOTELL EIENDOM AS had revenue of NOK 19.6m in 2024.

Where is VETTRE HOTELL EIENDOM AS based?

VETTRE HOTELL EIENDOM 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.