BIZTRAC BETA
COMPANY REGISTER PROFILE
932011557 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

F17 HOTELLTOMT AS

Org. no. 932011557 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Equity NOK 460,000
Incorporated 2023
Share capital NOK 312,000

F17 HOTELLTOMT AS is registered as a limited company in Oslo, Oslo with organisation number 932011557. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 312,000, divided into 48000 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, eie og leie ut fast eiendom, samt alt hva herved står i forbindelse.”.

Key figures · 2025

Equity
NOK 460,000
▲ +0 %
Est. value
NOK 420,000

Financial health · 2025

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

Who owns F17 HOTELLTOMT AS?

F17 HOTELLTOMT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about F17 HOTELLTOMT AS

Who owns F17 HOTELLTOMT AS?

VASTINT HOSPITALITY BV is the largest registered owner, with 100.0%.

Where is F17 HOTELLTOMT AS based?

F17 HOTELLTOMT AS has its business address in Oslo.

Property

Business address c/o Brækhus Advokatfirma DA Roald Amundsens gate 6, 0161 Oslo
Cadastral unit 301-209/355/0/0
Building Kontor- og administrasjonsbygning, rådhus · 1 unit

54 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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