BIZTRAC BETA
Activities of excursion and event organisers

TOP THE FJORDS AS

Org. no. 824673462 Limited company (AS) Bergen Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 9.2m
Operating profit NOK 595,000
Equity NOK 1.2m
Incorporated 2020
Share capital NOK 30,000

TOP THE FJORDS AS is registered as a limited company in Bergen, Vestland with organisation number 824673462. The business is classified under activities of excursion and event organisers (NACE 79.121). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Selger opplevelsesbaserte aktiviteter og kulinariske båtturer i de norske fjordene på Vestlandet. Vi vil også på forespørsel fra våre gjester tilby guiding/concierge og 24/7 VIP priority service.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.2m in revenue and NOK 595,000 in operating profit.

Key figures · 2025

Revenue
NOK 9.2m
Operating profit
NOK 595,000
Equity
NOK 1.2m
Est. value
NOK 3.3m

Financial health · 2025

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

Who owns TOP THE FJORDS AS?

KGS TRAVEL HOLDING AS
TOP THE FJORDS AS
NOK 9.2m rev. · NOK 595,000 profit

TOP THE FJORDS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TOP THE FJORDS AS

Who owns TOP THE FJORDS AS?

KGS TRAVEL HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of TOP THE FJORDS AS?

TOP THE FJORDS AS had revenue of NOK 9.2m in 2025.

Who is the general manager of TOP THE FJORDS AS?

Karianne Godøy Sætre is registered as general manager of TOP THE FJORDS AS.

Where is TOP THE FJORDS AS based?

TOP THE FJORDS AS has its business address in Mathopen.

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.