BIZTRAC BETA
Intermediation service activities for freight transportation by ship

FINN SØYLAND SHIPPING AS

Org. no. 967633267 Limited company (AS) Kvinesdal Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 5.3m
Operating profit NOK 92,000
Equity NOK 513,000
Incorporated 1993
Employees 14
Share capital NOK 30,000

FINN SØYLAND SHIPPING AS is registered as a limited company in Kvinesdal, Agder with organisation number 967633267. The business is classified under intermediation service activities for freight transportation by ship (NACE 52.311). The company was incorporated in 1993 and has 14 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Skipsmekling/klarering.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.3m in revenue and NOK 92,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.3m
Operating profit
NOK 92,000
Equity
NOK 513,000
Est. value
NOK 573,000

Financial health · 2024

Liquidity
1.17
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
14.3%
Satisfactory
Equity as a share of total capital

Who owns FINN SØYLAND SHIPPING AS?

SVEIN MAGNE MELAND
FINN SØYLAND SHIPPING AS
NOK 5.3m rev. · NOK 92,000 profit

FINN SØYLAND SHIPPING AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about FINN SØYLAND SHIPPING AS

Who owns FINN SØYLAND SHIPPING AS?

SVEIN MAGNE MELAND is the largest registered owner, with 50.0%.

What is the revenue of FINN SØYLAND SHIPPING AS?

FINN SØYLAND SHIPPING AS had revenue of NOK 5.3m in 2024.

Who is the general manager of FINN SØYLAND SHIPPING AS?

Svein Magne Meland is registered as general manager of FINN SØYLAND SHIPPING AS.

Where is FINN SØYLAND SHIPPING AS based?

FINN SØYLAND SHIPPING AS has its business address in Kvinesdal.

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.