BIZTRAC BETA
Site preparation

WEST' ENTREPRENØR AS

Org. no. 889221712 Limited company (AS) Drammen Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 8.7m
Operating profit NOK 1.6m
Equity NOK 18.3m
Incorporated 2005
Share capital NOK 100,000

WEST' ENTREPRENØR AS is registered as a limited company in Drammen, Buskerud with organisation number 889221712. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Entreprenørvirksomhet i form av diverse vedlikehold, samt annet som står i forbindelse med dette. ”. The most recent filed accounts, for the 2024 financial year, show NOK 8.7m in revenue and NOK 1.6m in operating profit.

Key figures · 2024

Revenue
NOK 8.7m
Operating profit
NOK 1.6m
Equity
NOK 18.3m
Est. value
NOK 13.2m

Financial health · 2025

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

Who owns WEST' ENTREPRENØR AS?

KAI-HENRIK WESTBY
WEST' ENTREPRENØR AS
NOK 8.7m rev. · NOK 1.6m profit

WEST' ENTREPRENØR AS has 3 registered shareholders:

All shareholders and roles →

Which companies does WEST' ENTREPRENØR AS own?

WEST' ENTREPRENØR AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about WEST' ENTREPRENØR AS

Who owns WEST' ENTREPRENØR AS?

KAI-HENRIK WESTBY is the largest registered owner, with 50.0%.

What is the revenue of WEST' ENTREPRENØR AS?

WEST' ENTREPRENØR AS had revenue of NOK 8.7m in 2024.

Who is the general manager of WEST' ENTREPRENØR AS?

Svein Ivar Westby is registered as general manager of WEST' ENTREPRENØR AS.

Where is WEST' ENTREPRENØR AS based?

WEST' ENTREPRENØR AS has its business address in Mjøndalen.

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.