BIZTRAC BETA
Construction of other civil engineering projects n.e.c.

WE BUILD PARKS NORWAY AS

Org. no. 932788209 Limited company (AS) Harstad Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 19.2m
Operating profit NOK 159,000
Equity NOK 54,000
Incorporated 2023
Share capital NOK 30,000

WE BUILD PARKS NORWAY AS is registered as a limited company in Harstad, Troms with organisation number 932788209. The business is classified under construction of other civil engineering projects n.e.c. (NACE 42.990). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Totalentreprenør med spisskompetanse innenfor aktivitetsparker som leverer både prosjektering og utførelse og alt som naturlig faller under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 19.2m in revenue and NOK 159,000 in operating profit.

Key figures · 2024

Revenue
NOK 19.2m
Operating profit
NOK 159,000
Equity
NOK 54,000
Est. value
NOK 434,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns WE BUILD PARKS NORWAY AS?

WE BUILD PARKS SCANDINAVIA AB
WE BUILD PARKS NORWAY AS
NOK 19.2m rev. · NOK 159,000 profit

WE BUILD PARKS NORWAY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WE BUILD PARKS NORWAY AS

Who owns WE BUILD PARKS NORWAY AS?

WE BUILD PARKS SCANDINAVIA AB is the largest registered owner, with 100.0%.

What is the revenue of WE BUILD PARKS NORWAY AS?

WE BUILD PARKS NORWAY AS had revenue of NOK 19.2m in 2024.

Where is WE BUILD PARKS NORWAY AS based?

WE BUILD PARKS NORWAY AS has its business address in Harstad.

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.