BIZTRAC BETA
Service activities incidental to water transportation

SEAWALK GEIRANGER AS

Org. no. 911626276 Limited company (AS) Stranda Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 14.0m
Operating profit NOK 9.3m
Equity NOK 20.4m
Incorporated 2013
Share capital NOK 13.6m

SEAWALK GEIRANGER AS is registered as a limited company in Stranda, Møre og Romsdal with organisation number 911626276. The business is classified under service activities incidental to water transportation (NACE 52.220). The company was incorporated in 2013. Registered share capital is NOK 13.6m, divided into 1363000 shares. The company's stated purpose is: “Etablere og drive et flytende kaianlegg i Geiranger, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.0m in revenue and NOK 9.3m in operating profit.

Key figures · 2024

Revenue
NOK 14.0m
Operating profit
NOK 9.3m
Equity
NOK 20.4m
Est. value
NOK 39.1m

Financial health · 2024

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

Who owns SEAWALK GEIRANGER AS?

GEIRANGER CRUISE HANDLING AS
SEAWALK GEIRANGER AS
NOK 14.0m rev. · NOK 9.3m profit

SEAWALK GEIRANGER AS has 11 registered shareholders:

All shareholders and roles →

Frequently asked questions about SEAWALK GEIRANGER AS

Who owns SEAWALK GEIRANGER AS?

GEIRANGER CRUISE HANDLING AS is the largest registered owner, with 25.9%.

What is the revenue of SEAWALK GEIRANGER AS?

SEAWALK GEIRANGER AS had revenue of NOK 14.0m in 2024.

Who is the general manager of SEAWALK GEIRANGER AS?

Ørjan Ersland Johansen is registered as general manager of SEAWALK GEIRANGER AS.

Where is SEAWALK GEIRANGER AS based?

SEAWALK GEIRANGER AS has its business address in Geiranger.

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.