BIZTRAC BETA
Hotels and similar accommodation

VETTRE HOTELLDRIFT AS

Org. no. 980452107 Limited company (AS) Asker Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 42.3m
Operating profit NOK −4.5m
Equity NOK 3.0m
Incorporated 1999
Employees 84
Share capital NOK 4.3m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−4,5 mill kr).

VETTRE HOTELLDRIFT AS is registered as a limited company in Asker, Akershus with organisation number 980452107. The business is classified under hotels and similar accommodation (NACE 55.100). The company was incorporated in 1999 and has 84 registered employees. Registered share capital is NOK 4.3m, divided into 1100 shares. The company's stated purpose is: “Drift av Vettre Hotell- og konferansesenter.”. The most recent filed accounts, for the 2024 financial year, show NOK 42.3m in revenue and NOK −4.5m in operating profit.

Key figures · 2024

Revenue
NOK 42.3m
Operating profit
NOK −4.5m
Equity
NOK 3.0m
Est. value
NOK 30.8m

Financial health · 2024

Liquidity
0.67
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.7%
Good
Equity as a share of total capital

Who owns VETTRE HOTELLDRIFT AS?

VETTRE HOTELL EIENDOM AS
VETTRE HOTELLDRIFT AS
NOK 42.3m rev. · NOK −4.5m profit

VETTRE HOTELLDRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VETTRE HOTELLDRIFT AS

Who owns VETTRE HOTELLDRIFT AS?

VETTRE HOTELL EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of VETTRE HOTELLDRIFT AS?

VETTRE HOTELLDRIFT AS had revenue of NOK 42.3m in 2024.

Who is the general manager of VETTRE HOTELLDRIFT AS?

Jeanette Bjerke Meland is registered as general manager of VETTRE HOTELLDRIFT AS.

Where is VETTRE HOTELLDRIFT AS based?

VETTRE HOTELLDRIFT AS has its business address in Vettre.

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.