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

PARK HOTEL EIENDOM AS

Org. no. 919356553 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 2.7m
Operating profit NOK −1.0m
Equity NOK 265,000
Incorporated 2017
Share capital NOK 30,000

Signals

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

PARK HOTEL EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 919356553. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Eie, drive og utvikle fast eiendom, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK −1.0m in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
▼ −39 %
Operating profit
NOK −1.0m
▼ −211 %
Equity
NOK 265,000
▼ −74 %
Est. value
NOK 242,000

Financial health · 2025

Liquidity
4.69
Very good
Current assets ÷ current liabilities
Profitability
0.5%
Not satisfactory
Return on total assets
Solidity
0.4%
Not satisfactory
Equity as a share of total capital

Who owns PARK HOTEL EIENDOM AS?

PARK HOTEL EIENDOM AS
NOK 2.7m rev. · NOK −1.0m profit

PARK HOTEL EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about PARK HOTEL EIENDOM AS

Who owns PARK HOTEL EIENDOM AS?

PARK HOTEL HOLDCO AS is the largest registered owner, with 100.0%.

What is the revenue of PARK HOTEL EIENDOM AS?

PARK HOTEL EIENDOM AS had revenue of NOK 2.7m in 2025.

Where is PARK HOTEL EIENDOM AS based?

PARK HOTEL 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 03.10.2026.

Report a problem

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