BIZTRAC BETA
Rental and leasing of water transport equipment

EIDESVIK SEVEN AS

Org. no. 996540952 Limited company (AS) Bømlo Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 61.6m
Operating profit NOK 15.4m
Equity NOK 239.1m
Incorporated 2011
Share capital NOK 2.4m

EIDESVIK SEVEN AS is registered as a limited company in Bømlo, Vestland with organisation number 996540952. The business is classified under rental and leasing of water transport equipment (NACE 77.340). The company was incorporated in 2011. Registered share capital is NOK 2.4m, divided into 10000 shares. The company's stated purpose is: “Selskapets formål er å drive rederivirksomhet, herunder å eie skip samt drift og management av skip. Selskapet kan ved aksjetegning eller på annen måte engasjere seg i andre foretak med samme formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 61.6m in revenue and NOK 15.4m in operating profit.

Key figures · 2024

Revenue
NOK 61.6m
Operating profit
NOK 15.4m
Equity
NOK 239.1m
Est. value
NOK 168.0m

Financial health · 2024

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

Who owns EIDESVIK SEVEN AS?

EIDESVIK SHIPPING AS
EIDESVIK SEVEN AS
NOK 61.6m rev. · NOK 15.4m profit

EIDESVIK SEVEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about EIDESVIK SEVEN AS

Who owns EIDESVIK SEVEN AS?

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

What is the revenue of EIDESVIK SEVEN AS?

EIDESVIK SEVEN AS had revenue of NOK 61.6m in 2024.

Who is the general manager of EIDESVIK SEVEN AS?

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

Where is EIDESVIK SEVEN AS based?

EIDESVIK SEVEN 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 15.06.2026.

Report a problem

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