BIZTRAC BETA
Other captive investment companies

ESPEN WESTØL AS

Org. no. 989143662 Limited company (AS) Gjerstad Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −19,000
Equity NOK 1.5m
Incorporated 2005
Share capital NOK 110,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−19k kr).

ESPEN WESTØL AS is registered as a limited company in Gjerstad, Agder with organisation number 989143662. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 110,000, divided into 4 shares. The company's stated purpose is: “Investering og deltakelse i andre selskaper og det som naturlig hører innunder dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −19,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −19,000
Equity
NOK 1.5m
Est. value
NOK 1.8m

Financial health · 2025

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

Who owns ESPEN WESTØL AS?

ESPEN WESTØL
ESPEN WESTØL AS
NOK 0 rev. · NOK −19,000 profit

ESPEN WESTØL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ESPEN WESTØL AS own?

ESPEN WESTØL AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ESPEN WESTØL AS

Who owns ESPEN WESTØL AS?

ESPEN WESTØL is the largest registered owner, with 100.0%.

What is the revenue of ESPEN WESTØL AS?

ESPEN WESTØL AS had revenue of NOK 0 in 2025.

Who is the general manager of ESPEN WESTØL AS?

Espen Westøl is registered as general manager of ESPEN WESTØL AS.

Where is ESPEN WESTØL AS based?

ESPEN WESTØL AS has its business address in Gjerstad.

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.