biztrac. BETA
COMPANY REGISTER PROFILE
923889078 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Business and other management consultancy activities

TORBJØRN SØRBY HOLDING AS

Org. no. 923889078 Limited company (AS) Bærum Incorporated 2019 Active
Ownership graph ↗
Equity NOK 328,000
Incorporated 2019
Share capital NOK 30,000

TORBJØRN SØRBY HOLDING AS is registered as a limited company in Bærum, Akershus with organisation number 923889078. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Konsulentvirksomhet, investeringsvirksomhet, herunder investeringer i aksjer, obligasjoner, selskapsandeler, verdipapirer, fast eiendom, samt utlån eller annen virksomhet, selv eller gjennom hel eller deleide selskaper og annet som naturlig faller sammen med dette.”.

Key figures · 2025

Equity
NOK 328,000
▲ +1243 %
Est. value
NOK 3.2m

Financial health · 2025

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

Who owns TORBJØRN SØRBY HOLDING AS?

TORBJØRN SØRBY HOLDING AS has 2 registered shareholders:

The company is not in the Tax Administration's shareholder register for 2025. The list shows the owners at the end of 2024.

All shareholders and roles →

Which companies does TORBJØRN SØRBY HOLDING AS own?

TORBJØRN SØRBY HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TORBJØRN SØRBY HOLDING AS

Who owns TORBJØRN SØRBY HOLDING AS?

Torbjørn Lee Sørby is the largest registered owner, with 85.5%.

Where is TORBJØRN SØRBY HOLDING AS based?

TORBJØRN SØRBY HOLDING AS has its business address in Kolsås.

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.