BIZTRAC BETA
Freight coastal transport

SOGNEFJORD HAVNESERVICE AS

Org. no. 989409905 Limited company (AS) Årdal Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 3.0m
Operating profit NOK 586,000
Equity NOK 1.1m
Incorporated 2006
Share capital NOK 100,000

SOGNEFJORD HAVNESERVICE AS is registered as a limited company in Årdal, Vestland with organisation number 989409905. The business is classified under freight coastal transport (NACE 50.202). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Agentvirksomhet tilknyttet sjøtransport, kjøp /salg/utleige og investering i alt som naturleg fell under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK 586,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.0m
Operating profit
NOK 586,000
Equity
NOK 1.1m
Est. value
NOK 2.4m

Financial health · 2025

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

Who owns SOGNEFJORD HAVNESERVICE AS?

GLENN MORTEN HESTETUN
SOGNEFJORD HAVNESERVICE AS
NOK 3.0m rev. · NOK 586,000 profit

SOGNEFJORD HAVNESERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SOGNEFJORD HAVNESERVICE AS

Who owns SOGNEFJORD HAVNESERVICE AS?

GLENN MORTEN HESTETUN is the largest registered owner, with 100.0%.

What is the revenue of SOGNEFJORD HAVNESERVICE AS?

SOGNEFJORD HAVNESERVICE AS had revenue of NOK 3.0m in 2025.

Who is the general manager of SOGNEFJORD HAVNESERVICE AS?

Glenn Morten Hestetun is registered as general manager of SOGNEFJORD HAVNESERVICE AS.

Where is SOGNEFJORD HAVNESERVICE AS based?

SOGNEFJORD HAVNESERVICE AS has its business address in Årdalstangen.

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.