BIZTRAC BETA
Repair and maintenance of machinery

VMS MØRE OG ROMSDAL AS

Org. no. 964838151 Limited company (AS) Sula Incorporated 1992 Active
Ownership graph ↗
Revenue 2024 NOK 82.8m
Operating profit NOK 9.9m
Equity NOK 17.6m
Incorporated 1992
Employees 24
Share capital NOK 200,000

VMS MØRE OG ROMSDAL AS is registered as a limited company in Sula, Møre og Romsdal with organisation number 964838151. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 1992 and has 24 registered employees. Registered share capital is NOK 200,000, divided into 10 shares. The company's stated purpose is: “Verksteds- og servicevirksomhet, å tilby konsulent- og servicetjenester, samt å drive handel med reservedeler, brukte deler, import og industrivirksomhet, samt alt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 82.8m in revenue and NOK 9.9m in operating profit.

Key figures · 2024

Revenue
NOK 82.8m
Operating profit
NOK 9.9m
Equity
NOK 17.6m
Est. value
NOK 48.5m

Financial health · 2024

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

Who owns VMS MØRE OG ROMSDAL AS?

VMS OPERATIONS AS
VMS MØRE OG ROMSDAL AS
NOK 82.8m rev. · NOK 9.9m profit

VMS MØRE OG ROMSDAL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VMS MØRE OG ROMSDAL AS

Who owns VMS MØRE OG ROMSDAL AS?

VMS OPERATIONS AS is the largest registered owner, with 100.0%.

What is the revenue of VMS MØRE OG ROMSDAL AS?

VMS MØRE OG ROMSDAL AS had revenue of NOK 82.8m in 2024.

Where is VMS MØRE OG ROMSDAL AS based?

VMS MØRE OG ROMSDAL AS has its business address in Eidsnes.

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.