BIZTRAC BETA
Passenger transport by cableways and ski lifts

FLØIBANEN AS

Org. no. 911732173 Limited company (AS) Bergen Incorporated 1914 Active
Ownership graph ↗
Revenue 2024 NOK 172.2m
Operating profit NOK 83.9m
Equity NOK 152.4m
Incorporated 1914
Employees 101
Share capital NOK 1.4m

FLØIBANEN AS is registered as a limited company in Bergen, Vestland with organisation number 911732173. The business is classified under passenger transport by cableways and ski lifts (NACE 49.340). The company was incorporated in 1914 and has 101 registered employees. Registered share capital is NOK 1.4m, divided into 135000 shares. The company's stated purpose is: “Drift av elektrisk banen til Fløien og deltakelse i tilknyttet virksomhet som kan øke banens trafikk.”. The most recent filed accounts, for the 2024 financial year, show NOK 172.2m in revenue and NOK 83.9m in operating profit.

Key figures · 2024

Revenue
NOK 172.2m
Operating profit
NOK 83.9m
Equity
NOK 152.4m
Est. value
NOK 329.5m

Financial health · 2024

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

Who owns FLØIBANEN AS?

BERGEN KOMMUNE
FLØIBANEN AS
NOK 172.2m rev. · NOK 83.9m profit

FLØIBANEN AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does FLØIBANEN AS own?

FLØIBANEN AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about FLØIBANEN AS

Who owns FLØIBANEN AS?

BERGEN KOMMUNE is the largest registered owner, with 47.4%.

What is the revenue of FLØIBANEN AS?

FLØIBANEN AS had revenue of NOK 172.2m in 2024.

Who is the general manager of FLØIBANEN AS?

Anders Nyland is registered as general manager of FLØIBANEN AS.

Where is FLØIBANEN AS based?

FLØIBANEN 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.