BIZTRAC BETA
Rental and operating of own or leased real estate

WENAAS HOTELL OSLO AS

Org. no. 979596383 Limited company (AS) Rauma Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 24.5m
Operating profit NOK 15.7m
Equity NOK 173.0m
Incorporated 1997
Share capital NOK 2.5m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

WENAAS HOTELL OSLO AS is registered as a limited company in Rauma, Møre og Romsdal with organisation number 979596383. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1997. Registered share capital is NOK 2.5m, divided into 2 shares. The company's stated purpose is: “Eie, bygge ut, utvikle og forvalte eiendommer.”. The most recent filed accounts, for the 2024 financial year, show NOK 24.5m in revenue and NOK 15.7m in operating profit.

Key figures · 2024

Revenue
NOK 24.5m
Operating profit
NOK 15.7m
Equity
NOK 173.0m
Est. value
NOK 143.2m

Financial health · 2024

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

Who owns WENAAS HOTELL OSLO AS?

WENAAS HOTELS NORWAY AS
WENAAS HOTELL OSLO AS
NOK 24.5m rev. · NOK 15.7m profit

WENAAS HOTELL OSLO AS has 1 registered shareholder:

All shareholders and roles →

Group structure

WENAAS HOTELL OSLO AS er morselskap for 10 datterselskaper:

Frequently asked questions about WENAAS HOTELL OSLO AS

Who owns WENAAS HOTELL OSLO AS?

WENAAS HOTELS NORWAY AS is the largest registered owner, with 100.0%.

What is the revenue of WENAAS HOTELL OSLO AS?

WENAAS HOTELL OSLO AS had revenue of NOK 24.5m in 2024.

Where is WENAAS HOTELL OSLO AS based?

WENAAS HOTELL OSLO AS has its business address in Måndalen.

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.