BIZTRAC BETA
Rental and operating of own or leased real estate

SON HOTELLEIENDOM AS

Org. no. 988320994 Limited company (AS) Bærum Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 34.2m
Operating profit NOK 23.3m
Equity NOK 168.9m
Incorporated 2005
Share capital NOK 100,000

Signals

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

SON HOTELLEIENDOM AS is registered as a limited company in Bærum, Akershus with organisation number 988320994. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Skal direkte eller indirekte bestå i kjøp, salg, drift, forvaltning, utleie og utvikling av faste eiendommer samt hva som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 34.2m in revenue and NOK 23.3m in operating profit.

Key figures · 2024

Revenue
NOK 34.2m
Operating profit
NOK 23.3m
Equity
NOK 168.9m
Est. value
NOK 152.6m

Financial health · 2024

Liquidity
1.92
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
39.8%
Good
Equity as a share of total capital

Who owns SON HOTELLEIENDOM AS?

THOR HALVORSEN HOLDING AS
SON HOTELLEIENDOM AS
NOK 34.2m rev. · NOK 23.3m profit

SON HOTELLEIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SON HOTELLEIENDOM AS

Who owns SON HOTELLEIENDOM AS?

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

What is the revenue of SON HOTELLEIENDOM AS?

SON HOTELLEIENDOM AS had revenue of NOK 34.2m in 2024.

Where is SON HOTELLEIENDOM AS based?

SON HOTELLEIENDOM AS has its business address in Lysaker.

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.