BIZTRAC BETA
Other captive investment companies

TRUDE WESTØL AS

Org. no. 989143514 Limited company (AS) Bamble Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −9,000
Equity NOK 244,000
Incorporated 2005
Share capital NOK 110,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−9k kr).

TRUDE WESTØL AS is registered as a limited company in Bamble, Telemark with organisation number 989143514. 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 2024 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −9,000
Equity
NOK 244,000
Est. value
NOK 138,000

Financial health · 2024

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

Who owns TRUDE WESTØL AS?

TRUDE WESTØL
TRUDE WESTØL AS
NOK 0 rev. · NOK −9,000 profit

TRUDE WESTØL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TRUDE WESTØL AS own?

TRUDE WESTØL AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TRUDE WESTØL AS

Who owns TRUDE WESTØL AS?

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

What is the revenue of TRUDE WESTØL AS?

TRUDE WESTØL AS had revenue of NOK 0 in 2024.

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

Trude Westøl is registered as general manager of TRUDE WESTØL AS.

Where is TRUDE WESTØL AS based?

TRUDE WESTØL AS has its business address in Stathelle.

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.