BIZTRAC BETA
Business and other management consultancy activities

LOO TEE HOLDING AS

Org. no. 833940252 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −2,000
Equity NOK 22,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

LOO TEE HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 833940252. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Økonomisk rådgivning og konsulenttjenester og det som naturlig faller under. Samt investeringer i aksjer og deltakelse i andre selskap samt annet som naturlig faller sammen med dette.”.

Key figures · 2025

Operating profit
NOK −2,000
Equity
NOK 22,000
Est. value
NOK 36,000

Financial health · 2025

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

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

Who owns LOO TEE HOLDING AS?

PATRICK JACOB LOO TEE
LOO TEE HOLDING AS
· NOK −2,000 profit

LOO TEE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does LOO TEE HOLDING AS own?

LOO TEE HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LOO TEE HOLDING AS

Who owns LOO TEE HOLDING AS?

PATRICK JACOB LOO TEE is the largest registered owner, with 100.0%.

Who is the general manager of LOO TEE HOLDING AS?

Patrick Jacob Loo Tee is registered as general manager of LOO TEE HOLDING AS.

Where is LOO TEE HOLDING AS based?

LOO TEE 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.