BIZTRAC BETA
Freight coastal transport

FSV MANAGEMENT AS

Org. no. 911698005 Limited company (AS) Smøla Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 134.7m
Operating profit NOK 1.6m
Equity NOK 207,000
Incorporated 2013
Employees 218
Share capital NOK 61,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FSV MANAGEMENT AS is registered as a limited company in Smøla, Møre og Romsdal with organisation number 911698005. The business is classified under freight coastal transport (NACE 50.202). The company was incorporated in 2013 and has 218 registered employees. Registered share capital is NOK 61,000, divided into 61224 shares. The company's stated purpose is: “Drift og utleie av fartøy, samt aktiviteter som naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 134.7m in revenue and NOK 1.6m in operating profit.

Key figures · 2024

Revenue
NOK 134.7m
Operating profit
NOK 1.6m
Equity
NOK 207,000
Est. value
NOK 5.2m

Financial health · 2024

Liquidity
1.00
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
0.2%
Not satisfactory
Equity as a share of total capital

Who owns FSV MANAGEMENT AS?

FSV GROUP AS
FSV MANAGEMENT AS
NOK 134.7m rev. · NOK 1.6m profit

FSV MANAGEMENT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FSV MANAGEMENT AS

Who owns FSV MANAGEMENT AS?

FSV GROUP AS is the largest registered owner, with 100.0%.

What is the revenue of FSV MANAGEMENT AS?

FSV MANAGEMENT AS had revenue of NOK 134.7m in 2024.

Who is the general manager of FSV MANAGEMENT AS?

Arild Aasmyr is registered as general manager of FSV MANAGEMENT AS.

Where is FSV MANAGEMENT AS based?

FSV MANAGEMENT AS has its business address in Smøla.

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.