biztrac. BETA
COMPANY REGISTER PROFILE
924791365 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other technical consultancy

TWI HOLDING AS

Org. no. 924791365 Limited company (AS) Grimstad Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK 2,000
Incorporated 2020
Share capital NOK 35,000

Signals

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

TWI HOLDING AS is registered as a limited company in Grimstad, Agder with organisation number 924791365. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2020. Registered share capital is NOK 35,000, divided into 1000 shares. The company's stated purpose is: “Å være et holdingselskap. Investeringer i aksjer og øvrige verdipapirer.”.

Former names: TW ISAKSEN INVEST AS

Key figures · 2025

Operating profit
NOK −5,000
▲ +61 %
Equity
NOK 2,000
▲ +108 %
Est. value
NOK 236,000

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
0.2%
Weak
Equity as a share of total capital

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

Who owns TWI HOLDING AS?

TWI HOLDING AS
· NOK −5,000 profit

TWI HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TWI HOLDING AS own?

TWI HOLDING AS holds stakes in 29 companies:

See the full ownership structure →

Group structure

TWI HOLDING AS er morselskap for 1 datterselskap:

Frequently asked questions about TWI HOLDING AS

Who owns TWI HOLDING AS?

Trond Willi Isaksen is the largest registered owner, with 100.0%.

Who is the general manager of TWI HOLDING AS?

Trond Willi Isaksen is registered as general manager of TWI HOLDING AS.

Where is TWI HOLDING AS based?

TWI HOLDING AS has its business address in Grimstad.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.