BIZTRAC BETA
Scheduled long distance passenger transport in coastal waters

FJELLVÅKEN AS

Org. no. 979699492 Limited company (AS) Tinn Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 2.7m
Operating profit NOK 371,000
Equity NOK 3.0m
Incorporated 1998
Employees 8
Share capital NOK 3.2m

FJELLVÅKEN AS is registered as a limited company in Tinn, Telemark with organisation number 979699492. The business is classified under scheduled long distance passenger transport in coastal waters (NACE 50.102). The company was incorporated in 1998 and has 8 registered employees. Registered share capital is NOK 3.2m, divided into 3165 shares. The company's stated purpose is: “Etablere et transportsystem i Møsvatn som er livsnerve for bosetting og utvikling av næring i området.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.7m in revenue and NOK 371,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.7m
Operating profit
NOK 371,000
Equity
NOK 3.0m
Est. value
NOK 2.8m

Financial health · 2024

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

Who owns FJELLVÅKEN AS?

DNT TELEMARK
FJELLVÅKEN AS
NOK 2.7m rev. · NOK 371,000 profit

FJELLVÅKEN AS has 3 registered shareholders:

All shareholders and roles →

Which companies does FJELLVÅKEN AS own?

FJELLVÅKEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FJELLVÅKEN AS

Who owns FJELLVÅKEN AS?

DNT TELEMARK is the largest registered owner, with 35.9%.

What is the revenue of FJELLVÅKEN AS?

FJELLVÅKEN AS had revenue of NOK 2.7m in 2024.

Who is the general manager of FJELLVÅKEN AS?

Jostein Hylland is registered as general manager of FJELLVÅKEN AS.

Where is FJELLVÅKEN AS based?

FJELLVÅKEN AS has its business address in Rjukan.

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.