BIZTRAC BETA
Uoppgitt

JTW INVEST AS

Org. no. 930701637 Limited company (AS) Fauske Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −20,000
Equity NOK 44.2m
Incorporated 2022
Share capital NOK 30,000

Signals

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

JTW INVEST AS is registered as a limited company in Fauske, Nordland with organisation number 930701637. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Selv, eller gjennom hel- eller deleide selskaper, eller ved å samarbeide med andre selskaper, å forestå investeringsvirksomhet, herunder investering i aksjer, obligasjoner, selskapsandeler, fast eiendom, samt annen virksomhet som har naturlig sammenheng med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −20,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −20,000
Equity
NOK 44.2m
Est. value
NOK 24.9m

Financial health · 2024

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

Who owns JTW INVEST AS?

JØRGEN TRONES WENBERG
JTW INVEST AS
NOK 0 rev. · NOK −20,000 profit

JTW INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JTW INVEST AS own?

JTW INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JTW INVEST AS

Who owns JTW INVEST AS?

JØRGEN TRONES WENBERG is the largest registered owner, with 100.0%.

What is the revenue of JTW INVEST AS?

JTW INVEST AS had revenue of NOK 0 in 2024.

Where is JTW INVEST AS based?

JTW INVEST AS has its business address in Fauske.

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.