BIZTRAC BETA
Construction of utility projects for electricity and telecommunications at sea

NORWIND STORM AS

Org. no. 931070207 Limited company (AS) Ålesund Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 48.7m
Operating profit NOK 20.3m
Equity NOK 233.2m
Incorporated 2023
Share capital NOK 60,000

NORWIND STORM AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 931070207. The business is classified under construction of utility projects for electricity and telecommunications at sea (NACE 42.221). The company was incorporated in 2023. Registered share capital is NOK 60,000, divided into 30000 shares. The company's stated purpose is: “Rederivirksomhet, herunder å eie og drifte skip, samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 48.7m in revenue and NOK 20.3m in operating profit.

Key figures · 2024

Revenue
NOK 48.7m
Operating profit
NOK 20.3m
Equity
NOK 233.2m
Est. value
NOK 157.2m

Financial health · 2024

Liquidity
0.66
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
33.9%
Good
Equity as a share of total capital

Who owns NORWIND STORM AS?

NORWIND SHIPHOLDING AS
NORWIND STORM AS
NOK 48.7m rev. · NOK 20.3m profit

NORWIND STORM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

NORWIND STORM AS er morselskap for 5 datterselskaper:

Frequently asked questions about NORWIND STORM AS

Who owns NORWIND STORM AS?

NORWIND SHIPHOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of NORWIND STORM AS?

NORWIND STORM AS had revenue of NOK 48.7m in 2024.

Who is the general manager of NORWIND STORM AS?

Svein Leon Aure is registered as general manager of NORWIND STORM AS.

Where is NORWIND STORM AS based?

NORWIND STORM AS has its business address in Ålesund.

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.