BIZTRAC BETA
Other captive investment companies

TWIN SPARK AS

Org. no. 964498318 Limited company (AS) Bærum Incorporated 1992 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −59,000
Equity NOK 13.0m
Incorporated 1992
Share capital NOK 100,000

Signals

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

TWIN SPARK AS is registered as a limited company in Bærum, Akershus with organisation number 964498318. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 1992. Registered share capital is NOK 100,000, divided into 200 shares. The company's stated purpose is: “Meglervirksomhet, handelsvirksomhet, samt på annen måte delta i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −59,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −59,000
Equity
NOK 13.0m
Est. value
NOK 26.7m

Financial health · 2024

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

Who owns TWIN SPARK AS?

SØREN HENRIK WARNCKE-WANG
TWIN SPARK AS
NOK 0 rev. · NOK −59,000 profit

TWIN SPARK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TWIN SPARK AS own?

TWIN SPARK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TWIN SPARK AS

Who owns TWIN SPARK AS?

SØREN HENRIK WARNCKE-WANG is the largest registered owner, with 100.0%.

What is the revenue of TWIN SPARK AS?

TWIN SPARK AS had revenue of NOK 0 in 2024.

Who is the general manager of TWIN SPARK AS?

Søren Henrik Warncke-Wang is registered as general manager of TWIN SPARK AS.

Where is TWIN SPARK AS based?

TWIN SPARK AS has its business address in Jar.

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.