biztrac. BETA
COMPANY REGISTER PROFILE
928355349 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

TORU HOLDING AS

Org. no. 928355349 Limited company (AS) Trondheim Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −53,000
Equity NOK 15.1m
Incorporated 2021
Share capital NOK 60,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−53k kr).
  • Nylig endring 2026-04-13 Aksjekapital registrert 2026-04-13.

TORU HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 928355349. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2021. Registered share capital is NOK 60,000, divided into 300 shares. The company's stated purpose is: “Investering i selskaper, eiendom og aksjer, samt deltakelse i andre virksomhet, herunder kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”.

Key figures · 2025

Operating profit
NOK −53,000
▼ −227 %
Equity
NOK 15.1m
▲ +51 %
Est. value
NOK 57.2m

Financial health · 2025

Liquidity
5.82
Very good
Current assets ÷ current liabilities
Profitability
44.4%
Very good
Return on total assets
Solidity
82.1%
Very good
Equity as a share of total capital

Who owns TORU HOLDING AS?

TORU HOLDING AS
· NOK −53,000 profit

TORU HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does TORU HOLDING AS own?

TORU HOLDING AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about TORU HOLDING AS

Who owns TORU HOLDING AS?

Rune Ka Yiu Yip is the largest registered owner, with 50.0%.

Who is the general manager of TORU HOLDING AS?

Tommy Ka Chun Yip is registered as general manager of TORU HOLDING AS.

Where is TORU HOLDING AS based?

TORU HOLDING AS has its business address in Trondheim.

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.