BIZTRAC BETA
Intermediation service activities for freight transportation by ship

VILHELM RAVN AS

Org. no. 968220446 Limited company (AS) Ullensvang Incorporated 1993 Active
Ownership graph ↗
Revenue 2024 NOK 8.5m
Operating profit NOK 1.3m
Equity NOK 739,000
Incorporated 1993
Employees 29
Share capital NOK 300,000

VILHELM RAVN AS is registered as a limited company in Ullensvang, Vestland with organisation number 968220446. The business is classified under intermediation service activities for freight transportation by ship (NACE 52.311). The company was incorporated in 1993 and has 29 registered employees. Registered share capital is NOK 300,000. The company's stated purpose is: “Skipsmegling, clearing samt annet som står i forbindelse med bistand for skip og rederi ved anløp av havn, derunder transportmegling og lasthåndtering.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.5m in revenue and NOK 1.3m in operating profit.

Key figures · 2024

Revenue
NOK 8.5m
Operating profit
NOK 1.3m
Equity
NOK 739,000
Est. value
NOK 4.2m

Financial health · 2024

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

Who owns VILHELM RAVN AS?

INEOS TYSSEDAL AS
VILHELM RAVN AS
NOK 8.5m rev. · NOK 1.3m profit

VILHELM RAVN AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about VILHELM RAVN AS

Who owns VILHELM RAVN AS?

INEOS TYSSEDAL AS is the largest registered owner, with 36.3%.

What is the revenue of VILHELM RAVN AS?

VILHELM RAVN AS had revenue of NOK 8.5m in 2024.

Who is the general manager of VILHELM RAVN AS?

Trond Harald Sævartveit is registered as general manager of VILHELM RAVN AS.

Where is VILHELM RAVN AS based?

VILHELM RAVN AS has its business address in Odda.

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.