biztrac. BETA
COMPANY REGISTER PROFILE
933881873 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

PARK PLUSS HOTELL AS

Org. no. 933881873 Limited company (AS) Bergen Incorporated 2024 Active
Revenue 2025 NOK 1.5m
Operating profit NOK −1.5m
Equity NOK 45.1m
Incorporated 2024
Share capital NOK 18.0m

Signals

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

PARK PLUSS HOTELL AS is registered as a limited company in Bergen, Vestland with organisation number 933881873. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 18.0m, divided into 180000 shares. The company's stated purpose is: “Å eie og forvalte, herunder kjøp, salg og utleie av fast eiendom og annet som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK −1.5m in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK −1.5m
▼ −247 %
Equity
NOK 45.1m
▲ +11 %
Est. value
NOK 41.2m

Financial health · 2025

Liquidity
0.30
Not satisfactory
Current assets ÷ current liabilities
Profitability
-1.3%
Not satisfactory
Return on total assets
Solidity
26.5%
Good
Equity as a share of total capital

Who owns PARK PLUSS HOTELL AS?

PARK PLUSS HOTELL AS
NOK 1.5m rev. · NOK −1.5m profit

PARK PLUSS HOTELL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PARK PLUSS HOTELL AS

Who owns PARK PLUSS HOTELL AS?

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

What is the revenue of PARK PLUSS HOTELL AS?

PARK PLUSS HOTELL AS had revenue of NOK 1.5m in 2025.

Where is PARK PLUSS HOTELL AS based?

PARK PLUSS HOTELL AS has its business address in Bergen.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.