BIZTRAC BETA
Passenger transport by cableways and ski lifts

FLØYEN EIENDOM AS

Org. no. 964531870 Limited company (AS) Bergen Incorporated 1992 Active
Ownership graph ↗
Revenue 2024 NOK 5.1m
Operating profit NOK −39.0m
Equity NOK 2.9m
Incorporated 1992
Share capital NOK 1.2m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−39,0 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FLØYEN EIENDOM AS is registered as a limited company in Bergen, Vestland with organisation number 964531870. The business is classified under passenger transport by cableways and ski lifts (NACE 49.340). The company was incorporated in 1992. Registered share capital is NOK 1.2m, divided into 12500 shares. The company's stated purpose is: “Kjøp, salg, utleie og drift av fast eiendom samt hva herved står i forbindelse, inkludert deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.1m in revenue and NOK −39.0m in operating profit.

Key figures · 2024

Revenue
NOK 5.1m
Operating profit
NOK −39.0m
Equity
NOK 2.9m
Est. value
NOK 3.1m

Financial health · 2024

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

Who owns FLØYEN EIENDOM AS?

FLØIBANEN AS
FLØYEN EIENDOM AS
NOK 5.1m rev. · NOK −39.0m profit

FLØYEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FLØYEN EIENDOM AS

Who owns FLØYEN EIENDOM AS?

FLØIBANEN AS is the largest registered owner, with 100.0%.

What is the revenue of FLØYEN EIENDOM AS?

FLØYEN EIENDOM AS had revenue of NOK 5.1m in 2024.

Where is FLØYEN EIENDOM AS based?

FLØYEN EIENDOM AS has its business address in Bergen.

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.