BIZTRAC BETA
Rental and operating of own or leased real estate

LOFOTEN LANDSKAPSHOTELL AS

Org. no. 927335808 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 251,000
Operating profit NOK 167,000
Equity NOK −646,000
Incorporated 2021
Share capital NOK 500,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−646k kr).

LOFOTEN LANDSKAPSHOTELL AS is registered as a limited company in Oslo, Oslo with organisation number 927335808. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Oppføring og utleie av fritidseiendom, samt aktiviteter som hører til.”. The most recent filed accounts, for the 2024 financial year, show NOK 251,000 in revenue and NOK 167,000 in operating profit.

Key figures · 2024

Revenue
NOK 251,000
Operating profit
NOK 167,000
Equity
NOK −646,000
Est. value
NOK 1.1m

Financial health · 2024

Liquidity
0.29
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-4.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LOFOTEN LANDSKAPSHOTELL AS?

FØSA EIENDOM AS
LOFOTEN LANDSKAPSHOTELL AS
NOK 251,000 rev. · NOK 167,000 profit

LOFOTEN LANDSKAPSHOTELL AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LOFOTEN LANDSKAPSHOTELL AS

Who owns LOFOTEN LANDSKAPSHOTELL AS?

FØSA EIENDOM AS is the largest registered owner, with 50.0%.

What is the revenue of LOFOTEN LANDSKAPSHOTELL AS?

LOFOTEN LANDSKAPSHOTELL AS had revenue of NOK 251,000 in 2024.

Where is LOFOTEN LANDSKAPSHOTELL AS based?

LOFOTEN LANDSKAPSHOTELL 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 15.06.2026.

Report a problem

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