BIZTRAC BETA
Building of civilian ships and floating structures

OVUN AS

Org. no. 964538794 Limited company (AS) Rauma Incorporated 1992 Active
Ownership graph ↗
Revenue 2024 NOK 211.9m
Operating profit NOK 23.0m
Equity NOK 39.0m
Incorporated 1992
Employees 64
Share capital NOK 5.3m

Signals

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

OVUN AS is registered as a limited company in Rauma, Møre og Romsdal with organisation number 964538794. The business is classified under building of civilian ships and floating structures (NACE 30.110). The company was incorporated in 1992 and has 64 registered employees. Registered share capital is NOK 5.3m, divided into 533585 shares. The company's stated purpose is: “Å drive forretningsmessig produksjonsvirksomhet og 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 211.9m in revenue and NOK 23.0m in operating profit.

Key figures · 2024

Revenue
NOK 211.9m
Operating profit
NOK 23.0m
Equity
NOK 39.0m
Est. value
NOK 95.8m

Financial health · 2024

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

Who owns OVUN AS?

OVUN HOLDING AS
OVUN AS
NOK 211.9m rev. · NOK 23.0m profit

OVUN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OVUN AS own?

OVUN AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about OVUN AS

Who owns OVUN AS?

OVUN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of OVUN AS?

OVUN AS had revenue of NOK 211.9m in 2024.

Where is OVUN AS based?

OVUN AS has its business address in Åndalsnes.

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.