BIZTRAC BETA
Rental and operating of own or leased real estate

FLÅM EIGEDOM AS

Org. no. 984170696 Limited company (AS) Aurland Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 3.7m
Operating profit NOK 2.5m
Equity NOK 9.7m
Incorporated 2002
Share capital NOK 750,000

Signals

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

FLÅM EIGEDOM AS is registered as a limited company in Aurland, Vestland with organisation number 984170696. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2002. Registered share capital is NOK 750,000, divided into 750 shares. The company's stated purpose is: “Å eiga og driva fast eigedom, eigedomsutvikling og å delta i anna verksemd som naturleg høyrer saman med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.7m in revenue and NOK 2.5m in operating profit.

Key figures · 2024

Revenue
NOK 3.7m
Operating profit
NOK 2.5m
Equity
NOK 9.7m
Est. value
NOK 10.5m

Financial health · 2024

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

Who owns FLÅM EIGEDOM AS?

FLÅM HOTELL AS
FLÅM EIGEDOM AS
NOK 3.7m rev. · NOK 2.5m profit

FLÅM EIGEDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does FLÅM EIGEDOM AS own?

FLÅM EIGEDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FLÅM EIGEDOM AS

Who owns FLÅM EIGEDOM AS?

FLÅM HOTELL AS is the largest registered owner, with 50.7%.

What is the revenue of FLÅM EIGEDOM AS?

FLÅM EIGEDOM AS had revenue of NOK 3.7m in 2024.

Where is FLÅM EIGEDOM AS based?

FLÅM EIGEDOM AS has its business address in Flåm.

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.