biztrac. BETA
COMPANY REGISTER PROFILE
977462525 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Supply and other sea transport offshore services

EIDESVIK MPSV AS

Org. no. 977462525 Limited company (AS) Bømlo Incorporated 1997 Active
Ownership graph ↗
Revenue 2025 NOK 65.3m
Operating profit NOK 8.0m
Equity NOK 195.1m
Incorporated 1997
Share capital NOK 35.0m

EIDESVIK MPSV AS is registered as a limited company in Bømlo, Vestland with organisation number 977462525. The business is classified under supply and other sea transport offshore services (NACE 50.203). The company was incorporated in 1997. Registered share capital is NOK 35.0m, divided into 70000 shares. The company's stated purpose is: “Eie og drive skipene Viking Poseidon og Viking Avant.”. The most recent filed accounts, for the 2025 financial year, show NOK 65.3m in revenue and NOK 8.0m in operating profit.

Key figures · 2025

Revenue
NOK 65.3m
▼ −12 %
Operating profit
NOK 8.0m
▼ −62 %
Equity
NOK 195.1m
▲ +8 %
Est. value
NOK 159.6m

Financial health · 2025

Liquidity
10.94
Very good
Current assets ÷ current liabilities
Profitability
7.3%
Satisfactory
Return on total assets
Solidity
57.1%
Very good
Equity as a share of total capital

Who owns EIDESVIK MPSV AS?

EIDESVIK MPSV AS
NOK 65.3m rev. · NOK 8.0m profit

EIDESVIK MPSV AS has 1 registered shareholder:

All shareholders and roles →

Group structure

EIDESVIK MPSV AS er morselskap for 18 datterselskaper:

Frequently asked questions about EIDESVIK MPSV AS

Who owns EIDESVIK MPSV AS?

EIDESVIK SHIPPING AS is the largest registered owner, with 100.0%.

What is the revenue of EIDESVIK MPSV AS?

EIDESVIK MPSV AS had revenue of NOK 65.3m in 2025.

Who is the general manager of EIDESVIK MPSV AS?

Erling Lodden is registered as general manager of EIDESVIK MPSV AS.

Where is EIDESVIK MPSV AS based?

EIDESVIK MPSV AS has its business address in Bømlo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.