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

NORWIND HELM AS

Org. no. 931070258 Limited company (AS) Ålesund Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 21.6m
Operating profit NOK 11.3m
Equity NOK 15.1m
Incorporated 2023
Share capital NOK 60,000

NORWIND HELM AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 931070258. 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: “Drive 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 21.6m in revenue and NOK 11.3m in operating profit.

Key figures · 2024

Revenue
NOK 21.6m
Operating profit
NOK 11.3m
Equity
NOK 15.1m
Est. value
NOK 39.4m

Financial health · 2024

Liquidity
0.83
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
1.7%
Not satisfactory
Equity as a share of total capital

Who owns NORWIND HELM AS?

NORWIND SHIPHOLDING AS
NORWIND HELM AS
NOK 21.6m rev. · NOK 11.3m profit

NORWIND HELM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

NORWIND HELM AS er morselskap for 5 datterselskaper:

Frequently asked questions about NORWIND HELM AS

Who owns NORWIND HELM AS?

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

What is the revenue of NORWIND HELM AS?

NORWIND HELM AS had revenue of NOK 21.6m in 2024.

Who is the general manager of NORWIND HELM AS?

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

Where is NORWIND HELM AS based?

NORWIND HELM 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.