BIZTRAC BETA
Buying and selling of own real estate

TUW HOLDING AS

Org. no. 911676044 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 240,000
Operating profit NOK 172,000
Equity NOK 6.9m
Incorporated 2013
Share capital NOK 30,000

TUW HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 911676044. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Selskapet skal drive eiendomsutvikling, investering i fast eiendom, eiendomsdrift, utleie av fast eiendom, investering i annen virsomhet, og det som herunder hører naturlig.”. The most recent filed accounts, for the 2025 financial year, show NOK 240,000 in revenue and NOK 172,000 in operating profit.

Key figures · 2025

Revenue
NOK 240,000
Operating profit
NOK 172,000
Equity
NOK 6.9m
Est. value
NOK 5.0m

Financial health · 2025

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

Who owns TUW HOLDING AS?

TIM WANG
TUW HOLDING AS
NOK 240,000 rev. · NOK 172,000 profit

TUW HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TUW HOLDING AS own?

TUW HOLDING AS holds stakes in 11 companies:

See the full ownership structure →

Frequently asked questions about TUW HOLDING AS

Who owns TUW HOLDING AS?

TIM WANG is the largest registered owner, with 100.0%.

What is the revenue of TUW HOLDING AS?

TUW HOLDING AS had revenue of NOK 240,000 in 2025.

Who is the general manager of TUW HOLDING AS?

Tim Wang is registered as general manager of TUW HOLDING AS.

Where is TUW HOLDING AS based?

TUW HOLDING AS has its business address in Oslo.

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.