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

PALÉHAVEN HOLDING AS

Org. no. 933252574 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −367,000
Equity NOK 997.0m
Incorporated 2024
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−367k kr).

PALÉHAVEN HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 933252574. 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 100,000, divided into 50 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”.

Former names: BNE H23 AS

Key figures · 2025

Operating profit
NOK −367,000
▼ −35854 %
Equity
NOK 997.0m
▲ +2174708 %
Est. value
NOK 909.8m

Financial health · 2025

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

Who owns PALÉHAVEN HOLDING AS?

PALÉHAVEN HOLDING AS
· NOK −367,000 profit

PALÉHAVEN HOLDING AS has 1 registered shareholder:

The company is not in the Tax Administration's shareholder register for 2025. The list shows the owners at the end of 2024.

All shareholders and roles →

Which companies does PALÉHAVEN HOLDING AS own?

PALÉHAVEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about PALÉHAVEN HOLDING AS

Who owns PALÉHAVEN HOLDING AS?

BANE NOR EIENDOM AS is the largest registered owner, with 100.0%.

Where is PALÉHAVEN HOLDING AS based?

PALÉHAVEN HOLDING 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.