BIZTRAC BETA
Other technical consultancy

VESTAS NORWAY AS

Org. no. 994967819 Limited company (AS) Trondheim Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 506.3m
Operating profit NOK 43.9m
Equity NOK 116.3m
Incorporated 2010
Employees 116
Share capital NOK 1.1m

VESTAS NORWAY AS is registered as a limited company in Trondheim, Trøndelag with organisation number 994967819. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2010 and has 116 registered employees. Registered share capital is NOK 1.1m, divided into 11000 shares. The company's stated purpose is: “Salg, installasjon og service av vindturbingeneratorer og enhver type utstyr i denne forbindelse samt å drive annen virksomhet som faller inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 506.3m in revenue and NOK 43.9m in operating profit.

Key figures · 2024

Revenue
NOK 506.3m
Operating profit
NOK 43.9m
Equity
NOK 116.3m
Est. value
NOK 303.1m

Financial health · 2024

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

Who owns VESTAS NORWAY AS?

VESTAS NORTHERN EUROPE AS
VESTAS NORWAY AS
NOK 506.3m rev. · NOK 43.9m profit

VESTAS NORWAY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VESTAS NORWAY AS

Who owns VESTAS NORWAY AS?

VESTAS NORTHERN EUROPE AS is the largest registered owner, with 100.0%.

What is the revenue of VESTAS NORWAY AS?

VESTAS NORWAY AS had revenue of NOK 506.3m in 2024.

Who is the general manager of VESTAS NORWAY AS?

Cornelis Anthonius Matheus De Baar is registered as general manager of VESTAS NORWAY AS.

Where is VESTAS NORWAY AS based?

VESTAS NORWAY AS has its business address in Trondheim.

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.