BIZTRAC BETA
Rental and operating of own or leased real estate

PURO HOTELL PROPERTY AS

Org. no. 926651005 Limited company (AS) Haugesund Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −50,000
Equity NOK 437.2m
Incorporated 2021
Share capital NOK 413.9m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−50k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

PURO HOTELL PROPERTY AS is registered as a limited company in Haugesund, Rogaland with organisation number 926651005. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 413.9m, divided into 413930559 shares. The company's stated purpose is: “Investering fast eiendom, enten direkte eller gjennom selskaper som eier fast eiendom, samt virksomhet og aktivitet som naturlig knytter seg til dette.”.

Key figures · 2024

Operating profit
NOK −50,000
Equity
NOK 437.2m
Est. value
NOK 301.5m

Financial health · 2024

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

Who owns PURO HOTELL PROPERTY AS?

PURO HOTELL HOLDING AS
PURO HOTELL PROPERTY AS
· NOK −50,000 profit

PURO HOTELL PROPERTY AS has 7 registered shareholders:

All shareholders and roles →

Frequently asked questions about PURO HOTELL PROPERTY AS

Who owns PURO HOTELL PROPERTY AS?

PURO HOTELL HOLDING AS is the largest registered owner, with 56.0%.

Who is the general manager of PURO HOTELL PROPERTY AS?

Hans Grønnestad is registered as general manager of PURO HOTELL PROPERTY AS.

Where is PURO HOTELL PROPERTY AS based?

PURO HOTELL PROPERTY AS has its business address in Haugesund.

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.