BIZTRAC BETA
COMPANY REGISTER PROFILE
835985962 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

TORGEIR SØRBY HOLDING AS

Org. no. 835985962 Limited company (AS) Tønsberg Incorporated 2025 Active
Ownership graph ↗
Equity NOK 9.2m
Incorporated 2025
Share capital NOK 75,000

TORGEIR SØRBY HOLDING AS is registered as a limited company in Tønsberg, Vestfold with organisation number 835985962. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 75,000, divided into 50 shares. The company's stated purpose is: “Å eie og kjøpe og selge aksjer, samt annen deltagelse i selskaper og det som naturlig står i forbindelse med dette.”.

Key figures · 2025

Equity
NOK 9.2m
Est. value
NOK 21.3m

Financial health · 2025

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

Who owns TORGEIR SØRBY HOLDING AS?

TORGEIR SØRBY HOLDING AS

TORGEIR SØRBY HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TORGEIR SØRBY HOLDING AS own?

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

See the full ownership structure →

Frequently asked questions about TORGEIR SØRBY HOLDING AS

Who owns TORGEIR SØRBY HOLDING AS?

TORGEIR SØRBY is the largest registered owner, with 100.0%.

Where is TORGEIR SØRBY HOLDING AS based?

TORGEIR SØRBY HOLDING AS has its business address in Tolvsrød.

Property

Business address Innlagveien 90, 3153 Tolvsrød
Cadastral unit 3905-97/55/0/0
Building Enebolig · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.